00:48:09 <BillyJoeBob> hello
00:53:15 <jauntyd> hi
02:13:08 <_xor> Anyone got any tips on optimizing NVMe on 13.x?
02:14:10 <_xor> I got an NVMe drive last year and it's been fine. Doing some I/O heavy work right now and wondering if there's anything I can/should tune for it. No big deal, but it feels like it's slower than it should be.
03:23:22 <rtprio> _xor: tunefs -t enable if it's ufs  ?
03:52:44 <ghoti> So.. My workstation is currently running 13.2-BETA2. I'd like to upgrade it to -RELEASE. How do I migrate from -dbg components?
03:53:57 <ghoti> Or does it matter that I'm installing, among other things, kernel/generic-dbg ?
04:02:15 <kevans> ghoti: -dbg pkg is just the symbols for the kernel, you should be able to just upgrade these as normal
04:44:20 <ExclamationPoint> anyone have a recommendation for the source of the most in-depth and complete info on kernel config options that's not "use the source, newb"?
04:50:00 <RhodiumToad> did you read NOTES ?
04:50:15 <ExclamationPoint> RhodiumToad, yep
04:50:48 <ExclamationPoint> wait, maybe i don't know what I need
04:51:34 <ExclamationPoint> I checked the NOTES, LINT, and GENERIC files for my arch, combined the includes, looked around, and couldn't find good info on the options for CPU
04:52:14 <ExclamationPoint> I had to go to the handbook, find the info on config, search config manpages, check the source, etc.
04:52:36 <ExclamationPoint> but I see now that's only valid for "cpu" since other values are just the name itself
04:52:51 <ExclamationPoint> I couldn't find WITH_CTF anywhere until i did a web search either
04:53:18 <ExclamationPoint> what I hoped to find is something with all the options and the possible values for those options if applicable
04:53:32 <ExclamationPoint> if it also included which options are related, that would be epic
04:56:26 <kevans> for WITH_/WITHOUT_ knobs, you want src.conf(5), though the details can be pretty sparse at times
04:57:36 <RhodiumToad> WITH_CTF is a kernel option not a src.conf option
04:58:00 <ExclamationPoint> kevans, checking. that's exaclty my problem. LINT has a comment that's the expanded name of the option. No real explanation
04:59:09 <ExclamationPoint> for example, what exaclty is "options         HID_DEBUG       # enable debug msgs"? am I debugging the HID drivers? am I debugging the HID devices? am I adding debug symbols to the HID drivers or debug messages enabled or other debug functions? JTAG support for the I2C HIDs? WTF?
04:59:12 <RhodiumToad> (more precisely, it goes in "makeoptions" in the kernel config)
05:00:13 <RhodiumToad> _DEBUG options generally mean verbose messages from the relevant driver or module
05:03:57 <ExclamationPoint> RhodiumToad, sure, I was just hoping for better docs for each option. Would anyone support starting a project that's compatible with the current state, but extends the interface for adding config options to support adding it's current name, value, description, supported values, data type, extended description, link to documentation, and link to project?
05:04:58 <ExclamationPoint> The idea being that we slowly convert each entry until the kernel has the info to auto-generate either a Handbook-style documentation set or even a config file directly?
05:05:23 <kevans> right, but most of the kernel WITH* knobs are mirrored versions of the src.conf(5) knobs intentionally
05:05:24 <ExclamationPoint> I don't really want to change the kernel source so this would have to be metadata and external to the kernel project
05:06:04 <kevans> not that they're marked +kernel or not
05:06:18 <ExclamationPoint> checkign src.conf now
05:06:33 <kevans> for stuff like HID_DEBUG, there's likely no good documentation
05:06:45 <kevans> those are config(8) options
05:07:40 <ExclamationPoint> kevans, that's exactly why I'm suggesting a metadata parser that we can run over the kernel and auto-generate both a Handbook-style documentation collection and a config file direclty
05:08:47 <kevans> in an ideal world, in the version of config(8) that we haven't written yet, we provide a description in the option metadata that's naturally machine-readable without tricks
05:09:21 <ExclamationPoint> kevans, maybe that's a natural fit for the thing I'm talking about
05:10:11 <ExclamationPoint> I see src.conf has some stuff, but not exaclty a full set or exmaple values
05:11:27 <kevans> right, figuring out everything that can be tuned is tricky; most of the kernel stuff you want is defined in sys/conf/options and documented (if not there, and if at all) in the various LINT configs
05:12:02 <kevans> there are some WITH* knobs that are defined in sys/conf/kern.opts.mk, many of these can generically be interpreted as "equivalent to whatever src.conf(5) has to say about them, if anything"
05:12:26 <ExclamationPoint> okay, let's say I was going to do the heavy lifting on this. Who would I ask about making sure I don't start something that won't be included because it somehow affects or upsets the authors, contributors, sponsors, or users and is only helpful if needed and unobtrusive if not
05:13:05 <ExclamationPoint> I checked sys/conf/options
05:13:34 <ExclamationPoint> I see an include for an opt_*.h file and those files aren't available in the tree. What do I do to find the next connection there?
05:15:44 <kevans> opt_* file contents are derived from sys/conf/options* (it's the second field on the content lines, "which header this goes in when it's defined") based on what's enabled or not enabled in the kernel config
05:15:47 <RhodiumToad> opt_* are autogenerated
05:16:49 <ExclamationPoint> The reason I ask is because I'm a decent programmer, I've got some spare time, and I can go through the source and track down each config option and get a grip on how the values are used, and then generate a quick explanation. I wanted to try to enlist some AI help. I know that it's possible without getting in anyone's way. I just don't want to do a lot of this work to see it go to waste immediately.
05:16:50 <kevans> (well, that's probably phrased better the other way around, but the idea is that if you want to see what might come from this header, sys/conf/options* are where you answer this)
05:18:15 <ExclamationPoint> okay, they're just #ifdef's in source files
05:18:30 <ExclamationPoint> I thought it was some make file magic, but nope
05:19:59 <ExclamationPoint> so, presumably, all kerenel #define's and #ifdef's are potential config options for the kernel?
05:20:27 <ExclamationPoint> is there a code style guideline for the kernel that bans use of #define's outside the config system?
05:23:15 <kevans> negative
05:23:50 <kevans> you're likely better off to approach it from the other way; take a knob out of sys/conf/options*, grep around for where it's used to get a feel for what it touches
05:24:44 <kevans> I would probably pitch the idea of thoroughly documenting this stuff to freebsd-arch@, btw, with some specifics of how you want the end result to look
05:25:06 <ExclamationPoint> mailign list?
05:25:11 <kevans> yeah
05:26:29 <ExclamationPoint> okay, yeah, here's my plan: I'm going to take one option and follow through on a the minimum usable implementation to get a flow going. then i'm going to think about what options would be helpful or worth investigating. then i'll take that to freebsd-arch@
05:27:07 <ExclamationPoint> I don't want to run in there and just dump this and then have no follow-up ready
05:27:35 <kevans> this is a major task, so it's definitely worth getting some concrete buy-in... we seem to have 900+ config(8) options across all architectures
05:27:51 <kevans> most of them probably not worth documenting, mind you
05:28:45 <ExclamationPoint> kevans, do you really think it's that big? I figured I could get GENERIC for amd64 done in a couple of weekends if I design the process correctly
05:29:51 <kevans> it depends on how you're scoping it; obviously the vast majority of those likely aren't used in any GENERIC config
05:29:54 <kevans> but they do exist
05:35:51 <ExclamationPoint> right now, I'm thinking: get GENERIC, grep options into one file, device into another, for each option create dir in name, grep all files with '#define OPTION" and add filenames to a files.txt, for each file, grep -B 100 -A 100, write a script to find the right #endif and the previous comment, write to "source_X.txt" for code and "commment_X.txt" for comments where X is the pathless filename disambiguated
05:37:13 <ExclamationPoint> then feed all that to a GPT/LLM/NLP chatbot. results would be: option name, option values, option descrition short, option description long or URL of project or related source files. that's off the top of my head. I'm sure I can do better
05:41:16 <Exclamation-Poin> maybe I'm wasting time
05:54:16 <Exclamation-Poin> okay, maybe I'm thinking about this from the wrong perspective. Can anyone help me find the right audience for this question? I suppose kernel developers vs. users who configure kernels but don't spend time with the project open in an IDE and aren't ready to chase down each #define..
05:56:55 <rtprio> what are you talking about man?
05:57:06 <rtprio> what are you trying to accomplish?
05:58:47 <Exclamation-Poin> document kernel config options as quickly and automatically as possible without impacting or upsetting kernel dev's and in a way that's useful to kernel config users
06:00:30 <rtprio> just how often are you building kernels that require these distinct options?
06:01:15 <rtprio> given that gpt just makes shit up, i don't think it's properly suited for documenting techical aspects of the freebsd kernel
06:06:09 <Exclamation-Poin> rtprio, I would like to make something that others use because I plan on customizing kernels for at least 4 machines and I expect to have to build/configure several dozen times, so if I can get my task done faster and help others, I'd like to at least try
06:06:46 <Exclamation-Poin> rtprio, I agree that GPT would have to be filtered through a, hopefully competent, developer's eye.
06:07:07 <rtprio> did you like, you know, read NOTES for more info on those options?
06:07:46 <rtprio> also, once you pare it down a lot you can load modules so you don't to customize that much
06:07:58 <Exclamation-Poin> rtprio, yep, LINT->NOTES->Handbook->man pages->config files->more man pages->source->here
06:08:09 <Exclamation-Poin> that's what got me thinkign this could be done better
06:09:08 <rtprio> then just send patches for NOTES why the fuck would anyone try and make this so complicated
06:10:15 <ExclamationPoint> rtprio, because it's so worthless right now that NOTES might as well be called NONSENSE.
06:11:02 <rtprio> how do you figure
06:11:51 <ExclamationPoint> let me see, what does NOTE say about "cardbus" for example
06:12:10 <ExclamationPoint> # cardbus: CardBus slots
06:12:24 <rtprio> aka pcmica
06:12:26 <ExclamationPoint> oh, well great, now I know whether that's important to include in my kernel
06:12:57 <rtprio> if you don't know, you probably don't have it
06:13:04 <ExclamationPoint> wouldn't have guessed that if it was the last question on who wants to be a millionaire
06:13:33 <ExclamationPoint> rtprio, I have a PCMCIA slot. never used it but also never heard of it being called CardBus
06:14:01 <RhodiumToad> cardbus is technically the extension of pcmcia to 32 bits
06:14:55 <ExclamationPoint> and I used PCMCIA Wifi, TV tuner, GSM data, and GPS and had half of that working in Linux. I probably never did in FreeBSD because WTF IS CARDBUS?
06:15:58 <ExclamationPoint> can we just agree that the kernel options docs are shit? I don't see a reason to argue on taht point. everyone knows but not everyone thinks that a full GUI menu is necessary. I don't like that myself and wouldn't waste time on it. But some docs??
06:16:02 <rtprio> well, i don't think that's the fault of the documentation
06:16:30 <rtprio> include cardbus if you need cardbus but it's on you to know what it is
06:16:36 <rtprio> just like all the shit in that list
06:17:44 <rtprio> do you want to copypasta whatever gpt comes up with to document cardbus for the 1% of people who might be using
06:18:30 <ExclamationPoint> so I should know alternative names for every single thing in my device tree and all the options and values I need to use instead of having that available and updated from the source? why don't I just write the whole OS myself? not much of a step if I only implement the options I need
06:18:59 <rtprio> no need to get huffy because your idea is not a good one
06:19:28 <rtprio> also, as i tried to say, you don't need it in your kernel, it will load as a module if it's needed
06:20:40 <ExclamationPoint> rtprio, I specifically want to use GPT to take the source code #ifdef'd in the config and explain in English how it would alter the behavior of FreeBSD. I think it can do a decent job that I can review.
06:21:02 <rtprio> ok look at the code and tell me if you can better explain what cardbus is
06:21:22 <rtprio> that's ridiculous
06:22:02 <ExclamationPoint> rtprio, I apologize if you misread my mood as "huffy" but please don't confuse the fact that you lack a usecase for this with the usefulness of the idea in others' hands
06:23:33 <rtprio> right. i've read NOTES and gotten by for 15+ years. as most the people in this channel. the ones who could be bothered to build a kernel
06:24:41 <ExclamationPoint> rtprio, I am trying to make something better than NOTES that explains what "device cardbus" does better than it's currenlty done in NOTES. If that's not useful to you, and you aren't obstructed by this, go tell someone else about your opionion. I  want to help some and impede none and their feedback mattes.
06:25:45 <rtprio> ok, well i look forward to see what you come up with
06:26:01 <ExclamationPoint> wait, maybe I'm wrong
06:26:49 <rtprio> i mean, perhaps i last googled 'cardbus' like 10 years ago, well after i threw out all my hardware that might have had cardbus
06:26:51 <ExclamationPoint> your feedback might matter if you have anything to say about why this would be entirely useless in your experience.
06:29:12 <ExclamationPoint> okay, forget cardbus. what about this:
06:29:15 <ExclamationPoint> options         SC_DEBUG_LEVEL=5        # Syscons debug level
06:29:39 <ExclamationPoint> what is that? what does 5 mean? is 0 off or the first option?
06:30:01 <ExclamationPoint> # Yet more undocumented options for linting.
06:30:02 <ExclamationPoint> options         MAXFILES=999
06:30:07 <ExclamationPoint> what does this do?
06:30:50 <rtprio> ok, you got me on that one
06:31:00 <ExclamationPoint> device          speaker         #Play IBM BASIC-style noises out your speaker
06:31:14 <rtprio> but unless youre debugging syscons, there's no reason why you'd ever give a shit
06:31:45 <rtprio> do you not know what a pc speaker is?
06:31:46 <ExclamationPoint> which speakers? the builtin? my tv's? my neighbors? the PC speaker connected to the PIT? do those still exist?
06:31:54 <rtprio> PIT?
06:32:19 <rtprio> yes, the header on the motherboard, from olden times
06:32:27 <ExclamationPoint> i know what a PC speaker is. does it say "PC speaker" anywhere?
06:32:44 <rtprio> it says 'speaker' i feel like that's close enough
06:33:00 <rtprio> not 'sound card' or whatever
06:33:34 <rtprio> just why are you compiling kernels anyway
06:33:57 <rtprio> do you have weird hardware that's not in GENERIC
06:34:36 <ExclamationPoint> options         ATKBD_DFLT_KEYMAP       # specify the built-in keymap
06:34:37 <ExclamationPoint> makeoptions     ATKBD_DFLT_KEYMAP=fr.dvorak
06:34:57 <ExclamationPoint> why is this using options to define and make options to set values? how would I know why it does that?
06:35:34 <RhodiumToad> the keymap is a separate file that has to be processed by the makefile at some stage
06:35:46 <RhodiumToad> so it can't just be a #define
06:36:46 <ExclamationPoint> ok
06:37:16 <rtprio> does the system with PCMICA still have an AT keyboard?
06:37:21 <rtprio> you're killing me, smalls
06:37:43 <RhodiumToad> what's wrong with AT keyboards?
06:38:13 <ExclamationPoint> # More undocumented options for linting. Note that documenting these are not considered an affront.
06:38:13 <ExclamationPoint> options KBDIO_DEBUG=2,options KBD_MAXRETRY=4,options KBD_MAXWAIT=6,options KBD_RESETDELAY=201,options PSM_DEBUG=1,options TIMER_FREQ=((14318182+6)/12),options VM_KMEM_SIZE,options VM_KMEM_SIZE_MAX,options VM_KMEM_SIZE_SCALE
06:38:55 <RhodiumToad> personally I find it annoying that the keyboard map now has to be specified in 4 places (ATKBD, KBDMUX, HKBD, UKBD)
06:39:39 <rtprio> nothing's wrong with it
06:41:30 <ExclamationPoint> RhodiumToad, this would be use case for documentation linking related options. thanks for the heads up
06:45:46 <ExclamationPoint> anyway, if anyone has ideas on how to amke this better, ways to be unobstructive to dev work, or reasons for me to reconsider doing this, I'd love to hear your thoughts
07:18:30 <Demosthenex> ty freebsd for being sane and supporting "df -g"
07:59:07 <armin> Demosthenex: wait until you realize freebsd's ls doesn't have --group-directories-first
08:07:45 <Demosthenex> armin: alas neither linux nor freebsd support grep -p for paragraphs.
08:07:59 <pstef_> I think you can get the same result (as df -g) under Linux by using the BLOCKSIZE variable
09:42:57 <ExclamationPoint> brb
10:38:36 <frafusco> Hi, I got this problem: i carefully followed the instructions of installing the XFCE desktop environment and the LightDM display manager, but after a reboot, the DM won't start.
10:54:33 <wikan> hi, do you know how can I install both, terminal and gtk3 version of vim?
10:56:26 <frafusco> every command was executed correctly and I doule-checked the writing in /etc/fstab
11:06:34 <drobban> having some trouble on understanding an issue I have. trying to use wildcards to perform actions on very large list of files =)
11:06:44 <drobban> example on error msg: exec: Failed to execute process '/usr/bin/grep': the total size of the argument list and exported variables (883kB) exceeds the OS limit of 512kB.
11:07:06 <drobban> how do I change this OS limit?
11:07:39 <drobban> I also seem to hit some limit when I try to browse the same directory with thunar.. =)
11:08:34 <drobban> perhaps the issues I have is related - but I seem to understand the problem to little to even know where to start googling it =D
11:10:21 <debdrup> You probably need to pipe to xargs.
11:18:39 <tercaL> Hello there, got a node process using "21.3G" of "VIRT" ram, any clue on that? https://i.ibb.co/nBCj2S9/highmem.png
11:20:09 <meena> tercaL: any idea what it's doing?
11:20:24 <SKull> tercaL: the clue is that JavaScript is a terrible thing to begin with
11:20:55 <meena> wouldn't it be if node had introspection where you could find out what it's doing and why so much memory is bound up
11:21:06 <tercaL> And by the way, the Swp: shows 0K/0K, but the process uses that much amount.. How can this be?
11:21:17 <debdrup> Please use ps(1) - whatever that tool is, it's probably not reporting the right values.
11:22:03 <debdrup> ps(1) understands the difference between virtual size and resident set size.
11:22:52 <debdrup> I've seen JavaScript stuff take up over 1TB of virtual memory all by itself, while being well under 1GB of resident set size - so it's not exactly unimportant.
11:53:44 <yuripv> well, that screenshot says RES 220M
12:13:27 <tercaL> Interesting and really cool details, thank you all!
12:13:36 <tercaL> Will dig further into the proc. itself..
12:23:41 <drobban> is it possible to change this limit: the total size of the argument list and exported variables (883kB) exceeds the OS limit of 512kB
12:24:14 <drobban> looking at the sysctl list, but not sure which could be relarted
12:26:43 <miltux> kern.argmax maybe?
12:28:00 <drobban> miltux: seems to make no difference in boot/loader.conf and read only with sysctl
12:28:28 <neirac> I'm trying to do use linux emulation, the application works but there is no sound, do I need to setup something extra to make sound be available through linux emu?
12:29:10 <miltux> drobban: it's probably this one, but no idea how to go about changing it
12:29:46 <drobban> miltux: thanks. I tried, it seems like I dont either =D
12:34:14 <dch> wrt pkg: . wrong user or group ownership (expected 0/0 versus actual 1002/0)
12:34:45 <dch> during `pkg --rootdir ... install` this is a reasonable error as this is all as non-root
12:34:59 <dch> is it possible to tell pkg to just go ahead anyway?
12:36:10 <miltux> drobban: If you really, really need it, you have to change /usr/src/sys/sys/syslimits.h and compile a new kernel, I guess. Search for ARG_MAX
12:37:43 <dch> oh we have a #pkg channel I will ask there
12:38:13 <drobban> miltux: =) what I was affraid of.
12:38:28 <drobban> miltux: thx!
12:38:37 <miltux> drobban: np
12:41:30 <miltux> dch: how many files are we talking about? If they're not that many, perhaps @owner and @mode in plist file would be enough
12:44:39 <dch> miltux: this is using pkg install as a non-root user, not modifying a port itself
12:44:58 <miltux> dch: Ah! sorry
14:02:36 <tercaL> An in-line IP change question: I've a jail configuration like; web { ip4.addr = lo1|10.10.10.2; jid = 1; } and so far, it works fine. I'd like to change its ip within the root terminal in host, with the command; jail -m name=web ip4.addr=10.10.10.44, and this works too it seems, because "jls" reports the updated IP. However, when I enter into jail, it seems it didn't change the IP address. And when I restart the jail, the older IP (from jail.conf) seems
14:02:36 <tercaL> back. Any solution to this?
14:03:08 <tercaL> Is there any command like to apply such changes to the jail, without restarting it?
14:24:13 <jschmidt3786> maybe jexec the proper ifconfig command to change the IP?
14:31:25 <meena> jschmidt3786: we now have ifconfig -j !
15:02:59 <rtprio> i imported a disk image that was running zfs into a different system; and files i was expecting in /var are not there
15:03:43 <rtprio> there's only "audit   crash   log     mail    tmp" but /var/puppet is suspiciously missing
15:09:49 <rtprio> where are the other directories that used to live in /var
15:13:16 <isley> maybe a different dataset that you didn't import/mount or maybe a different dataset on a different pool that you didn't import. you'd have to look.
15:14:57 <rtprio> that's the only pool
15:17:52 <rtprio> i've ran into this before and unfortunatly cannot remember the explanation
15:29:37 <markmcb> narrowed the failure mode on PR 273372. IOV for bhyve vms works if i reduce the vfs (or possibly if all vfs are homogenous passthrough). will test more later to see if i can narrow it down further.
15:29:38 <VimDiesel> 273372 – SR-IOV Networking in Bhyve Causes Chelsio T520-SO-CR to Fail on Host, Kernel Panic if Reset https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273372
15:31:40 <jschmidt3786> meena: gotcha, I forgot about that.
15:53:38 <rtprio> i think it has to do with `canmount`
17:05:31 <Ronis_BR> Hi! Is there a way to list all volumes inside a ZFS filesystem?
17:08:37 <yuripv> volumes are inside pool, same as fs
17:10:07 <Ronis_BR> thanks!
17:11:31 <yuripv> if you mean the paths, zfs list -t volume -r path/to/dataset
17:13:14 <Ronis_BR> yuripv: yes, this is perfect! Thanks!
17:13:33 <yuripv> sorry if my first reply didn't make sense, i just read your question wrong
17:14:04 <Ronis_BR> yuripv: np! thanks you very much for your help :)
17:29:38 <public-static> hi, anyone knows where i can get 15.0-CURRENT from?
17:29:44 <public-static> link is dead -> https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/15.0/
17:56:29 <Macer> opnsense isn’t FreeBSD based?
18:00:34 <Cami_no> It is stated that it is based on FreeBSD.
18:02:05 <kevans> public-static: check back in a day or two
18:02:42 <public-static> will do
18:04:40 <kevans> (the first builds post-stable/14 failed, iirc because packages weren't quite there yet)
18:07:31 <Cami_no> public-static: found mirror for i386 http://ftp2.de.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/15.0/
18:07:32 <VimDiesel> Title: Index of /pub/FreeBSD/snapshots/ISO-IMAGES/15.0/
20:17:11 <signalblue_> Hello everyone, I am having a problem getting a WireGuard server (FreeBSD 13.2) to have good performance when connecting to other devices on the same LAN as the server itself. For example, if I am at work, and the work server is connected to my WG server at my datacenter, the work server has a hard time with VNC to a Windows VM on that same network, or a file server on the same network. I'm not sure how to diagnose this as I'm not the most
20:17:11 <signalblue_> fluent in firewall/IPFW/PF (for NAT) configurations.
20:17:21 <signalblue_> for example, my VNC speeds are at 127Kbit/s whereas without WG, the speeds hover aroung 80-110 Mbit/s
20:54:23 <NekobitSock> Hey, could anyone help me getting my USB controller to work without root in Dolphin-emu?
20:54:28 <NekobitSock> I can setup any udev stuff myself.. i think
20:54:32 <NekobitSock> but I tried messing with permissions around /dev/usbXXX, i was getting "Other error" from libusb
20:54:35 <NekobitSock> are these the wrong dev files? is there a specific tool for changing usb device permissions?
20:54:40 <NekobitSock> Of course. These work fine in Root
20:54:44 <NekobitSock> Controller works as is.
20:55:38 <NekobitSock> ugen1.2: <Nintendo WUP-028> at usbus1
20:55:39 <NekobitSock> uhid1 on uhub1
20:55:39 <NekobitSock> uhid1: <Nintendo WUP-028, class 0/0, rev 2.00/1.00, addr 1> on usbus1
20:58:40 <NekobitSock> #chmod 777 /dev/usb/1.2.0 causes the libusb error
20:58:44 <NekobitSock> running it as root works fine.
21:13:46 <Beladona> at 3am what runs that spins hdd so much? its not scrub but what else?
21:23:58 <Beladona> got to do with setuid ?
21:55:47 <V_PauAmma_V> Beladona, looks like "periodic daily". See periodic(8).
22:01:22 <Beladona26> V_PauAmma_V ya but what in it?
22:02:29 <DrKK`> something strange has happened when I did the 13.2p3 update
22:02:37 <DrKK`> with the boot environments
22:02:46 <DrKK`> check it out:
22:02:54 <DrKK`> FBSD-13.1-p2                      NR     /           29.6G 2022-09-14 08:03
22:02:56 <DrKK`> but
22:03:04 <DrKK`> root@daneel:~ # uname -a
22:03:04 <DrKK`> FreeBSD daneel 13.2-RELEASE-p3 FreeBSD 13.2-RELEASE-p3 GENERIC amd64
22:03:13 <DrKK`> root@daneel:~ # freebsd-version -kru
22:03:13 <DrKK`> 13.2-RELEASE-p3
22:03:13 <DrKK`> 13.2-RELEASE-p3
22:03:13 <DrKK`> 13.2-RELEASE-p3
22:03:33 <DrKK`> that's really whacked out, that's a very old boot environment I had back in 2022,
22:03:39 <DrKK`> it somehow, it put the new p3 update into that
22:03:43 <DrKK`> and put it into now/running mode
22:03:47 <DrKK`> what do you make of that?
22:04:12 <DrKK`> excuse me, the next/running mode
22:04:28 <DrKK`> I just used the standard freebsd-update fetch install
22:04:30 <DrKK`> and rebooted
22:07:40 <DrKK`> yeah I'm definitely not insane
22:07:41 <DrKK`> zroot/ROOT/FBSD-13.1-p2                       mounted   yes      -
22:07:56 <DrKK`> any ideas?  I cannot of any reason this should have happened
22:08:42 <DrKK`> I guess I can just rename the boot environment, but this seems crazy
22:10:37 <meena> DrKK`: is freebsd-update.conf still unchanged? does it enable boot envs?
22:11:13 <DrKK`> I'll check that
22:11:18 <DrKK`> but I noticed my "default" is gone
22:11:24 <DrKK`> I don't have a "default" BE
22:11:28 <DrKK`> let's see if it's operator error
22:11:30 <DrKK`> hold one
22:11:32 <V_PauAmma_V> Beladona, see the manual page. It will tell you where under /etc/periodic to look to see what all is done. (Although from your mention of setuid, I'd guess 450.status-security, which in turn runs "periodic security", and through that 100.chksetuid. But that's only a guess.)
22:12:12 <DrKK`> # Create a new boot environment when installing patches
22:12:13 <DrKK`> # CreateBootEnv yes
22:12:16 <DrKK`> so that should be fine
22:12:25 <DrKK`> it's probably my dumb ass somehow deleted the default BE
22:12:32 <DrKK`> let me check the zfs history
22:13:46 <DrKK`> 2022-02-01.23:43:39 zfs destroy -r zroot/ROOT/default
22:13:51 <DrKK`> ^^^
22:13:54 <DrKK`> whoops
22:14:00 <DrKK`> so then something else became my "default"
22:14:10 <DrKK`> and I didn't notice until just now, somehow, after 1.5 years
22:14:16 <DrKK`> that seems hard to believe.  But.  OK.
22:14:59 <DrKK`> cancel inquiry.  I'll assume everything is fine unless this happens again at the next point upgrade
23:13:17 <Soni> is there an sctp equivalent for unix domain sockets?
23:29:59 <Soni> do sctp streams eat up file descriptors?