00:03:44 <sixpiece> yes it does
00:03:46 <sixpiece> in usb config
00:04:40 <sixpiece> not sure how to do it for sysctl
00:04:47 <RhodiumToad> what's the device id?  usbconfig -d ... dump_device_desc
00:05:23 <RhodiumToad> specifically idVendor / idProduct
00:06:18 <sixpiece> https://termbin.com/n897
00:06:43 <RhodiumToad> the realtek?
00:06:47 <sixpiece> yes
00:07:01 <RhodiumToad> usbconfig -d ugen3.2 dump_device_desc
00:08:21 <sixpiece> https://termbin.com/1qdu
00:08:39 <RhodiumToad> what freebsd version?
00:08:52 <sixpiece> 386 13.1
00:09:44 <sixpiece2> hello I am in the chat now with this computer
00:09:57 <sixpiece2> as well as my laptop running natively freebsd
00:10:28 <sixpiece2> FreeBSD 13.2-RELEASE releng/13.2-n254617-525ecfdad597 GENERIC
00:12:17 <RhodiumToad> sixpiece: as far as I can tell there's no driver for it
00:12:46 <RhodiumToad> that usb device id isn't in the usb device list or in any of the builtin driver sources
00:12:56 <sixpiece2> ok so just return it?
00:13:17 <sixpiece2> what a headache
00:13:27 <sixpiece2> hopefully they take it back without questions
00:14:32 <sixpiece2> ok thank you it's a done deal correct?
00:19:25 <RhodiumToad> as far as I know. my knowledge in this area is not perfect
00:19:43 * RhodiumToad not expert in laptops or wifi
00:23:42 <sixpiece2> there's a patch available supposedly
00:23:54 <sixpiece2> I mean is it worth doing or it's just a headache and try to find the one that works?
00:24:33 <sixpiece2> https://forums.freebsd.org/threads/getting-tp-link-archer-t2u-ac600-to-work.80530/
00:24:35 <VimDiesel> Title: Solved - Getting TP-LINK Archer T2U AC600 to Work | The FreeBSD Forums
00:31:09 <sixpiece2> do you see any hope there or just return it?
00:31:34 <RhodiumToad> your device id doesn't match the one there?
00:33:04 <sixpiece2> ok thank you
00:33:31 <sixpiece2> what terrible sales people they told me I wouldn't have any comptability issues with this one they wanted to sell the more expensive gadget
00:33:41 <sixpiece2> but at least they are supposed to return it for 15 days
00:34:07 <sixpiece2> painful day today...
00:34:35 <sixpiece2> they also sold me two bad vga cords so I have to return that also and buy a new monitor at the second hand shop
00:35:17 <sixpiece2> thank you RhodiumToad
01:10:56 <ted-ious> antranigv: Your sales pitch was very effective. :)
02:30:18 <antranigv> ted-ious :)))))
02:45:46 <last1> is there an equivalent to FreeBSD's du of the --max-depth option ?
02:45:58 <last1> I want to get just the size of a directory, not its sub-directories
02:52:15 <Kalten> du -hc `find . -depth 1 -type f`
02:53:35 <Kalten> . is the directory (. for current), f is file
02:54:02 <last1> that only calculates files in the current directory
02:54:30 <last1> I want the size of all directories ( and subdirectories ) but to only show the first level name size...ugh, not sure if that makes sense
02:54:48 <Kalten> so you DO want the subdirectories too?
02:54:48 <Kalten> ah
02:54:53 <last1> right now du -kc for example shows me dir1/subdir/subdir , I want it to just show dir1 = 8G
02:55:11 <last1> I want subdirectories to be calculated as part of the main dir, but not be shown
02:55:16 <Kalten> e.g.
02:55:17 <Kalten> 200M  ,/a_file
02:55:24 <Kalten> 20G dir1
02:55:29 <last1> exactly
02:55:34 <Kalten> hmmmm
02:56:15 <Kalten> du -d 0 -hc `find . -depth 1`
03:00:35 <last1> I got it
03:00:43 <last1> du -hd1 | sort -hr
03:00:52 <Kalten> last1: does that do the trick for you?
03:02:33 <Kalten> du -hd1 does only show entries for the directories, not the files in the current directory
03:13:59 <kevans> we could use some long options in du(1)
03:15:49 <kevans> -A looks like --apparent-size; -B / --block-size, -c / --total, -L / --dereference, -P / --no-dereference, at a minimum
03:38:03 <_xor> This is so freaking strange. My WM exits when I close out a (seemingly) random terminal session.
03:38:47 <_xor> last1: Do you have to stick with du or are alternatives an option?
03:40:47 <_xor> last1: If not, then take a look at https://www.freshports.org/sysutils/erdtree/
03:40:48 <VimDiesel> Title: FreshPorts -- sysutils/erdtree: Filesystem and disk-usage analysis tool
03:46:00 <last1> erdtree looks nice
03:46:01 <last1> thank you
03:46:15 <last1> I don't have to stick to du but an already existing utility is nice
05:04:23 <zBeeble> if zfs status says "use -v to see errors" ... and then zfs status -v has no output below the errors line --- what might the error be, then?
06:24:32 <concrete_houses> its might be time to use ufs
06:25:13 <ted-ious> concrete_houses: Are you the opposite of glass_houses? :)
06:25:27 <ted-ious> Or are you by chance into dome houses?
08:50:59 <antranigv> last1 du -d 1
09:18:02 <Demosthenex> well, he doens't have to dress in basement
09:24:52 <uskerine> Hi, I was wondering if anyone is experiencing issues with firefox-esr lately, I just updated after installing RStudio and I am getting JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Can't find profile directory. The result is that Firefox does not connect to any website
09:26:13 <uskerine> well I ran pkg upgrade now and it is upgrading 400 packages
09:27:39 <ted-ious> How often do you usually upgrade?
09:28:06 <uskerine> Seems that not as often as I shall
09:28:13 <uskerine> am I expected to do pkg upgrade from time to time>
09:28:13 <uskerine> ?
09:28:58 <parv> I you do not want 400 package to be upgrade together, yes
09:29:06 <parv> s/I/If/
09:29:12 <meena> uskerine: are you on Quarterly or on latest?
09:29:37 <uskerine> I think I am in Quarterly, I am googling how to check taht
09:30:05 <ted-ious> Is that like 13.1 vs 13.2?
09:30:16 <meena> no.
09:30:17 <uskerine> 13.1-RELEASE
09:30:40 <uskerine> shall I upgrade the release?
09:31:18 <parv> ("13.1-p8") Patch 8 is still current
09:32:01 <meena> ted-ious: all releases get the same versions of packages (so long as they build) but some people are not comfortable upgrading everything every day (which is what the "latest" pkg branch gives you) and prefer to go slowly… that's the "quarterly" pkg branch, which only fixes severe bugs and security issues.
09:32:42 <meena> by default, a freshly installed system (RELEASE, STABLE) uses "quarterly". A CURRENT system uses "latest"
09:32:55 <uskerine> quarterly is my thing
09:33:10 <parv> uskerine, Do you not update the OS per security or errata announcements?
09:33:37 <meena> 😬
09:33:38 <uskerine> No I do not, unless I see something crazy around ssh
09:33:55 <uskerine> I use it as a desktop inside a LAN
09:34:33 <ted-ious> Oh ok so freebsd tests groups of patches and releases them together.
09:34:34 <uskerine> so if I do pkg upgrade frmo time to time I am fine I guess
09:34:47 <uskerine> ?
09:35:00 <uskerine> or am I expected to do something, like, when I shall move from 13.1 to somewhere else
09:35:05 <uskerine> or add a patch to that
09:47:23 <uskerine> pkg-upgrade fixed everything, both rstudio and firefox
12:05:24 <nimaje> quarterly is cut from the ports tree every quarter, so it is likely, that you get many updates after the quarter changes, but in the quarter only security fixes and bug fixes should get in there, so in the quarter you shouldn't get many updates, for latest the builders build the current ports tree
13:38:10 <uskerine> thanks nimaje
13:55:43 <mrtnt> I have a FreeBSD(PowerPC architecture) kernel core dump. "file coredump" gives "ELF 32-bit MSB core file, PowerPC or cisco 4500, invalid version (embedded)". However, if I try to open it with "gdb coredump", then I get the "not in executable format: file format not recognized" error. Any suggestions, how to analyze this further? If I open this core dump with hex editor, then for some reason it also seems to
13:55:45 <mrtnt> include some kernel ring buffer messages, content of the TLS cert files, etc
13:57:38 <CmdLnKid> might have something to do with kTLS in the kernel. last time ive ran on a G5 i had to strip that kernel down quite a bit to get it going but that was long ago
13:59:03 <CmdLnKid> eventually a faulty network card conflicted with the kernel and coredumped randomly from every 3-10
13:59:43 <meena> mrtnt: which FreeBSD version is that?
14:02:19 <CmdLnKid> as for gdb and the file you might have to set "osabi"
14:03:03 <RhodiumToad> use kgdb
14:04:27 <mrtnt> meena: it should be FreeBSD 6
14:04:51 <RhodiumToad> an oldie but a goodie
14:05:03 <mrtnt> CmdLnKid: "show osabi" shows 'The current OS ABI is "FreeBSD/kernel".'
14:05:05 * meena steps out as she's too young for this
14:06:14 <mrtnt> RhodiumToad: I tried with "kgdb coredump", but this does not seem the be different from gdb..
14:06:49 <RhodiumToad> you're opening it on the same system that crashed or on a different system?
14:08:13 <mrtnt> RhodiumToad: sorry that I didn't mention that. I am trying to open it on FreeBSD 13.1 for PPC. I am emulating it with qemu-system-ppc64
14:08:27 <RhodiumToad> ah.
14:08:27 <mrtnt> perhaps I should try with qemu-system-ppc32
15:17:05 <weust> Just a sanity check: Upgrading Samba 4.13 to 4.16, is that as simple as stopping the Samba service, uninstall 4.13 and install 4.16 and start the service? Or would I miss something crucial?
15:56:24 <weust> zfs snapshot ftw. remove and install seems to be enough. I don't use anything LDAP/AD here.
17:18:31 <last1> is there a way to set a comment/label next to a rule and/or table in ipfw ?
17:19:42 <last1> I mean, I see this in the manual:  -b	     Only show the action and the comment, not the body	of a rule. Implies -c.
17:19:51 <last1> but not how to add a comment
17:21:26 <last1> I tried: ipfw add 5 allow ip from 1.2.3.4 to any //comment but that errors out with: ipfw: pathname: //comment: No such file or directory
17:31:45 <RhodiumToad> what version?
17:32:08 <last1> ?
17:32:59 <last1> This is on 12.2 , but I mean, it's in the local manpage, it should be supported, no ?
17:33:04 <RhodiumToad> oh, I think you need a space after the //
17:33:13 <last1> let me check
17:33:31 <last1> yeah that was it
17:33:36 <last1> damn, that's strict
17:33:37 <last1> thx!
20:02:28 <Oleg> if I plug my USB 2.0 stick into a USB 3.1 slot, then I get: "ugen0.3: <SanDisk Cruzer Glide> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (200mA)" and write speeds that are appropriate for a USB 2.0 stick
20:03:23 <Oleg> but if I plug it into a USB 2.0 slot, then I get: "ugen0.3: <SanDisk Cruzer Glide> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (200mA)" and very slow write speeds (below 1 MB/sec)
20:03:26 <Oleg> why is that?
20:05:27 <rtprio> ugen.... does that present at a 'da' device?
20:06:51 <Oleg> a da* device gets created, yes; otherwise, I wouldn't have been able to test write speeds
20:07:15 <RhodiumToad> spd=FULL is usb 1 speed, not usb 2
20:07:43 <RhodiumToad> possibly the port is faulty or damaged
20:07:56 <rtprio> or your port isn't actually 2, but 1
20:08:27 <RhodiumToad> that seems unlikely, unless you have a very old hub or something
20:09:28 <Oleg> RhodiumToad: no, I don't experience this kind of problem with my other USB 2.0 stick
20:11:34 <RhodiumToad> could still be physical incompatibility between the stick and the port (just not making a good enough contact)
20:11:45 <Oleg> seriously?
20:12:09 <RhodiumToad> have you tried a different usb2 port? or a usb2 hub or extension cable between them?
20:12:33 * RhodiumToad has seen all kinds of weird usb breakage
20:13:14 <Oleg> There are two USB 2.0 slots in the front and a couple of usb 2.0 slots in the back
20:13:49 <rtprio> could it be a ... an immitation usb stick? there are some sketchy fakes on amazon
20:14:30 <RhodiumToad> if it works on usb2 in any port, then it has working usb2
20:14:57 <Oleg> if it's a fake, why do I get appropriate speeds (for a usb 2.0 stick) when it's plugged into a usb 3.1 slot?
20:14:57 <RhodiumToad> fakery is usually about capacity - having the device report itself as much larger than it is
20:18:30 <Oleg> it's a usb 3.2 slot, actually
20:20:14 <RhodiumToad> doesn't matter
20:20:15 <Oleg> but, as I said, I get normal usb 2.0 write speeds when that stick is plugged into that 3.2 port and very slow speeds when it's plugged into either one of those front usb 2.0 ports
20:20:45 <RhodiumToad> that suggests some incompatibility between the stick and the internal hub, perhaps
20:22:44 <Oleg> I have some usb 2.0 slots in the back too, but never plugged the stick into any of those slots
20:24:06 <rwp>  USB is a terrible, terrible, terrible non-standard interface. Everyone who works on USB hardware and software ends up making hacks to make it _mostly_ work.  It's likely some incompatibility between those particular bits of hardware.
20:25:59 <moonshine> i think what rwp meant to say is, usb is a standard, but it's just really bad
20:27:18 <rwp> If implemented to the USB standards one will not have a working USB implementation.  Therefore all implementations are mostly standard but then with a long list of modifications for practical functionality.
20:27:20 <moonshine> but it's like any hardware standard. just because there's a standard doesn't mean the standard is good, or that the hw manufacturer follows the spec faithfully
20:28:22 <moonshine> uefi for instance
20:29:06 <rwp> Let's throw IPSEC in there too as one of those things that would be great if one could implement it from the standards documentation.
20:30:03 <rwp> But yes UEFI is another one of those with an awful implementation history from vendors.
20:32:35 <moonshine> all the patents on firewire expired. maybe someone could pick that up again.
20:33:29 <rwp> I don't myself know much about firewire other than that the interns at Intel who invented USB didn't understand it and so did their own thing.
20:33:54 <rwp> But either way so much time has passed now that I think improving the USB situation with Firewire is no longer viable.
20:34:05 <moonshine> intel understood firewire perfectly well. they created usb to be cheaper and host-centric in their own interest.
20:34:27 <moonshine> (and succeeded)
20:34:54 <moonshine> firewire was a threat to intel because it didn't need a host.
20:35:01 <rwp> Created for detachable disk drives, used for keyboards and mice, and now expanded to be a power distribution system!
20:35:39 <moonshine> well at first it was to get rid of rs-232
20:35:49 <moonshine> but then other stuff later, yes.
20:35:55 <rwp> "Brother can you spare an ampere?" Only if you can negotiate the power protocol for it.
20:37:17 <RhodiumToad> mice were an intended use-case for usb from the start
20:37:21 <rwp> In the end we have this somewhat compatible collection of things that mostly works but sometimes does not.  If you find a combination that does not work then avoid it.  If it works then keep using it.
20:37:29 <RhodiumToad> they're the main reason why there's a low-speed mode at all
20:38:41 <rwp> As for Oleg it would definitely be good to try the rear slots too.  Those will likely be a different chip driving them.
21:11:23 <Oleg> rwp: since those additional slots are located in the back, it would be hard for me to see if they are usb2 or usb3 slots. I know that usb3 slots look blue and usb2 slots look black. I wish the front part of this tower had more than one usb3 slot.
21:13:09 <Oleg> what FreeBSD command can I type to find out if the port is a usb 2.x or 3.x if I am not able to see that "blue" or "black" thing with my own eyes?
21:13:31 <RhodiumToad> unfortunately there's no way to identify which physical port is which
21:14:06 <RhodiumToad> the only reliable way to detect whether a port is usb3 is to plug a usb3 device in and see what speed it reports
21:18:00 <Oleg> if a usb3 device is plugged into a usb3 port, then the message has to be something like " usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (0mA)"?
21:18:24 <RhodiumToad> yes
21:20:24 <kdehl> Hi! Has anyone here been able to run MedusaJS on FreeBSD? I have set up a vanilla FreeBSD 13.1 system with git and PostgreSQL 15.3, and I can create a new store, but when I try to run 'medusa develop', I get a lot of SQL errors, like "QueryFailedError: relation "staged_job" does not exist" and others.
21:20:53 <kdehl> Seems like I have forgotten something, but according to medudsjs.com, this is what I should need.
21:20:59 <RhodiumToad> that sounds like it expected you to do some setup
21:21:11 <kdehl> Of course the guides are for Linux, but I figured it should be about the same for FreeBSD.
21:21:20 <RhodiumToad> what was the _first_ error you got?
21:21:59 <kdehl> RhodiumToad: You're asking me? If so, that was the first error I got during the "Initializing defaults" stage.
21:23:29 <RhodiumToad> what exact command did you run and what guide are you following?
21:29:49 <kdehl> Sorry, got distracted by a phone call.
21:29:55 <kdehl> https://docs.medusajs.com/development/backend/install
21:29:56 <VimDiesel> Title: Install Medusa Backend | Medusa
21:30:01 <kdehl> That's the guide I'm following.
21:30:05 <kdehl> Really simple.
21:30:44 <kdehl> Maybe I should reinstall FreeBSD in a new VM.
21:30:49 <kdehl> I'm running this on AWS.
21:31:49 <RhodiumToad> the error is nothing to do with freebsd
21:31:57 <RhodiumToad> what did you do at step 2 of that guide?
21:32:33 <kdehl> I did exactly what it said. "medusa new my-medusa-store"
21:32:43 <RhodiumToad> and what happened?
21:33:16 <kdehl> No, it's not FreeBSD specific. But when I'm googing around I don't get a lot of hits on the combination of FreeBSD with MedusaJS. So I figured I should ask here and maybe someone has a hint.
21:33:22 <kdehl> That step worked fine.
21:33:52 <kdehl> It's when I go to my-medusa-store and run 'medusa develop' that I get the SQL error messages.
21:34:41 <RhodiumToad> it's expecting some database table to already exist, and it doesn't exist. so the problem is likely to be with an earlier step
21:35:34 <RhodiumToad> what other errors were there?
21:36:39 <kdehl> Hm. When I installed PostgreSQL, I had to create a super user. That is the user I gave to Medusa. Maybe the problem is there somewhere.
21:36:48 <kdehl> I'm running it again, it takes several minutes.
21:41:42 <RhodiumToad> how did you install postgresql?
21:43:07 <kdehl> pkg install postgresql15-server postgresql15-client
21:43:29 <kdehl> Then added postgresql_enable="YES" to /etc/rc.conf
21:43:51 <kdehl> And of course started it: `/usr/local/etc/rc.d/postgresql start`
21:44:25 <kdehl> Oh yeah, I had to run `sudo /usr/local/etc/rc.d/postgresql initdb` too
21:45:08 <kdehl> Then I started it as root and ran "CREATE USER pg WITH SUPERUSER CREATEDB CREATEROLE PASSWORD '...'"
21:45:31 <kdehl> Then I gave the pg user to MedusaJS when it asks for PostgreSQL credentials.
21:45:45 <kevans> er, medusa requires superuser?
21:46:32 <kdehl> kevans: I assume not, but I don't know how else to do it. I gave it some other user, but apparently it requires permissions to create a database and whatnot, so I figured I could try with the superuser first.
21:46:45 <kdehl> This guide isn't very specific.
21:46:53 <kdehl> kevans: Do you have experiences with Medusa?
21:48:22 <kevans> nope
21:49:09 <RhodiumToad> kdehl: btw,  service postgresql initdb  and  service postgresql start  are the approved way to init and start pg
21:49:26 <RhodiumToad> running the rc scripts directly is deprecated
21:49:53 <kevans> i'd probably run away from it as soon as it wanted me to give it a db superuser; you get a database with all privileges on that database, and you'll like it, damnit
21:50:29 <kdehl> RhodiumToad: Oh. Okay.
21:51:22 <RhodiumToad> did you have to specify what database to use?
21:53:03 <kdehl> RhodiumToad: I didn't. Which I found weird.
21:53:12 <RhodiumToad> did it create one?
21:53:16 <kdehl> I found this guide: https://dev.to/yinks/how-to-setup-a-medusa-server-locally-44e3
21:53:17 <VimDiesel> Title: How to Setup A Medusa Server Locally - DEV Community
21:53:32 <kdehl> It tells me to create a database named medusa_admin.
21:53:39 <kdehl> I'm trying that.
21:53:53 <kdehl> RhodiumToad: Yes, it did create a database named something random.
21:54:21 <RhodiumToad> those instructions look reasonably sane
21:54:48 <RhodiumToad> note that it's creating a non-superuser :-)
21:55:30 <kdehl> Exactly. Which is nice.
21:55:52 <kdehl> Just strange that this info is not part of the official guide.
21:56:41 <kevans> yeah now that one looks better
21:56:41 <kdehl> And whenever I ask around people are like "huh? You're not using whatever-favolrite-Linux-distro-of-the-week?! Then I can't help you."
22:05:43 * RhodiumToad is both a freebsd expert and a postgresql expert. no experience with this particular application, though
22:09:45 <Oleg> RhodiumToad: okay, it looks like I don't have this problem with my two rear USB 2.0 ports. That stick gets "spd=HIGH (480Mbps)" messages when it's plugged into them. But for some unknown reason, it doesn't like my front USB 2.0 ports because it behaves like a USB1 device when plugged into them. However, as I mentioned earlier, my other USB 2.0 stick behaves identically no matter what USB 2.0 port
22:09:47 <Oleg> it's plugged into.
22:10:15 <RhodiumToad> is the other stick from the same manufacturer?
22:11:02 <Oleg> no, the other stick is PNY and this one is Sandisk
22:11:25 <RhodiumToad> could well be a bad interaction of some sort between the hub behind the front ports and the stick hardware or firmware
22:18:54 <Oleg> but the front usb 3.2 port is attached to a separate hub? I just don't know if usb2 and usb3 ports can ever be attached to the same hub.
22:19:50 <RhodiumToad> the way that mixed usb3/usb2 hubs work is weird and I'm not sure I understand it
22:22:25 <RhodiumToad> usb2 and usb3 are actually very different beasts
22:23:01 <RhodiumToad> i.e. it's not just cranking up the clock speed, which is more or less how usb1 and usb2 relate
22:23:20 <signalblue> Does anyone seem to see that people claim that ports in FreeBSD are one of the best features, yet they are, in terms of servers, very hard to work with?
22:23:38 <RhodiumToad> no
22:24:14 <signalblue> I've done cd /usr/ports/dns/bind918 ; make config ; make clean, I think 5 hours ago, and it's still going
22:24:38 <signalblue> which is infuriating to say the very least
22:24:53 <rtprio> it's probably compiling clang or something like that
22:25:01 <RhodiumToad> was there another make in there? just doing make clean shouldn't take 5 hours
22:25:12 <signalblue> no other make in there
22:25:12 <rtprio> right
22:25:39 <signalblue> it's compiling texlive, x stuff, python stuff, and all kinds of other dependencies
22:25:55 <signalblue> make install not make clean, sorry.
22:26:12 <RhodiumToad> ah
22:26:20 <signalblue> and it's just dependency after dependency and it just never ever seems to end
22:26:22 <RhodiumToad> a lot of that will be to build docs
22:26:48 <rtprio> there are some shortcuts
22:26:52 <signalblue> because this is a two core, 768 MB RAM VM, I just sit and suffer
22:27:51 <RhodiumToad> I don't see texlive on the list, though
22:28:06 <RhodiumToad> x stuff?
22:28:18 <signalblue> I'm not joking when I say that
22:28:30 <RhodiumToad> did you select any non-default options in the config?
22:28:45 <signalblue> I just wanted BIND 9.18 with 64 bit file support and a few other add-ins
22:29:04 <signalblue> no just hit enter on all of the blue make configs for the myriad of deps
22:29:05 <RhodiumToad> ah, which add-ins exactly
22:29:16 <signalblue> let me check
22:29:44 <rtprio> `make install-missing-packages install` would probably really speed things up for you
22:30:03 <signalblue> OVERRIDECACHE, FIXED_RRSET, TCP_FASTOPEN, QUERYTRACE, LARGE_FILE, IDN. and DOCS
22:30:16 <signalblue> Maybe DNSTAP as well
22:30:58 <signalblue> and it's just been going and going in what I can only describe as dependency hell
22:31:30 <martinrame> Hi, I'm getting "Too many open files". This happens in a 13.2 Jail after running a Python program that open/close thowsands of files residing in a Windows filesystem mounted with smbfs_mount.
22:32:13 <martinrame> I would like to know how can I see what files are open, but fstat doesn't show that info, or I can't find which param should I pass.
22:32:39 <RhodiumToad> martinrame: fstat on its own, as root, should list all open files
22:33:01 <RhodiumToad> martinrame: sysctl kern.openfiles   should give you the number of open files
22:33:19 <RhodiumToad> martinrame: sysctl kern.maxfiles   is the system-wide limit
22:35:45 <RhodiumToad> signalblue: ok, I see that with all default options, bind918 has about 234 deps, including such horrors as llvm15, texlive, and a bunch of x11 client libs
22:36:02 <signalblue> horrors is an understatement
22:36:09 <signalblue> thank you for the confirmation
22:36:33 <martinrame> RhodiumToad: thanks, kern.openfiles shows 535, now I wold like to know how to list those files, because I can't see them with fstat.
22:36:34 <signalblue> freshports.org helped me verify that and yes, I dread the X stuff along with OpenJDK for things like Nginx
22:37:31 <signalblue> this is a server serving hundreds of critical DNS zones and I end up with all kinds of junk that I need to run an pkg autoremove on at the end
22:37:36 <signalblue> can't wait
22:38:20 <RhodiumToad> signalblue: a few careful settings can prune the dependency list a lot
22:38:37 <signalblue> and don't get me wrong, I love FreeBSD but this is annoying.
22:38:59 <martinrame> Mmm. kern.maxfiles: 517260, kern.openfiles: 544, something is wrong.
22:39:26 <signalblue> martinrame: I could be wrong, but that sounds reasonable?
22:39:39 <martinrame> signalblue: no, of course not.
22:40:09 <martinrame> This is a Jail, can it be the host having the rest of files open?
22:40:09 <Macer> what blocksize should i set for zfs. i'm guessing this is related to zvols
22:40:11 <Macer> in proxmox
22:40:32 <Macer> 16k good enough or should i go larger?
22:40:59 <signalblue> Oh it is a jail, sorry I missed that part.
22:41:37 <RhodiumToad> signalblue: 147 of those dependencies can be removed with one option.
22:41:55 <RhodiumToad> (turn off DOXYGEN option of devel/protobuf-c)
22:42:01 <signalblue> RhodiumToad: which option, please do tell.
22:42:36 <RhodiumToad> that gets rid of all the X stuff and llvm and texlive
22:43:10 <signalblue> which option though>
22:43:24 <signalblue> s/>/?
22:43:25 <RhodiumToad> the DOXYGEN option of devel/protobuf-c, like I just said
22:43:35 <signalblue> ohh of that dependency
22:43:48 <signalblue> it's a bit to late for it at this point
22:44:42 <signalblue> I think I will just go out for a walk and let it do it's thing
22:44:53 <RhodiumToad> honestly, given that llvm is involved, which takes nearly two hours to build on all 4 cores of my box, I'd abort it and start over
22:45:03 <signalblue> seriously?
22:45:32 <RhodiumToad> unless it's already finished with llvm
22:45:43 <signalblue> Installing texlive-texmf-20230313... is where we stand
22:45:49 <RhodiumToad> (pkg info  should tell you what it installed so far)
22:45:57 <signalblue> yep
22:46:12 <signalblue> let me initiate a new SSH connection
22:46:15 <RhodiumToad> texlive is nothing to build but it's a huge mass of files, so it takes forever to extract and stage
22:46:31 <signalblue> on Windows, TeX is the same way :)
22:46:36 <rtprio> things that build rustc, that's what ruins my day
22:46:52 <RhodiumToad> oh yeah
22:47:00 <RhodiumToad> and that new python horror
22:47:12 <RhodiumToad> (py-poetry)
22:47:33 <RhodiumToad> because that pulls in _both_ gcc12 and rust
22:47:53 <signalblue> looks like LLVM isn't installed according to pkg info
22:48:04 <RhodiumToad> kill it then
22:48:54 <RhodiumToad> you'll struggle to build llvm at all on two cores with only 768M
22:49:26 <signalblue> yes
22:50:13 <RhodiumToad> if you have plenty of swap set up then it might work on one core, but then you're looking at, what, 6-8 hours of build time
22:50:41 <signalblue> killing it as we speak
22:52:15 <RhodiumToad> you might create an /etc/make.conf   with  OPTIONS_UNSET_FORCE=DOCS  to remove some more deps
22:52:53 <RhodiumToad> not sure how much that helps in this case
22:54:14 <RhodiumToad> not as much as I'd hoped unfortunately
22:56:42 <signalblue> just going to not do DOXYGEN and save the X, llvm and texlive stuff
23:03:50 <RhodiumToad> ah, you need to force off MANPAGES as well as DOCS to really cut down the deps list, but that may be undesirable
23:04:29 <RhodiumToad> that DOXYGEN option on protobuf-c is a real menace though