00:07:02 freebsd-update fetch | awk 'NF>1{print $NF}' 04:36:31 bitblt: there is a freebsd-ports channel 08:18:30 I assume there is no legitimate reason for Xorg to be resident for more than a gigabyte? 08:39:03 MelMalik: your desktop enviroment software selection for sure :) 08:57:18 badkat, did you just gloss over the word «legitimate» 08:59:44 I could see Xorg being resident for slightly more memory based on my decision to use or not use a certain programme, but that memory should be released when I stop using said programme (be it mpv, firefox, or anything else). 09:01:50 afaik, memory usage of Xorg depends on your screen resolution too 09:52:56 I remember many years ago running the old fglrx driver on Linux, and that made the Xorg process leak quite a bit of memory on my system 09:53:14 the usage gradually kept rising and never went down 09:55:08 do I remember you 09:55:22 also: that just tells us that the problem is prolonged, not that it's not a problem 11:59:32 hi folks! i installed a game and noticed the version was outdated (port doesn't have a maintainer), so i downloaded the latest version straight from github and built it with a few minor changes, what do i do now? do i sumbit a PR where i explain everything i did or do i try to modify the port by myself and the ask for a merge somehow? (I have no idea what I'm doing) 12:00:46 benjamino: perhaps have a look through https://docs.freebsd.org/en/books/porters-handbook/upgrading/ 12:01:38 ivy: thank you! i'll read it at once! 12:02:14 If you have successfully got the game going, perhaps consider becoming the port maintainer: https://docs.freebsd.org/en/articles/contributing/#ports-contributing 12:02:20 if you use the port yourself, you may also consider becoming its maintainer by editing MAINTAINER= in the makefile, but that isn't required to submit an update 12:58:05 What's that Plex replacement people are implementing? 13:00:32 CrtxReavr: Jellyfin for video and Navidrome for audio here 13:00:46 both are well maintained in ports (navidrome wasn't for a while but it has a maintainer now) 13:00:47 ahh - Jellyfin is the one I think was mentioned. 13:00:59 Thanks. 14:02:16 /usr/bin/cd annoys me every time i am reminded that it exists 14:03:48 that's really sad 14:04:06 heartbreaking, really 14:20:40 o_O 14:22:02 is there a way to permanently protect(1) daemons from rc.conf? 14:22:30 WTF even is that? 14:22:35 It doesn't even seem to work. 14:24:24 CrtxReavr: it "works" in that it changes the directory, then immediately exits, so it does nothing. it only exists because it's required by POSIX 14:24:26 phryk, you could probably follow the example of what you find when you look at: grep protect /etc/defaults/rc.conf 14:24:28 CrtxReavr: well, that cd script starts a shell, cds in that shell and then exits that shell, seems really useful 14:26:46 # This file is in the public domain. 14:26:46 Well, thank goodness for that. 14:26:46 wait, where does posix requires an executable cd? I only know about the shell built-in cd being required by posix 14:26:46 nimaje, there's gotta be some legacy kruft reason for it. 14:26:46 I can't say I've noticed that before. 14:26:46 CrtxReavr: oh neat, thanks for pointing out the obvious. seems like it's not a thing specifically implemented in rc.d/syslogd either. :) 14:26:46 Though. .. /usr/bin/[ generally bothers people more. 14:26:46 nimaje: there's some requirement that all the shell builtins have to be available as actual commands, i don't remember where off hand 14:27:07 phryk, it is useful to always remember that /etc/defaults/rc.conf is there. 14:27:29 CrtxReavr: yeah, every 3-4 years i stumble over /etc/defaults but then forget about it again ^^; 14:27:46 * CrtxReavr casually pulls out his tatoo gun. 14:28:12 well, i've been looking for inspiration for a new tattoo, so… 🤔 14:29:08 CrtxReavr: well, [ is usually not a shell built 14:30:21 ivy: found it, but cd is excluded as it is an intrinsic (at least in posix 2024) https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap01.html#tag_18_07 14:31:53 interesting, i wonder if that changed at some point, i would love to get rid of these 14:32:09 (last time i asked i was told we can't, but that was a while ago) 14:36:32 sometimes doing the right thing gets in the way of posix compliance 14:54:21 mhh, i'm getting "protect: option requires an argument -- p" when trying to start services with _oomprotect="YES". but not reliably reproducable… 14:54:52 i have one service where it always happens. had 2 other ones where it just disappeared without further changes to rc.conf when restarting the service a second time. 14:55:28 the service where it always happens also has "service foo status" reporting it's not running, even tho the .pid file exists and points to the correct pid that's running. 15:08:30 okay, these issues seem to be independent. get the same issue with status claiming the service ain't running when i remove the _oomprotect and restart… 15:11:30 Mhh, the package wasn't in my poudriere package list and is still an ancient build with py39 flavor. Gonna ignore it for now and see if it resolves itself when I got a py311 build. 15:18:52 can i get ps or some other tool to show process flags in a *human readable* form? 15:54:02 phryk: ps has libxo support 15:54:22 phryk: try ps --libxo=json -auxw 15:54:34 er, you can probably drop the w 15:54:36 habit :) 15:56:44 ps --libxo=json -o flags 91843 15:56:46 {"process-information": {"process": [{"flags":"10100100"}]}} 15:57:05 oh, you asked for **human readable** 15:57:06 that's even less human-readable if anything^^ 15:57:09 oops 15:57:15 in that case, ps auxwww should do? 15:57:57 unless by process flags you mean something differently than what i'm assuming it means 15:58:52 oh, you mean -o flags, i really should read. in my defence, it's really hot here :| 15:59:12 :P 15:59:16 i really thought procstat(1) would be able to do this, but it cannot 15:59:37 or at least if it can i cannot find it in the manual page 16:00:01 i never really understood why there's ps *and* procstat in the first place tbh. is this some historical thing like apt/aptitude/apt-get on debian?^^ 16:00:50 procstat can do more things, it's more like a debugging utility than a system management thing like ps 16:01:43 also ps is kind of terrible 16:02:15 like, even allowing for the two completely different option syntaxes, the way the options interact with each other just makes no sense 16:02:54 phryk: i can't really find a way to print them in human-readable form through the man page and a skim through the code, sorry :( 16:05:47 dstolfa: no problem – thanks for looking into it and confirming it. :) 16:31:19 mhh, is there really no way to use procctl in a jail? would like to use *_oomprotect for a few services in there. 16:32:31 i assume i could protect those by using jail_oomprotect="ALL" on the host, but that would cast a much wider net and as poudriere jails are the only reason the oomkiller is ever triggered, i'm not sure if that isn't just a recipe for an immediate deadlock. 17:58:22 how do i split a make(1) variable definition over multiple lines without it inserting a space after each backslash? 18:03:19 ivy: Can you be more specific about what you're trying to accomplish? How are you attempting this now? 18:04:07 % printf 'FOO=bar\\\nbaz\n' | make -VFOO -f - 18:04:07 bar baz 18:04:13 i want the output to be "barbaz" 18:04:49 (the reason it's "bar baz" is that make(1) inserts a space after a line continuation using backslash) 18:06:55 dstolfa, FYI, auxwww does nothing different than auxww - no more than two w are recognized. 18:08:03 Is there a reason you can't printf simply "barbaz" instead of including the \\'s and \n's? 18:08:59 CrtxReavr: It was so ingrained in me to use "auxwww" over the years, I still find myself using it. Have to re-learn not to use the 3rd "w". 18:09:59 ivy: Is "printf 'FOO=barbaz' | make -VFOO -f -" not going to work? 18:11:48 ek: for context, https://reviews.freebsd.org/D50150 - i solved this another way but it would be neater if there was a way to do it directly in make 18:20:08 ivy: Ah. Gotcha'. Hrm... That does make it a little more intricate. Can't just pipe to sed or something to remove the whitespace. 18:20:34 ek, trying to save the world 10 ms at a time. 18:20:34 Well, I suppose you could, but you're looking for "cleaner" 18:20:43 Yep. 18:20:50 i think just fudging it in the lua is neater than using sed :-) 18:27:37 Yeah. I'm trying to fudge it via regex but I can't, for the life of me, think of a "clean" way to replace "\\\n" with a non-whitespace while still needing "\\\n" (or a replacement.) 18:29:57 To be fair, "printf 'FOO=bar\\\nbaz\n' | make -VFOO -f -" Isn't terribly readable or clean anyway. Running "printf 'FOO=bar\\\nbaz\n' | make -VFOO -f - | sed 's# ##'" wouldn't make much of a difference. 18:30:33 well, yeah, but we're not actually using printf here, that was just the shortest method to demonstrate the make behaviour i was trying to solve 18:31:39 https://freebsdfoundation.org/blog/the-hidden-costs-of-stagnation-why-running-eol-software-is-a-ticking-time-bomb/ 18:31:46 Right. I see the code in there. That's what I'm trying to adhere to. I'm not sure what a cleaner way would be to remove that whitespace while following that same syntax for that for loop. 18:32:28 About EOL software link above.. I type this from EOL software.. Hexchat, lol. Yet to find suitable replacement :| 18:36:09 nullsector: Yep. For a desktop/GUI IRC client, Hexchat still works just dandy. Shame they haven't continued to maintain it (much.) 18:37:09 I'd imagine here in the next couple or so years, it'll start to choke due to GTK updates and such. Another end of an era. 19:06:51 May The Forth be with you. . . always. 19:52:15 CrtxReavr: May the 4th be with you! 21:07:32 may 7th next ethereum hardfork $>:)|--^< 21:08:47 is anyone here is using only keepassxc secrets provider integration in D-Bus? 21:09:14 maybe some hint to migrate th gnomekeyring to this one? :P