00:30:59 Does etcupdate always try to build binaries when it goes to update its tree? Never seen this before: cc -O2 -pipe -fno-common -I/usr/src/crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/usr/src/kerberos5/include -MD -MF.depend.simple_exec.o -MTsimple_exec.o -std=gnu99 -Wno-format-zero-length -Wsystem-headers -Wno-pointer-sign -Wdate-time -Wno-absolute-value -Wno-empty-body -Wno-string-plus-int 00:31:01 -Wno-unused-const-variable -Wno-error=unused-but-set-parameter -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments 00:31:03 -I/var/db/etcupdate/etcupdate-JrGOU0J/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include -c /usr/src/crypto/heimdal/lib/roken/simple_exec.c -o simple_exec.o 00:31:13 Oops. Among other things, like stuff in usr.sbin 00:49:17 amigan: how are you calling it? 02:33:23 i'm starting to think that zfs on an external usb drive may not have been the best choice 04:26:27 i must be going mad, does anyone else, fresh freebsd 14 install..using xfce4 NOT have the startxfce4 command? 04:28:24 fresh freebsd install does not have xfce4; which packages exactly did you install? 04:31:12 for Christmas I want FreeBSD 14 and NetBSD 10 04:31:53 zwr: FreeBSD 14 is available today. 04:32:12 (And NetBSD 10rc1 too.) 04:33:24 Ooh, sup removed from base. =removes hat in respect= https://netbsd.org/releases/formal-10/NetBSD-10.0.html 04:33:26 Title: Announcing NetBSD 10.0 RC1 (Nov 5, 2023) 04:36:36 pkg install x11-wm/xfce4 04:36:45 yuripv: correct, i "installed" it 04:37:10 i can get it to run with exec xfesktop but the configuration file for xrdp talks about a start xfce4 file.. which i do not see anywhere 04:45:36 never mind, looks like if you invoke installing xfce in multiple ways.. you get "different" results pkg install xfce this time 04:45:46 voy4g3r2, x11-wm/xfce4-session should provide it. See https://cgit.freebsd.org/ports/tree/x11-wm/xfce4-session/pkg-plist 04:45:47 Title: pkg-plist « xfce4-session « x11-wm - ports - FreeBSD ports tree 04:46:57 vbotka: thanks, xce install identified that package 05:23:49 anyone have any idea how to get the MM keys woring on an a1243? 05:30:35 are you using x or wayland? 05:30:44 or at the console? 05:32:58 voy4g3r2: package 'xfce4-session' has startxfce4 05:41:41 /usr/local/bin/startxfce4 I copied that to my .xinitrc and startx works to start XFCE4 here. 06:51:46 meena: just etcupdate, like I always do after installworld 06:58:49 well, I updated to 14.0 and now it can't find the ZFS root 07:00:07 weird, my zroot box was fine 07:00:32 tons of other little issues though 07:02:39 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275336 for one, and lots of weird stuff in my kernel messages. And just now I ran ifconfig and I got "ifconfig: getnameinfo: Address family not recognized", and ran it again and it was fine 07:02:42 Title: 275336 – Processes exiting with SIGSEGV on shutdown on ZFS systems 07:03:24 "module_register_init: MOD_LOAD (sctp, 0xffffffff80a8c870, 0) error 17" on boot 07:04:06 something to do with the kernel. The old 13.2 kernel works. Btw I have to compile a custom kernel because my wi-fi card's driver is GPL. My kernel config is this: https://paste.debian.net/plain/1300309 07:04:43 did I miss a step for people with custom kernels? btw it's an encrypted install so it's ZFS on top of GELI 07:05:30 I see no reason it shouldn't work as it did before 07:06:26 But I have also never booted zfs on geli, not sure what is entailed in keying up the kernel so you can see the pool 07:46:43 I guess I stay on 13.2 for now, I only use that laptop for testing programs on FreeBSD 08:01:03 I broke apt in a linux jail :P 08:01:15 wait, it may be fixable lol 08:01:29 elsewise I want to see if I can install something like arch in a linux jail 08:04:55 amigan: try this https://man-dev.freebsd.org/etcupdate#B 08:04:56 Title: etcupdate(8) - FreeBSD Manual Pages (Dev) 08:09:31 otis: IIRC you know a bit about fibre... 08:11:23 dch: yes, a bit, yes :-) you mean storage or ethernet? 08:11:43 ethernet in this case 08:12:03 that's more of a simple case. 08:12:19 I planned a fiber upgrade at home here, and unexpectedly picked up a couple of 100G chelsio NICs at bargain basement prices 08:12:43 so now I am wondering whether that changes the fibre type I need 08:13:00 singlemode should do 08:13:01 OS2 08:13:17 nazxar vbotka 08:13:26 dch: what's the card type? 08:14:02 originally I was going for OM4 but it seems SMF is the way to go 08:14:31 Chelsio T62100-LP-CR https://store.chelsio.com/products/t62100-lp-cr-high-performance-low-profile-dual-port-40-50-100gbe-unified-wire-adapter-with-pcie-3-0-x16-interface 08:14:32 Title: T62100-LP-CR: 2-port Low Profile 40/50/100GbE Unified Wire Adapter wit – Chelsio Online Store 08:14:32 yes, i prefer SMF, too. when there's no other way, also MMF would do, ofc. 08:14:55 ok, qsfp28, thought so. you can buy qsfp28 with either mmf or smf, i'd suggest smf. 08:15:38 smf has longer reach, is not so prone to attenuation... 08:15:53 initially I am going to use 25Gb SFP28 because they are significantly cheaper than the 100Gb ones 08:15:57 fwiw https://www.fs.com/c/100g-qsfp28-1159 08:16:02 Title: 100GbE QSFP28 Transceiver Modules | Optical Transceivers - FS.com 08:16:21 the total length is ~ 40m 08:16:52 yeah my fs.com person already recommended some compatible parts, its very handy to check with them 08:17:21 nazdar otis 08:17:47 we even got some kind of a "partnership" for slovak republic. our sales person gives us slightly better prices. 08:19:28 hey vbotka! I've seen your really awesome ansible modules. nice to see you around here 08:19:51 yeah, vlado's ansible playbooks are neat, indeed. 08:20:29 some folks asked me if therw would be an interest in attending a FreeBSD Users Group meeting in eastern Slovakia during summer (they aimed to organize it in that case) 08:21:23 Thank you for comments. Nice to see you too! 08:21:51 I would come, if it lined up with my dates 08:22:00 (family holiday plans) 08:23:05 otis: I think my electricians could probably put in an actual patch cable directly, a 50m run would be ideal. there's a tube in the building already for this stuff. 08:23:34 dch: good for you then! 08:25:20 otis: thanks for the advice, I owe you a few beers! 08:25:34 few coffees :-P 08:29:58 otis: any other tips you can think of? I am planning 2 get a couple of these https://www.fs.com/de-en/products/177394.html?attribute=700&id=1786819 08:30:02 Title: 50m (164ft) LC UPC to LC UPC Duplex OS2 Single Mode PVC (OFNR) 2.0mm Tight-Buffered Fiber Optic Patch Cable - FS.com Europe 08:31:19 dch: that's good choice 08:31:56 care should be taken to not tear the connectors off while laying the cable 08:40:18 mason: what was sup used for in the past two decades? 08:49:31 either I am dreaming or p2 has fixed my vnlru woes 08:52:26 Remilia: i think you are not dreaming, looks related? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275063 08:52:28 Title: 275063 – kernel using 100% CPU in arc_prune 08:53:05 yuripv: how do I get top to show that {threadname} thing? 08:53:23 mine just says kernel 08:53:44 top -H? 08:53:47 but otherwise percentages look similar, aside from vnlru taking 40-70% for me 08:54:02 top -SH maybe? 08:54:06 thank you! 08:54:11 never noticed that option before 08:54:13 ah ok yuri already responded. 08:54:43 -H also goes for ps 08:54:45 wow that is a lot of time in epair_task, I should probably see if netgraph is faster 09:07:21 Thanks otis 09:41:55 tsundoku: if you haven't solved it yet, i think it will be helpful if you can paste a full netstat -rnf inet output from the jail and host, ifconfig of the relevant interfaces, and tcpdump output from both sides of the epair, the bridge, and the vlan (and maybe the external interface), from the moment that you emit the ping 09:42:54 someone on LQ called KDE 'snappy' and I laughed pretty hard... 09:47:46 hello, any idea why colours disapeared in cmus when upgrading to 14 ? (tmux, rvxt-unicode, and TERM set to screen-256color) 09:57:50 mage: which command lost its colors? 09:58:25 ah ic cmus obviously 10:09:44 elliottp: yeah. 10:10:04 it's strange, neomutt works, cmus not 10:10:51 although they depend both on the same libncursesw.so.9 10:17:05 Address resolution failed for http://pkg.FreeBSD.org/FreeBSD:14:amd64/quarterly. 10:17:05 Consider changing PACKAGESITE. 10:17:08 why? WHY? 10:18:46 AumShivaya: ping pkg.freebsd.org 10:18:52 yeah, it doesn't 10:18:58 ping 1.1.1.1 10:19:32 root@ubuntu:/ # ping 1.1.1.1 10:19:32 ping: ssend socket: Operation not permitted 10:19:40 theres yr problem 10:20:26 yeah, perhaps p4.addr="192.168.1.150" is wrong? 10:20:36 does that have to point to my router address or is it just that? 10:20:52 I just copy and paste from the handbook that 10:20:55 if yr router caches dns then yes 10:21:20 well I set up my resolv.conf the same in side the ubuntu jail 10:21:48 but your problem here is "dns isnt working" and not "pkg is unreachable" 10:21:50 how do I change the settings once the jail has been created with jail -cm? 10:21:54 yes 10:22:40 i dunno about jails. but i think you have to set the jail up to allow networking 10:22:55 I am just learning, trying to follow the handbook 10:23:00 there might be a sysctl somewhere 10:23:14 sysctl -a | grep jail 10:23:38 what am I looking for? 10:23:53 https://docs.freebsd.org/en/books/handbook/jails/#creating-linux-jail 10:23:54 Title: Chapter 17. Jails and Containers | FreeBSD Documentation Portal 10:24:24 security.jail.allow_raw_sockets i guess - but I don't know security implications of those 10:24:42 yeah saw that 10:25:18 https://forums.freebsd.org/threads/allowing-raw-sockets-in-jails.86868/ 10:25:19 Title: jails - Allowing raw sockets in jails | The FreeBSD Forums 10:25:37 https://www.cyberciti.biz/faq/configuring-freebsd-12-vnet-jail-using-bridgeepair-zfs/ 10:26:27 nah I set raw sockets to 1 10:26:32 and chrooted back in 10:26:42 and still cannot ping 1.1.1.1 or pkg.freebsd.org 10:27:05 outside the jail, can oyu ping 1.1.1.1 10:27:14 sure can 10:27:24 im baffled then 10:28:09 aye 10:28:19 thanks for your help. Perhaps someone else may speak up soon 10:28:52 try subscribing to -questions and posting there? or the forums, or both 10:33:38 could do soonb 10:33:40 soon 10:33:40 brb 10:45:43 so the line ip4.addr= 10:45:50 I put in the address of my wifi 10:45:59 and it stopped all my networking I had to reboot 10:47:47 bear in mind more ppl will be on here later (seems most ppl are utc-5 to utc-8) 10:49:46 also try creating a freebsd jail 1st, and if that works then the issue would be specifically with the linux jail 10:51:29 which one? thin? 10:51:37 thick 10:52:37 one with all the bells and whistles. if it works you have a linux-in-jails problem. if not, a jails-general-problem 10:54:10 ok shall give that a go...bbl 11:15:23 Anyone else getting "No valid device tree blob found!" when booting -CURRENT on arm64? 11:52:12 how do you look at the not install packages 11:59:29 maybe https://ports.freebsd.org/cgi/ports.cgi 11:59:30 Title: FreeBSD Ports Search 12:01:19 i just use pkg dont use ports 12:03:44 freshports also lists the available packages 12:37:52 richard_: `pkg search` `pkg rquery` 12:40:11 e.g. `pkg search -Qfull ` would provide all needed details about *not* installed package 13:06:25 richard_: pkgs are build from ports 14:44:06 hi all 14:56:59 does anyone use usb microphone? 14:57:31 i noticed volume issue. It is not loud enought 14:58:11 and as I understand it isn't microphone failt but a driver. Another guy says the same on his video. 15:01:44 wikan: i assume volume is at 100, when running 'mixer'? 15:05:32 wikan, sure it's not a hardware issue. . . ie. a volume rocker on the microphone? 15:21:38 meena: I bet sup has not been used in that stretch. Even I was using cvsup. But it still marks an era. 15:22:07 mason: I wonder how their transition to hg is coming along 15:23:06 I believe it's stalled, last I knew. 15:27:54 well it is not hardware issue 15:28:44 i am not only person with the same problem. Other microphone but usb type 15:29:27 volume is 100% but works like 35% 16:00:42 What's that CLI volume level tool? 16:00:45 Been a while. 16:01:00 Think it's part of base. 16:07:21 hmmm 16:07:27 mixertui 16:07:53 and it works up to "35%" 16:08:00 Oh, nope - just mixer(8) 16:08:31 What does it say your volume is at? 16:08:56 hi all. trimming zpool ssds is easy: zpool trim pool. How to trim a ufs ssd? 16:08:58 mixertui is a tui as the name says 16:09:00 wait, must check 16:09:35 mixertui is a port though. 16:10:39 Been a while, since I had a FreeBSD workstation, but I would toss a mixer command in my /etc/rc.local to set the levels where I wanted them on each boot. 16:11:39 mic/rec 96:96 95:95 16:12:02 f451: fsck_ffs has an -E option to trim unused storage. i've never tried it though 16:12:21 unixwitch: thanks 16:12:49 audacity prints my voice wave up to maybe 30% 16:12:55 hi, i fucked up and let freebsd-update completely fill my zfs disk. now i can't even remove files to free space? 16:12:59 if i am close 16:13:18 problem im having is a GIS returns old docs, and I know stuff has changed in the last couple of years 16:13:35 ascreen, zfs list -rt snapshot -o name,used,refer,clones 16:13:53 you may have a snapshot or two that will free up a bunch of space 16:14:01 i deleted a few snapshots, zpool list says i have 393M free 16:14:05 f451: trim(8)? 16:14:11 but the fs still say AVAIL 0B 16:14:46 What does df -i say? 16:14:59 zroot/ROOT/default 9612024 9612024 0 100% 568182 0 100% / 16:15:10 so inodes are full too? 16:15:17 but i think zfs doesnt preallocate inodes 16:15:20 Well.. .. probably first. 16:15:30 That I dont' know. 16:15:33 anyway, i can't even truncate some file i have laying around 16:15:37 zapata: checking ... didnt realise htat was there. old docs suggest its enabled at newfs time 16:15:58 also 500k files isnt that much 16:16:12 What does mount -p say? 16:16:33 zroot/ROOT/default / zfs rw,noatime,nfsv4acls 0 0 16:16:37 and some other stuff 16:17:00 Does ZFS not re-allocate inodes? 16:17:39 That'd be important to know for certain, 'cause 'df -i' says you're out of them. 16:17:54 well i guess it means it can't create new inodes 16:18:06 e.g. touch fails too 16:18:22 Well, every file, no matter how small, needs an inode. 16:18:50 So if you're out of them, the volume is "full." 16:18:53 yes, but a classical fs would have some inodes allocated and could create an empty file even if disk is full for blocks 16:18:58 but i think zfs doesnt do that 16:19:22 i just dont get why zpool list says a little free space yet it's not used 16:19:38 Can you delete a file and see if inode count decriments by one? 16:19:44 no i can't delete a file 16:19:50 else i could just clean up the old freebsd-update stuff :D 16:20:12 You in single user mode? 16:20:28 no, regular boot. but nothing else is using that machine 16:21:19 ok, i have an idea. perhaps deleting a file that is not in any snapshot helps 16:21:34 no :< 16:22:11 Maybe 'shutdown' to single user mode, make sure that / is still mounted rw and try 'fsck -y /' 16:23:11 f451: note that trim(8) will trim the entire device (i.e., erase all the data), at least by default, which probably isn't what you want 16:24:51 phew, deleting a newer snapshot helped 16:30:26 deleating a file that is part of a snapshot too won't help, as the snapshot prevents removal from disk, you should be able to delete anything that isn't part of a snapshot and some old snapshot could maybe prevent some big file from being removed from disk 16:32:10 yeah, the problem was that freebsd-update created a new snapshot :) 16:37:37 unixwitch: yeah. i think i can sort it by fsck_ffs -E -y then enabling tunefs -t then running the fsck_ffs -E again all while in single user mode 16:38:08 trim(8) seems to be a little different! 17:24:55 any dhcpcd users? 17:25:10 I'm struggling with the manpage to get it to do what I need. 17:26:44 CrtxReavr: what do you need? 17:27:08 CrtxReavr: also note that you can ask questions on the Github discussions, and it's usually very responsive 17:27:29 Well, I have an ISP facing interface that I need to do v4 DHCP on and v6 DHCP-PD. 17:28:26 Then I need to configure /64s from that PD on some internal-facing interfaces. . . which I don't necessarily need dhcpcd to do, but I do need the prefix. 17:30:35 *nod* *nod* 17:30:47 I think maybe you could pass that off to… something else. 17:37:34 ok, i have one more dumb question... the system says in zfs list: zroot/var 3.64M 7.73G 96K /var 17:37:41 however, /var isnt mounted? 17:38:06 ascreen: looks mounted 17:38:09 and thus the whole /var/db stuff ended up in zroot/ROOT/default 17:38:20 mount doesn't list it 17:38:21 Right. /var and /usr are usually not mounted. Run this: zfs list -o name,compression,exec,setuid,atime,canmount,mounted,mountpoint 17:38:41 The canmount will say off for some of those. That's by design and intentional. It supports Boot Environments. 17:38:57 so what is intended to be snapped by a boot environment? 17:38:59 But other datasets are mounted under those directories. 17:39:13 ah, 17:39:15 Yes. So that things that must keep moving forward keep moving forward. 17:39:31 And things that need to be able to snap back to a previous snapshot can be reverted if needed and everything works. 17:39:41 yeah /var is canmount no, mounted no 17:39:52 So /var/log for example needs to keep moving forward. So it is an explicit dataset mounted under /var 17:40:38 It's confusing at first glance until it is understood that /usr and /var set up an inheritance for other things to be created but those directories themselves are held by the zroot/ROOT 17:41:21 I saved this off a while back: https://forums.freebsd.org/threads/why-are-usr-and-var-not-in-a-boot-environment.59844/ 17:41:22 Title: ZFS - Why are /usr and /var not in a boot environment? | The FreeBSD Forums 17:42:07 And with that I must run afk but I saw this discussion in the channel and had to jump in! Sorry to barge in and then run off. 17:42:23 well thx :) 18:23:24 I have a 14.0p2-RELEASE installation on bare metal that can't boot until plugged into a monitor. xorg, sddm (did this give me plasma?), a couple xf86, and drm-kmod are installed, among others, if it matters. anyway, i tried in /boot/loader.conf setting console to EFI or even nullconsole. i searched on various dmesg items, and none seem related that I can tell. any ideas for making this boot even if not plugged into HDMI? 18:23:57 i wanted to learn to set up a desktop, and finally succeeded, but this will be a headless box 18:28:22 FYI for all the people who were puzzling over my bridge problem yesterday: the issue was that my rc.conf order was wrong. 18:29:53 I had cloned_interfaces=" " below ifconfig_bridge0=" " because I had some kind of problem earlier with it above, and I read something that led me to believe cloned_interfaces was not creating anything, just indicating to the OS which interfaces were virtual. that was not correct. 18:33:29 scoobybejesus: can you elaborate on "can't boot"? where does it stop booting? do you see anything relevant (like errors) if you connect a monitor after it fails to boot? 18:33:33 scoobybejesus: can it boot anything else without a monitor ? 18:34:14 I had a crappy motherboard that wouldn't post without video output 18:34:25 tsundoku: that's odd since order of directives in rc.conf shouldn't make a difference to anything... the whole is read in whole and doesn't affect the order services/devices are started 18:34:34 s/whole/whole file/ 18:34:57 i wish i could be more specific. what happens is i am ssh'd in, so i do doas reboot, and then i can't ssh in again. so i plug in the monitor, and a few seconds later, things populate and it finishes booting 18:35:24 does it beep? :) 18:36:01 either i turned off beeping, or it never beeps. i don't recall. perhaps i could pop into the bios to enable it 18:36:30 scoobybejesus: if you disable sddm from starting, does it boot correctly then without video connected? just to isolate the problem 18:36:49 i will give it a try :) 18:37:21 tsundoku: rc.conf order should not matter, these are environment variables 18:37:22 (i don't know anything about sddm, but at least with xdm, the dm is responsible for starting X, so it's at least theoretically possible that if it can't start X for some reason, it might interrupt the boot process... this is just a wild guess though) 18:37:50 .. 18:37:59 . 18:38:26 apparently the order does matter, at least for networking stuff 18:38:57 tsundoku: if you look at the rc.d scripts all they do is check variables 18:39:03 tsundoku: it really doesn't... it can't matter. the rc scripts in /etc/rc.d are run in a specific order based on their dependency requirements, and they always read the entire /etc/rc.conf... the problem is almost certainly something else 18:39:15 they source the conf file, then use values 18:39:27 well, putting cloned_interfaces above the other lines apparently fixed it, because it's working now 18:39:30 well unless you were setting and then using $variables in rc.conf in some reason, in which case order would matter, but... 18:39:54 one thing i noticed is that the way i have things now in loader.conf (console="nullconsole"), one section of booting populates a block in the center of the screen which ends in saying it's Loading /boot/loader.conf. Then FreeBSD logo. Then it uses the monitor normally, putting everything in the top left and prints down the lefthand side. This part starts with "Setting hostuuid." Continued.. 18:40:24 When I reboot without the monitor attached, and it hangs, and i eventually plug it in, this is always the first line i see once the monitor comes up 18:40:25 tsundoku: chances are you first renamed the interface then used cloned with the new name 18:40:31 tsundoku: either you fixed the issue by accident, or you have some sort of timing-dependent problem that fixed itself by accident somehow 18:42:01 this might just be me but did 14.0 have more ENs than usual for a .0 release? 18:42:31 yes, disabling SDDM allowed for a normal, speedy reboot :) 18:43:39 <- still loves startx 18:43:59 scoobybejesus: i would be inclinced to just leave it disabled then, and use `service sddm onestart` if you really need it for some reason 18:44:28 I am impressed it goes in rcorder before sshd 18:44:44 although it is odd it breaks the boot process, even if X can't start it should just background and keep trying, not break the entire boot process 18:44:53 it would be nice to know more, but yes, this is definitely suitable for now. thank you unixwitch 18:45:49 my other suggestion would be to switch to xdm, which has worked fine for 30 years, idk why we need all these new fancy things (back in my day, etc. etc.) 18:46:11 unixwitch: So what would you do if trying to start it 5 times in a row failed? Try another 1000 times? 18:46:13 tsundoku: if you do something like: create_args_bridge0="name brj" cloned_interfaces="brj" it will not work 18:46:37 what I have now is like 18:46:40 it will create brj, but what kind of interface it will be is ??? 18:46:42 cloned_interfaces="bridge0" 18:46:44 and then 18:46:46 armin: yes? i mean, i suppose it could also just log and error and quit, which would be fine too. but it shouldn't do whatever it's apparently actually doing. 18:47:17 unixwitch: There's something about trying the same thing over and over and expecting a different result... 18:47:41 ifconfig_ixl1="up" and then ifconfig_bridge0="addm ixl1 up" 18:47:46 that's it 18:48:09 tsundoku: and the order would not matter 18:48:18 it appears to matter 18:48:27 it cannot, sadly 18:48:36 hmokay https://hostit.tfnux.org/obj/wsz62a3y5exnozajqpo7m45qgu5j4jtf/paste.txt 18:48:37 armin: i really have no interest in how sddm handles X server startup failure, my point was that it should handle failure in some way that doesn't break everything else 18:48:49 I had a friend look at it who discovered the problem and what he said was that cloned_interfaces is what creates the bridges 18:48:55 tsundoku: rc scripts source defaults/rc.conf and rc.conf 18:49:03 as variables 18:49:05 no, /etc/rc.d/netif creates the bridge 18:49:15 cloned_interfaces is just configuration, by itself it doesn't do anything at all 18:49:35 the rc scripts do not read rc.conf line by line like some interpreted language 18:49:45 unixwitch: yeah, fair point, I've seen that on Linux, systemd trying to re-start X, X crashes, re-start X, X crashes, and so on. Try to switch to a TTY and log in while that happens. Fun. 18:49:48 the other thing I was told was that from FreeBSD 13, interfaces default to down on boot 18:50:07 are you sure it is from 13 18:50:18 and not like 2.2.1 18:50:48 *shrug* 18:50:50 though it has been a long while so I may be misremembering 18:51:05 tsundoku: `less /etc/rc.d/netif` and educate yourself 18:51:12 it is a shell script 18:52:56 yeah 18:53:09 well all I can tell you right now is that changing the order of things in rc.conf resolved the issue 18:53:16 Remilia: i'm pretty sure every Unix system since forever has defaulted interfaces to down... right? unless maybe there was some weird special case where cloned_interfaces would be brought up by default or something (but i honestly don't remember that ever being the case) 18:53:25 unixwitch: aye 18:53:39 tsundoku: switch their places and reboot and you will see that nothing changes 18:53:43 something something the interfaces were getting added to the bridge in a down state and I guess trying to bring them up after the fact does not work 18:54:21 tsundoku: it does work (i've recently tested that since i've been configuring some jails) but it is true that they will be done by default, which is fixed by ifconfig_xxx0="up" 18:54:22 you had the bridge renamed 18:54:30 s/be done/by down/ 18:54:44 like, I remember very well that your bridge was called svcbridge 18:54:49 yes 18:55:10 so swapping the order was not the only change 18:55:19 well I'm still renaming the bridge 18:55:43 ifconfig_bridge0="addm ixl1 up" should not work if you renamed the bridge in rc.conf 18:55:46 but in troubleshooting we took out the rename for expediency and then put it back after it got sorted out 18:55:55 tsundoku: it's up to you, but i would suggest editing rc.conf to move cloned_interfaces after ifconfig_ (or whatever) and rebooting just to see what happens. i'm 100% sure it'll still work, if it works now. 18:55:56 so the rename doesn't appear to have affected anything one way or another 18:56:06 because by ifconfig time interfaces are already renamed 18:56:08 then why didn't it work before? 18:56:23 i have no idea, unless you have a backup of the non-functional rc.conf to compare, who can say 18:56:30 ^ 18:56:39 basically there is no magic in `. /etc/rc.conf` 18:57:44 well, maybe I'll lab it out sometime later if I get really curious 18:58:00 tsundoku: /etc/net.subr processes the cloned_interfaces in clone_up() 18:58:06 on this machine I kind of just want to move on 18:58:14 it literally goes `for ifn in ${cloned_interfaces}; do .....` 18:58:31 /etc/net.subr? 18:58:37 network 18:58:42 i recommend testing it just because this is fairly important to understand how /etc/rc works in freebsd. but like i said it's up to you so -shrug- 18:58:50 doesn't exist on my system 18:58:57 how can /etc/network.subr not exist 18:59:07 what did you do to it 18:59:18 oh, I misinterpreted what you were saying 18:59:40 if you look at that file you will see that it only accesses shell variables 18:59:46 and never tries to read rc.conf line by line 19:00:09 makes sense 19:00:14 kind of related, i've always avoided renaming interfaces because i've never been entirely sure what rc.conf variables are used prior to the rename and which are used after... i should probably go work that out at some point 19:01:05 yeah, I really wanted the rename because I was like... if this is a virtual object that I'm creating deliberately on my own, I want the name to be desctiptive and not just like bridge0 19:01:08 unixwitch: cloned first, then rename 19:01:35 I mean, if you are renaming via create_args, it would be after cloned 19:01:37 Remilia: so ifconfig_ is already after? (like if i want to rename then add to a bridge) 19:01:42 s/already/always 19:01:53 ifconfig_ lines operate on existing interfaces 19:02:33 unixwitch: look at netif, it goes # Create cloned interfaces \n clone_up $cmdifn 19:02:43 then # Rename interfaces 19:02:50 then # Configure 19:05:35 yeah, that makes sense. ok, now i just need to sit down and come up with an overengineered and needlessly complicated if naming scheme 19:08:23 you usually want somthing like 19:08:23 cloned_interfaces="vlan0" 19:08:24 ifconfig_vlan_name="myvlan" 19:08:24 ifconfig_myvlan="inet 100.64.0.1/16" 19:08:24 but the order of the lines doesnt matter 19:10:39 yep 19:10:58 what do people like for automatic zfs snapshot management? zfs-auto-snapshot, zfs-periodic, zfs-snapshot-mgmt? 19:11:09 tsundoku: the reason I was trying to explain this to you is to prevent more weird voodoo spreading 19:14:36 i used sanoid for snapshots. the config file is easy enough for me. put it in cron. done 19:15:31 scoobybejesus: thanks, never heard of that one 19:15:48 it comes bundled with syncoid which makes off-site replication easy as well 19:25:52 my kernel spends 3% of a core in epair_task hahahaha 19:27:34 mine is spending 700% cpu in "idle"! what a terrible waste of CPU 19:28:12 Remilia: fwiw i remember reading recently that epair sends all packets through a single taskq which seems not great for scalability 19:30:14 that's odd, why does my 2023Q4 poudriere have 209 ports queued? does an update to pkg rebuild everything? 19:36:26 unixwitch: no but if you updated a jail it kills everything 19:37:01 oh, that's probably it then since it just updated to 14.0-RELEASE-p2 19:37:19 maybe i should disable jail auto update on build, i doubt it makes any difference to the built packages in 99% of cases 19:41:05 I think the reason is this 19:41:05 https://www.freebsd.org/security/advisories/FreeBSD-EN-23:15.sanitizer.asc 22:37:41 nimaje yeah i see that