01:02:02 Howdy, folks! 01:07:31 Just making a personal shell script that acts as a reconnector for catgirl. 01:08:52 Basically, it runs catgirl in a infinite loop, and after it closes, sleeps the script for 5 seconds giving me time to Ctrl+C out of the script. Afterwards it runs catgirl again. 01:11:54 https://termbin.com/0jku my bsdinstall installerconfig is getting nondeterministic network init time. any solution? 01:13:00 it's like it takes a few seconds for the network to warm up or something then traffic starts passing normally 01:13:17 but elsewhere when i run this it always works immediately 01:14:35 https://termbin.com/b264 is clearer 01:25:59 sleep 5, and it works. maybe i need to set the if to "up" somewhere? 02:00:27 common reasons to get "solaris: notice: cannot find the pool label for zroot" after an install? 02:42:16 seems i got a prob with my geli encrypted zfs 04:23:30 100py: https://forums.freebsd.org/threads/how-to-check-presence-of-a-host-in-shell-script.69582/ 04:24:46 last post best post 04:26:59 when i run ifconfig after service netif restart it says status: no carrier. maybe i need to set it to UP? 04:48:29 where'd the i915kms kernel driver go? 04:48:38 i used to use it for my mac mini to run freebsd 04:48:46 but now it says no such file or dir 04:51:49 ah nvm 05:02:52 if an interface has status: no carrier, what command makes it status: active? 05:06:17 ifconfig if up will do it 05:06:44 i guess the error im running into is the lag between when i bring an if up with service netif restart, and when its status changes from no carrier to active 05:06:55 maybe i have to embed a sleep 5 in there to deal with that 05:08:53 ok so now i just need to figure out why my geli encrypted zfs isn't booting right 12:26:17 JRiver 29 running on FreeBSD 14.1-RELEASE in Wine 9!! 13:24:26 trying to install grub for multibooting purposes, doing `sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB` gives me `grub-install: error: relocation 0x4 is not implemented yet.` 14:48:19 yabobay: did you verify that the efi partition is mounted? i don't have it in my fstab, so i have to mount it if i want to monkey around with it 14:53:58 scoobybejesus: it's mounted 14:54:51 i got my grub from the `grub2-efi` port, i hope that's the right one 14:56:10 dang, i tried. i don't have any more ideas atm 14:58:06 That looks like a repetitive bug for grub... linux/freebsd alike that has been re-appearing for several years 14:58:33 (in my initoal few minutes of searching) 14:58:59 there's a relocation patch to fix it on the linux side 14:59:09 not sure if that was added in the FreeBSD port 15:00:17 huh. so just like wait a bit for some upgrades to come out? 15:00:45 cause if so then i'm not in any particular hurry so i'm ok with that 15:01:32 yabobay: problem is who knows if its been reported/acknowledged/taken to work on 15:01:59 Tenkawa: is there any way to get freebsd's regular bootloader to recognize windows? 15:02:20 That I canot say.. I haven't run windows in 10 years 15:02:33 lucky you haha 15:03:02 I barely ran windows then heheh 15:03:17 also this isn't a support question but while i was digging around in /boot i realized a lot of the bootloader stuff is written in forth which is kinda nuts 15:03:54 why? forth is sturdy and stable like cobol and assembly... it doesn't change 15:04:15 (I am from the cobol and assembly era) 15:06:40 i'm from the right now era. was the cobol and assembly era better when it came to developing stuff? 15:07:07 It was different.. 15:12:13 bbl... time for lunch.. cheers all 15:35:45 anybody here using prometheus to monitor services on freebsd? if so, what exporter are you using for that? not seeing anything related with node_exporter. 17:11:35 phryk: Not sure how related, but I'm using node_exporter on pfSense. Seems to be exposing counters for a lot of the network stuff going on. Haven't explored "true" freebsd exporters. 17:13:31 services that I write myself, i usually put a /metrics endpoint into a/the http.ServeMux, and expose service-specific stuff there. Not sure how a more generic exporter is supposed to know what counters I'm interrested in, in a custom piece of sw 17:14:02 oh, exposing my language of choice, there. :) 17:26:04 mml: yeah, i'm not interested in the network counters (i mean i am, but for different things). what i want is a "service is running" state timeline, i.e. what 'service x [one]status' shows. on linux+systemd machines there's the `node_systemd_unit_state` metric for that – essentially i'm looking for something giving me the freebsd equivalent of that… 17:27:49 i can of course hack up my own exporter that enumerates all rc files and calls status on them but that sounds really inefficient. wondering if there's some C API that'll make this less awful, but given that rc scripts are just shell scripts… i don't think so? 17:29:48 i general, i keep coming back to the idea of writing a "libfreebsd" that directly uses any C APIs to expose freebsd-specific stuff like package states and similar info. 17:46:03 TIL libpkg is a thing 🤔 17:53:51 but, how'd you expose metrics of services running? a prom-metric is a number, with associated labels. You could of course attach a label with servicename, but that would pollute your series, heavily. 17:54:26 upservice="servicename"} would explode pretty quickly 17:54:36 up{service="servicename"} would explode pretty quickly 17:55:01 and, probably use another seriesname than "up" :) 17:59:46 are there any non-obvious power settings to consider? i have a server board with a Xeon-E and 1 nvmeplugged in. If I boot any recent flavor of Linux (defaults, no config), it idles as 29W. Boot FreeBSD, and that is around 40W. I've noticed the same with FreeBSD bhyve instances too. I can't figure out if there's something I can tweak, or if the FreeBSD kernel is just less concerned with power 17:59:48 efficiency. i've tried hwpstate_intel(4) tweaks, but nothing gets the idle as low as linux. 18:15:44 markmcb: Is fan control handled by the OS or by IPMI? 18:16:15 Xeon-E is… vague. Assume post KabyLake? 18:16:30 duncan: IPMI. Xeon E-2388G. 18:17:28 OK, I'd check if there's any difference by monitoring IPMI, but you presumably have a good idea of it assuming it's rackmount and loud 18:18:11 the fans power down for both FreeBSD and Linux after the boot process, so I don't think it's that 18:18:31 Do you have CPU frequency scaling set up, or perhaps NVMe is at a high power state? 11W is plausible in terms of combination of a few things. 18:19:02 also is this average or observed at specific points? 18:22:30 FWIW, I have X12STH-SYS and the 28W idle reported by IPMI is not accurate. More like 35-40W at the wall. 18:28:01 it's average, as reported by the BMC, checked periodically with the same results. I have a X12STH-F, so could be a reporting issues, but I poll it for both FreeBSD and Linux and see the difference. 18:29:35 haven't done anything on CPU scaling, just speedshift tweaks, e.g., dev.hwpstate_intel.0.epp=100 18:30:39 I'd graph it over 20m with a similar workload and compare. I would guess Linux for relatively new hardware like this has a power subsystem with buy-in from the manufacturer. 18:31:13 My box runs NetBSD HEAD though 18:31:44 ipmitool should report it 18:32:00 I think sdr power is the command 18:32:57 yeah, i've monitored it over several house on both OSes with no workload other than being on. 29W and 40W are the steady idle power readings I get 18:33:24 fair enough. that sounds fairly robust 18:33:58 and i've been using ipmitool dcmi power reading 18:34:07 I wouldn't expect much higher idle usage without frequency scaling, but I wouldn't be surprised if it was consequential either 18:51:38 mml: nah, that's pretty standard practice. the real problem is having stuff in labels that you wouldn't feasibly put into an enum. like URLs visited on a site. a couple dozen or a couple hundred isn't much of a problem. 18:52:44 node_exporter does it for systemd units and windows_exporter does it for, well, windows services. 18:54:03 node_exporter is directly published by the prometheus team and windows_exporter is published by the "prometheus-community" account on GH, so I consider this canonically correct and officially supported use of prometheus. 19:04:18 Howdy, folks! 19:18:32 duncan C-states? maybe. 19:29:29 maybe the timecounter too https://man.freebsd.org/cgi/man.cgi?query=timecounters&sektion=4 19:31:05 because depending on what you have set it might prevent C-states 20:03:52 phryk: Well, might just be that I haven't been exposed (!) to a big(ger) setup, so that my threshold for big and messy is somewhat different :) 20:07:55 mml: windows_exporter routinely exports like 100+ services. i think the most i've seen was around 300… :F 22:56:23 at the end of unattended bsdinstall, the debug log pops up and it says at the bottom "cannot unmount /mnt/tmp: pool or dataset is busy" so if i want to try zfs unmount -f to see if that fixes it, would i pass it zfs unmount -f /mnt/tmp or zfs unmount -f zroot/tmp? 23:01:00 yeah! clang/llvm 19 :-) 23:01:08 in current 23:04:32 nice 23:07:01 llvm20 when 23:16:30 i don't know, v20 isn't on the llvm releases page yet. I'm happy to have v19 as it makes it easier for me to build zig from source 23:17:11 thanks to dim@ and whoever helps on that 23:23:33 oh wow current llvm is 15 so ya prolly pretty big upgrade 23:45:06 looks like a busy day tomorrow, 3x sec advs 23:45:39 9for me anyway, i have lots of bhyve) 23:46:24 i wonder if any woulda been prevented with rust 23:48:18 problem with rust, at least on freebsd, is that it seemingly cant be held to a stable api 23:49:10 $thing updates? rebuild rust!! 23:49:35 curl updates? rebuild rust!! 23:50:07 ripgrep updates? rebuild rust!! 23:51:30 takes 45 mins-1hr 30 each time. a tremendous amount of energy could be saved if rust was held to a point 23:51:59 not built ports for 60 hrs? rebuild rust!!! 23:52:14 before oct23rd, llvm on freebsd-current was llvm/clang v18.1.x, now it is llvmorg-19.1.2-0-g7ba7d8e2f7b6 23:53:25 llvm doesnt need to be rebuilt all the time though. the problem with llvm is that there are 57 different versions and each port wants its own particular one 23:54:23 yeah, after freebsd switched from gcc to clang, buildworld times got pretty long 23:55:24 i stick with openbsd to my important, personal machines. at least it holds to a version, then when it needs to upgrade, everything happens at once 23:55:29 grafana port pretty old right? v10 but v11 launched 6 months ago 23:56:24 wha a beautiful 7/24 alive community this is felt like installing freebsd :) ive used years ago on my lenovo t430 for few years