00:26:51 <darwin> how do I change ttyv* foreground & background colours and optionally save setting?
00:28:25 <ngortheone> is there a way to enable dtrace for users?
00:28:56 <ngortheone> i.e. not requrie root privileges to trace user-owned processes?
02:15:19 <kenrap> Hi, I'm trying to write a port that requires inotify_init and I've already added libinotify as part of LIB_DEPENDS but the build still acts like it's an "undefined symbol". Can someone lead me in the right direction?
02:25:43 <V_PauAmma_V> You may get more expert help on porting in #freebsd-ports on Libera. But they'll probably want something more to work from, like a pastebinned build log showing the error.
02:37:39 <hwpplayer1> hi FreeBSD People!
02:53:59 <puddinghead> hey
02:54:12 <puddinghead> i'm planning to start dual booting windows and freebsd, any tips?
03:02:29 <kenrap> Keep it simple by installing FreeBSD on one storage drive and Windows on another and use your UEFI/BIOS's boot manager to select the OS to boot?
03:03:01 <hwpplayer1> he or she is not here as far as I can see
03:03:20 <kenrap> Ah, skimmed it.
03:03:27 <hwpplayer1> np
03:05:54 <kenrap> Honestly, I would prefer to GPU passthrough an nvidia card to a Bhyve VM running Windows for gaming and avoid dual booting.
03:06:19 <kenrap> Waiting 14-RELEASE for that.
07:27:22 <yuripv> kenrap: why do you think it will be supported in 14?
07:28:41 <yuripv> i can only find changes for intel iGPU passthrough
07:55:16 <mage> from time to time I'm getting:
07:55:17 <mage> (da0:mrsas0:1:0:0): READ(10). CDB: 28 00 33 9f ac 48 00 00 f0 00
07:55:17 <mage> (da0:mrsas0:1:0:0): CAM status: SCSI Status Error
07:55:17 <mage> (da0:mrsas0:1:0:0): SCSI status: OK
07:55:23 <mage> any idea what could be the cause of this?
07:55:34 <mage> this is on a Dell r340 with H330 HBA
07:57:57 <meena> mage: so, something is checking CAM for status, but it's too busy to produce a status? or something is causing a hickup? and then it catches up and says everything is fine? (wild guesses)
08:05:56 <mage> meena: I don't know.. I get some CKSUM errors afterwards but a zpool scrub doesn't show any additionnal error
08:07:47 <mage> smart status is OK too
08:08:10 <mage> this is on 12.4-RELEASE
10:09:51 <hwpplayer1> hi FreeBSD People !
10:10:01 <xtile> Hello hwpplayer1 person!
10:10:15 <hwpplayer1> xtile: how are you doing ?
10:10:38 <xtile> Pretty good.  Just chatting. (on my FreeBSD machine)
10:11:23 <hwpplayer1> We are building a local Turkish community btw
10:11:57 <xtile> Nice.
10:12:05 <hwpplayer1> thanks xtile
11:31:31 <kenrap> yuripv: I recall finding out about it being mentioned in r/freebsd. I also tested 14-CURRENT recently and it works, even with the nvidia drivers in Windows and without blue-screening. Bhyve needs a bit more ironing out and it will be awesome.
11:32:54 <yuripv> that's good to hear, really, might go the same way
11:33:15 <yuripv> kenrap: which card btw?
11:35:40 <kenrap> I passed through an EVGA RTX 3080Ti card
12:01:54 <kenrap> #bhyve
12:02:05 <kenrap> Sorry
12:10:28 <yourfate> my freebsd 13.2 on an rpi seems to hang: I can't LS a certain directory on a mounted zpool, LS just hangs indefinitely
12:10:35 <yourfate> so I did `doas reboot`, and that also hangs
12:10:42 <yourfate> I can do other stuff on the system just fine
12:27:27 <yaazkal> morning
13:07:17 <yourfate> is there a way other than `reboot` to force a reboot?
13:07:46 <RhodiumToad> reboot has several options
13:08:25 <yourfate> oh, it has 100% usage on all cores
13:08:44 <RhodiumToad> if you have a filesystem hang in reboot, then reboot -q  is a bigger hammer (doesn't unmount filesystems first) and reboot -qn is an even bigger hammer (doesn't flush dirty buffers)
13:09:45 <yourfate> and I keep seeing this in htop: ` sh -c logger -p local7.warn -t ZFS pool I/O failure, zpool=$'ext-pool' error=$'6'`
13:09:48 <yourfate> that might be it
13:10:57 <yourfate> if I try to umount it I get ` zfs unmount ext-pool
13:10:59 <yourfate> cannot open 'ext-pool': pool I/O is currently suspended`
13:11:15 <RhodiumToad> reboot -q  is usually a fairly safe choice (obviously not ideal, but usually doesn't scrag filesystems)
13:11:40 <RhodiumToad> reboot -qn  is worth a try if reboot -q  is hanging
13:12:18 <RhodiumToad> if even that doesn't work, time for a hardware reset or power cycle
13:13:28 <yourfate> i'm trying to clear the zpool error right now with `zpool clear -nFX ext-pool`, following stack overflow
13:13:31 <yourfate> i'll give that a few mins
13:13:38 <yourfate>  if it doesn't do anything I'll try the reboot -q
13:17:12 <yourfate> -q or even -qn didn't stop anything, I can still open new tmux tabs. I shall have to do the power dance
13:17:16 <yourfate> pray for my SD card
13:17:52 <yourfate> oh, one more idea, i'll unplug the external pool that erroring, maybe that'll let it reboot
13:20:12 <yourfate> not even `shutdown -np now` ran as root does anything other than send the `wall` to every console
13:20:41 <RhodiumToad> shutdown is a high-level rebooter, if reboot doesn't work then shutdown certainly won't
13:21:06 <yourfate> I unplugged it, the rpi was very hot to the touch
13:21:18 <RhodiumToad> shutdown tries to stop all services before rebooting, whereas reboot just kills processes at best
13:21:32 <RhodiumToad> if it was pegged at 100% on all cores, not surprised
13:21:56 <yourfate> yes, and that maybe for at least a day :D
13:24:23 <yourfate> :/ its not comming up, time to bust out an hdmi cable to see what it prints
13:26:49 <yourfate> ah, without the usb drive it booted
13:31:13 <yourfate> I could then re-mount the pool
15:10:14 <CrtxReavr> Guess I've been lucky in that I've never seen reboot not work. . .
15:10:38 <CrtxReavr> Have seen 'shutdown -r' not work.
16:14:13 <Beladona> I am setting node javascript heap size.  that probably depends on your OS. there seems to be no hard-coded limit https://github.com/search?q=repo%3Anodejs%2Fnode+%22max-old-space-size%22&type=code&p=1   If I give 12000 or so, it gives heap out of mameory error. If I give more, it said invalid value.  What should be done here/
16:14:15 <VimDiesel> Title: Sign in to GitHub · GitHub
18:36:37 <Beladona> Something wired is happening. An app says `rror: ENOSPC: no space left on device, open '/li-images/p...` but `zfs list` says `zroot/li-images                             177G used  55.9G avail      177G  Ref /li-images/  Mountpoint.`
18:37:26 <RhodiumToad> what app?
18:37:33 <Beladona> its a nodejs app
18:38:38 <RhodiumToad> my response to weird errors is usually to ktrace the offending process and look for the real underlying error, since often what the app reports is not closely related to what the kernel reported
19:09:16 <Beladona> RhodiumToad ok
21:13:30 <s2r> I'm getting some vulnerabilities warning in the daily cron checks regarding some py9 libraries is there any way to upgrade them? I tried pkg upgrade unsuccesfully. Maybe related to this bug? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270358
21:13:32 <VimDiesel> Title: 270358 – devel/py-setuptools: update to 67.7.2
21:31:03 <Schamschula> s2r: seeing the same. Happily running py311-setuptools 67.7.2 under MacPorts.
21:35:08 <s2r> Schamschula: I tried with latest in pkg/FreeBSD.conf but that didn't upgrade those packages either.
21:35:59 <Schamschula> s2r: the ticket hasn't been closed. In other words, no change has been committed.
23:59:53 <darwin> how do I change ttyv* foreground & background colours and optionally save setting?