02:34:51 <polyex> where do ppl point XDG_RUNTIME_DIR to?
02:35:34 <polyex> like ~/.run or ~/.local/run or?
02:36:10 <Zyxer> I thought it goes into /tmp/ and then $USER or soemthing
02:37:16 <polyex> handbook has /var/run/user/uid
02:37:29 <polyex> seems weird to put user dirs outside their home tho
02:38:08 <polyex> another freebsd blog i read used /tmp/uid-runtime-dir
02:38:55 * V_PauAmma_V left it to the default value.
02:39:02 <Zyxer> The /tmp isn't weird
02:39:11 <Zyxer> V_PauAmma_V: What is the default?
02:39:38 <polyex> default from where? not base
02:40:24 <Zyxer> I am also curious about that
02:42:05 <V_PauAmma_V> I just checked, and (using Xfce) it's unset by default.
02:42:33 <Zyxer> It is usually set by Display Managers
02:42:42 <Zyxer> Hmm...
02:43:12 <Zyxer> On my linux thing it is
02:45:25 <Zyxer> /run/user/{UID}
02:45:37 <Zyxer> Uh...
02:46:06 <polyex> which explains i guess why freebsd handbook says /var/run/user/uid
02:46:08 <Zyxer> Change {UID} to the UID, usually 1000 is the UID of the first user made other than root
02:46:46 <Zyxer> user is just user, not user login
03:10:59 <_xor> Anyone know which flavor of regex expr uses/implements? Trying to loop over an fstab file for a jail and create the mountpoint directories before starting the jail, but for some reason I'm having trouble matching the first line against \/.+\s+\/.+ to verify it before cutting the 2nd column.
03:11:31 <kevans> should be BREs
03:11:31 <_xor> ...or alternatively, if there's a way to tell mount to create the target directory if it doesn't already exist, which would be ideal :D
03:11:57 <_xor> Hmm
03:11:57 <kevans> I have a patch that adds an -E option to use EREs, but I haven't looked at it in probably five years
03:12:18 <_xor> Pulls in a lib, I assume?
03:12:29 <kevans> nah, just non-standard
03:12:51 <kevans> try something like \/.{1,}[[:space:]]{1,}\/.{1,}
03:12:54 <_xor> Ah
03:13:04 <kevans> ugly, unwieldy,  but it might work
03:13:10 <kevans> alternatively, awk might be nicer
03:13:18 <_xor> Yeah, I might just go with awk.
03:13:55 <_xor> Hmm, apparently it didn't like that expression either.
03:14:33 <_xor> expr '\\/.{1,}[[:space:]]{1,}\\/.{1,}' : '/mnt/services/data /cluster/nomad/jails/EXAMPLE/data/jail/mnt/data nullfs rw,noatime 0 0'
03:14:38 <_xor> That should match, no?
03:15:00 <_xor> oh wait, remove the escape slashes since I'm single quoting it?
03:15:22 <_xor> Nevermind, removing them didn't help either heh.
03:32:23 <V_PauAmma_V> ... You have the string and regex reversed.
03:33:48 <V_PauAmma_V> Quoting from expr(1): The “:” operator matches expr1 against expr2, which must be a basic regular expression.
03:34:34 <kevans> also, I forgot that bounds have to be escaped
03:34:43 <kevans> '\/.\{1,\}[[:space:]]\{1,\}\/.\{1,\}'
08:08:20 <dch> welp, we're on -p3 for 14.0-RELEASE already...
08:11:29 <Reinhilde> oh
08:22:42 <meena> dch: and that's why more people need to test RCs
08:24:22 <Reinhilde> ope
10:20:10 <nerozero> found this: https://github.com/dylanaraps/pure-sh-bible , maybe some one find this useful
10:20:11 <VimDiesel> Title: GitHub - dylanaraps/pure-sh-bible: 📖 A collection of pure POSIX sh alternatives to external processes.
10:24:51 <polyex> update on alacritty not running on a vm, over rdp, after a freebsd-update and pkg upgrade a few days ago. tried to ssh into vm and run alacritty on the rdp session: DISPLAY=:10 (my xrdp x11 display) alacritty says mesa: error: zink: failed to load libvulkan.so.1 glx failed to create drisw screen failed to load driver zink
10:25:01 <polyex> can anyone help me figure that out or fix it or smth?
10:27:10 <polyex> adding LIBGL_ALWAYS_SOFTWARE=1 and it runs btw, so definitely a bug in the driver
10:29:12 <polyex>  llvmpipe is better than zink too i guess, author of alacritty says
10:32:46 <polyex> the reason vulkan got loaded is because of zink, since it's a OpenGL to Vulkan translation layer.
10:46:07 <polyex> 13.2
10:55:08 <Remilia> now on -p3 woo
11:03:07 * meena needs to do that too
11:05:32 <meena> uh-oh. No updates for pkgbase yet :O
11:31:52 <ghoti> Ugh. I have a bhyve process that's taking all my memory.  Can't seem to kill it. Is there a way I can hit it harder than `kill -9`?  My `ps auxw` output shows this:
11:31:56 <ghoti> root      3209    0.0 87.9 127644812 117926436 v0- TNC  Tue03     297:54.00 bhyve: haos (bhyve)
11:34:58 <meena> ghoti: first up, both of those things seem like bugs and should be reported
11:35:40 <meena> if kill -9 doesn't work, then i suggest trying a reboot, after getting the info you need to report a bug
11:54:47 <nerozero> ghoti, how did you run the "bhyve process" ?
11:56:44 <nerozero> if you use vm-bhyve package to manage virtual machine run "vm powerof <vmname>"
11:57:01 <nerozero> "vm poweroff <vmname>"
11:58:16 <nerozero> or stock bhyvectl: bhyvectl --vm=vmname --destroy
11:58:40 <nerozero> or bhyvectl --vm=vmname --force-poweroff
12:18:16 <ghoti> nerozero: for that one, I'm using vm-bhyve to launch; it has a pretty basic config, here: http://sprunge.us/LMP8gU
12:18:56 <nerozero> is it amd machine ?
12:19:32 <ghoti> meena: this is in 13.2, which I recently upgraded to. All was fine in 12.4.
12:20:19 <ghoti> nerozero: nope, CPU: Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz (2600.11-MHz K8-class CPU)
12:20:41 <nerozero> yah ...
12:21:21 <ghoti> ?
12:21:26 <scoobybejesus> vm-bhyve is being run on the host, right?
12:21:38 <ghoti> Yes.
12:21:40 <nerozero> My issue with bhyve is that windows guest machine usint 200% cpu core doesn't matter is guest doing something or completely idle
12:22:23 <ghoti> I haven't run Windows in years.. This was a HAOS appliance, Linux..
12:22:54 <ghoti> And this wasn't CPU, I can afford that; it was failure to release memory.
12:23:18 <ghoti> From top: Mem: 27M Active, 776K Inact, 111G Laundry, 9417M Wired, 1397M Free
12:23:30 <nerozero> same but office need one accounting software which is run only on win 7
12:24:10 <ghoti> The machine has 128GB RAM. Everything plus swap got used.
12:24:37 <nerozero> never had ram issues with bhyve
12:25:15 <nerozero> in case of zfs your zfs will try to grab as many ram as it possible
12:25:22 <nerozero> this is normal
12:26:04 <nerozero> could you please share the "top" head ?
12:26:13 <nerozero> what is in the ARC field ?
12:29:00 <ghoti> Hmm, I was running an older patch level of 13.2. One sec while I upgrade and test again..
12:33:26 <ghoti> nerozero: here's the top of `top` when I'm not running that bhyve VM: http://sprunge.us/JYyNAM
12:37:24 <ghoti> Sigh.. Seems to bebehaving after the upgrade. Ain't that always the way? Anyway, thanks for your attention...
12:41:39 <nerozero> ghoti, sorry, working in parallel ..
12:41:44 <nerozero> try this link: https://forums.freebsd.org/threads/bhyve-100-cpu-usage.58398/
12:41:45 <VimDiesel> Title: bhyve 100% CPU usage | The FreeBSD Forums
12:42:01 <nerozero> it may have some useful information
16:35:15 <ghoti> nerozero: indeed, there are some useful diagnostic strategies there. But still, my problem was not CPU usage, it was laundered memory not being released. And I haven't been able to replicate it since upgrading to 13.2-p8.
16:36:31 <nerozero> ghoti, could you please create a new thread in freebsd forum and post the link here?
16:36:58 <nerozero> I'm also a active bhyve user so ...
16:38:09 <nerozero> also you can find a #bhyve  channel here on libera, but its kinda dead, never respond anyone there ...
17:10:39 <ghoti> nerozero: yes, I gave up on #bhyve a while ago. Tell you what, I'll create a thread if I can replicate the problem. If I can't, I think I just chalk it up to randomness that went away with the update.
17:11:38 <nerozero> ghoti, good luck!
17:11:47 <ghoti> Or should I make a thread basically saying "this happened; what do I do if it happens again?"
17:12:57 <nerozero> IMHO, if problem still exists, it is good to share the issue and steps taken... If someone else will experience same issue - the thread will grow.
17:13:06 <ghoti> In almost 2 decades of FreeBSD, I've never seen this before, which makes me think it can't be too common. :)
17:13:40 <nerozero> I'm with BSD from bsd 3.0
17:17:51 <ghoti> Dang, I'm counting wrong. I started with 2.2 I think. So a quarter century I guess.
17:19:49 <nerozero> :) remember deco commander? on  Hercules monochrome screen? :)
17:21:13 <nerozero> squid and mgetty, IDSDL for USRobotics Courier modems ... yah...
17:22:57 <ghoti> 720 × 348 was my favourite resolution. :)  I didn't use deco though. I came from 4DOS/4OS2 and SCO Xenix. Different lifestyle...
17:23:36 <nerozero> yeh ....
17:23:41 <nerozero> what a time...
17:24:55 * RhodiumToad started just before 2.2
17:25:24 <nerozero> 386 with 16MB or ram ...
17:25:44 <nerozero> 40MB hard drive
17:25:53 <nerozero> that was a server :D
17:26:31 <nerozero> custom kernel compilation took ~1 day
17:29:22 <nerozero> actually I do remember 2.2 BSD
17:30:30 <nerozero> the longest supported bsd was 4.22 if I recall
17:38:36 <ghoti> Chronologically, the 2.2 branch had the longest stretch of releases, with 2.2.9.
17:43:03 <RhodiumToad> freebsd 4.x had a long production lifetime because of the whole 5.x issue (5.x was really a development-only branch for making SMP work)
17:44:57 <ghoti> yes. fbsd has long had a reputation for putting experimental/broken stuff into odd-numbered releases. Seemed to go away with fbsd 9.
17:47:42 <RhodiumToad> I think I skipped over either 7 or 8 or both, I don't recall
17:49:00 <RhodiumToad> I think the idea was that the odd numbers were "current" rather than "stable", but I wasn't paying so much attention to development back then
18:32:47 <michaeldexter> Is this 404 for you too? https://mail-archive.freebsd.org/mail/archive/2022/
18:33:06 <Zyxer> It 404 for me
18:36:12 <Kalten> For me too
18:36:52 <michaeldexter> Any list admins here to look at that?
18:41:15 <Kalten> https://mail-archive.freebsd.org/mail/archive/2021/ does work, so likely wrong owner/rights of the directory
18:41:16 <VimDiesel> Title: Index of /mail/archive/2021/
18:43:10 <michaeldexter> Yep, most years work.
18:52:11 <V_PauAmma_V> Wouldn't wrong owner/rights be a 403 rather than a 404?
19:00:53 <Kalten> V_PauAmma_V: oh! You are right! Sorry.
19:10:59 <V_PauAmma_V> michaeldexter, if no list admin answers, email postmaster@? I think that's also the web archive server admin group.
19:15:03 <michaeldexter> Mystery maybe solved: https://lists.freebsd.org/pipermail/freebsd-current/
19:15:04 <VimDiesel> Title: The freebsd-current Archives
19:15:14 <michaeldexter> Certain archives are there.
19:15:38 <michaeldexter> But not 2022. Hmm
19:17:53 <michaeldexter> I have mailed postmaster@ asking how that is intended to be accessed.
19:30:50 <Kalten> at least the directory 2022/ with a file named “no archive for 2022” so people do not wonder what happened
19:43:14 * kevans whips up a conspiracy theory
19:43:56 <RhodiumToad> the lizards did it
19:45:05 <meena> maybe it was advanced lizards…
19:45:12 <meena> like… birds.
19:46:33 <Kalten> Those: https://almanach.worldofgothic.de/index.php/Echsenmenschen
19:46:34 <VimDiesel> Title: Echsenmenschen – Gothic Almanach
19:47:55 <RhodiumToad> I think technically they (birds) are not lizards, even in a broad sense, since "lizard" refers to a different branch of the reptiles
19:49:06 <rwp> I'll believe the advanced lizard alchemists theory, but there not that birds exist, no way, did my own research on that one.
19:49:35 <meena> yeah, I guess that's like saying a shark is a fish, which is true in the most abstract sense
19:49:42 <RhodiumToad> uh
19:49:50 <RhodiumToad> a shark definitely is a fish?
19:50:04 <RhodiumToad> it's just not a bony fish
19:58:38 <Zyxer> Hi.
20:00:18 * RhodiumToad grumbles at missing or outdated leapseconds files
21:14:27 <rwp> RhodiumToad, Re leap-seconds.list, Yes, Is there a plan that I might know about how FreeBSD handles such things?  (I know I can manually update it.)  I have so many questions.  Is the plan to update from 13 to 14?  Is it updated in 14?  To install the port of ntpd, ntpsec, or openntp?
22:55:27 <topcat001> Just finished installing 14.0 at work. This will be our clang machine (why? because I love it).
22:56:12 <topcat001> (our Linux devs are very excited :))
23:12:26 <cybercrypto> Hey... not sure where to look... everytime I open a term, I got this: bash: SRCDIR: unbound variable
23:12:56 <cybercrypto> I am not sourcing anything in bashrc nor .profile....
23:13:12 <cybercrypto> not sure where to start looking 8-) any clues?
23:16:17 <rwp> cybercrypto, Sounds like a shell with -u set which will error when any unset variable is referenced.
23:16:47 <rwp> But I can't create a reproducer for that exact message.
23:18:00 <rwp> Ah, yes, try this: bash -uc 'echo $SRCDIR'
23:19:06 <rwp> Regardless, I am NOT an advocate for the use of -u and I recommend not using it.  Along with -e.  Both of those are not helpful.  Not like people wish them to be helpful.
23:22:28 <rwp> cybercrypto, If it is every time you open a terminal then it must be in the environment file somewhere.  If not the default ~/.bashrc then $ENV.  But put a "set -x" at the top of the .bashrc file for a debug run and that should trace through it.
23:23:04 <rwp> You don't have to open a new terminal.  Just stack another shell.  Invoke "bash" again in the terminal.
23:25:14 <_0pr_> join #c
23:25:26 <_0pr_> whoops...
23:27:27 <mane> i'm reading about ipsec but the example the handbook contains is showing how to connect two lans over ipsec
23:27:53 <mane> i'd like to see how to make kinda client - server solution if possible