00:00:21 meena: if you wanted to build a source package today, for a system using quarterly packages, would you built from 2023Q4 or 2024Q1? 00:00:44 the correct answer is 2023Q4, because 2024Q1 binary packages aren't ready yet. but how is an end-user meant to know that? 00:00:59 I… would not build packages for quarterly… i am using latest everywhere, 00:01:24 sure, but most people (who use binary packages) are using quarterly 00:01:39 that sounds fake 00:01:55 like, most dogs who go outside do that for eating slugs 00:01:58 i will stand by this fact, since quarterly is the default 00:02:03 (that's probably just my dog) 00:03:13 It's the tyranny of the default. I mostly use pkg, which defaulted to quarterly, having no reason to change it I have not, I am still on quarterly. It's been fine. 00:05:38 i wish ports could build subpackages. like pulseaudio and pulseaudio-jack 00:05:49 this would solve a *lot* of cases of building from source 00:06:00 * meena maintains like, one port and likes it shows up after updating it, and not after updating it + 3 months 00:06:19 unixwitch: oh! ooooh!!! subpackages *just* landed. 00:06:34 <_xor> sub-packages? 00:06:48 meena: oh really, i saw something about this but i thought it was for pkgbase for some reason 00:06:57 if this is true it might be enough to get me to switch back to packages 00:08:51 https://reviews.freebsd.org/D40549 00:08:52 Title: ⚙ D40549 Subpackages! 00:08:57 hm, www/qutebrowser says it's like vi, so i tried :q to close a tab and it quite the entire program 00:09:19 <_xor> :bd 00:09:29 the previous review https://reviews.freebsd.org/D16457 has examples of how to use it 00:09:30 Title: ⚙ D16457 Subpackages. (deal with it.) 00:10:46 "Subpackages. (deal with it.)" darned greybeards, eh 00:11:33 meena: this looks great, i hope everything gets updated to use it this week! 00:12:45 it's already friday here, and that means two things: I need to bring the dog out for a piss before going to bed, and then try to sleep 00:13:41 <_xor> So do subpackages basically mean that a package can be built as a single unit but broken out piecemeal during install/deinstall? 00:13:58 <_xor> Oh 00:14:03 * _xor just looked at the 2018 issue by mat 00:14:04 _xor: it means you can build a single piece of software and create multiple packages from the files it installs 00:14:23 so instead of using on/off OPTIONS, you just build mypackage, mypackage-foo and mypackage-bar 00:14:43 most importantly, you can break out docs/man pages 00:14:57 so if you're installing tiny … things, you can leave those out 00:15:04 i actually don't care about that but i can see it would be useful for embedded systems 00:15:17 everyone benefits! 00:15:29 <_xor> That would be very nice, yes. I currently build without DOCS generally (since I install a lot of packages on my servers), and just use the web for docs when needed. 00:15:48 although, i hope there's a way to automatically install man packages? 00:16:00 <_xor> Every once in a while I think about rebuilding the repo with DOCS set, which would probably take up a 1-2 days. 00:16:03 think headers, docs, man pages, etc… you can build really tiny jails. I can now see why this is pushed to conclusion by pizzamig, they work on pot 00:16:43 maybe i'll make a patch for pulseaudio to do this, but otoh, i feel like whoever maintains that is probably already doing it? 00:16:47 <_xor> The smallest base-runnable jail I built was around 18mb, I think. 00:17:15 unixwitch: this is desktop@ and they are buuuuuuusy… so any help is appreciated, I reckon 00:17:24 _xor: *nice* 00:17:37 i feared i might need to sub to desktop@, my poor inbox 00:17:37 i think dfr's are even tinier, somehow. I don't know how 00:17:53 <_xor> I don't use it though, because so many packages rely on more than just that 18mb from PkgBase. 00:18:04 <_xor> With sub-packages though, I might be able to do so. We'll see. 00:18:11 unixwitch: i am subbed to wireless, for some reason, and I don't even run FreeBSD on my laptop anymore (because I bricked it) 00:18:51 meena: laptop under warranty? 00:18:53 <_xor> It's going to really help with packages like www/nginx though. Break out all of those modules and their individual dependency trees. 00:19:30 kenrap: not by a decade, also it's not a real brick, only a metaphorical one, because it's heavy work making it not-a-brick without complete reinstallation 00:19:41 AH 00:20:14 _xor: yeah. i hope postfix can benefit from this too although i suspect postfix builds this into its main executables 00:20:47 oh, yeah, i remember mwl complaining about this 00:21:00 <_xor> Heh, I remember when I was younger I got the components to build a new system. It was an older AMD CPU, one of the ones that ran *really* hot. I was really excited to get a new system. 00:21:39 <_xor> Put the thing together and I wanted to check that it would actually power on without issues, and without thinking, I turned it on...without the CPU cooler installed. 00:22:07 Apparently the new ryzen 7000 cpus run very hot even though they're very energy efficent 00:22:20 <_xor> It was dead quite, the fan spun up for a second, and then I watched a tiny puff of smoke rise off of the CPU, and then the system died. 00:22:34 <_xor> It was dead quite for a solid 5 seconds after that, with me just staring at the (now dead) CPU lol. 00:22:37 _xor: i did that once too. *once* 00:22:51 i can't get my Ryzen 5800X3D to go over 60C no matter how many poudriere builds i run, but i think this is because the X3D parts have a lower boost clock 00:22:57 <_xor> lol I still laugh when I think about that. 00:23:14 unixwitch: join a google meet 00:23:30 Or a zoom meeting 00:23:36 meena: never. but i might need to find out if Teams work on FreeBSD at some point... 00:23:42 brrrrr 00:23:46 how is *that* better? 00:23:48 (or else figure out how to pass the mic through to my bhyve windows vm) 00:23:55 meena: it's not but it's what we (and all our clients) use :-/ 00:24:20 The X3D gives it more cache, so maybe the cpu doesn't have to work as hard? 00:24:45 kenrap: i think the issue is the extra cache is on top of the CPU die (that's the 3D part) and they don't want to fry it by dissipating too much heat through it 00:24:56 Ah, haha 00:36:41 ok, most difficult problem of today, how the heck do i tell alacritty to open links in qutebrowser instead of firefox. this is some xdg crap, isn't it 00:39:07 ah xdg-settings 00:39:17 why can't we just use .mailcap for this smh 00:42:43 freebsd survey is about to close, if anyone cares (and didn't already do it) https://www.surveymonkey.com/r/freebsdsurvey24 00:42:44 Title: FreeBSD 2024 Community Survey 00:42:45 mailcap is for mime things 00:49:01 I would like to see the results of the survey 00:51:46 (already done it a while back) 01:08:03 kenrap: I reckon you will read about it in the next status report, at the very latest 01:30:01 rwp: xdg-open is also for mime-types, it just gets abused for url schemes by using fake mime-types 01:30:08 rwp: ok well maybe not mailcap, but there should be a plain text file for this 01:30:15 Probably not the next one, which should come out sometime this month, but the 1Q2024 one, in April. 01:30:35 i am confused that there's been a resurgance of non-"desktop" applications in X/Wayland, but everyone still relies on this xdg crap. even Sway needs it! 01:31:29 I replaced xdg-open by my own script, because I didn't want to run that code 01:31:48 hmm, that sounds like a good idea for a port 01:33:03 well, the settings are instde the script, because the handlers are python functions https://0x0.st/H6vN.bin 01:33:22 My onboard sound sucks. I want to get a proper dedicated Sound Blaster card. Sadly I have only 2 PCI-e slots. One is used by wifi+bluetooth card. THe other, obscured by graphics card. Sadly, I do not think one can buy a PCI sound card nowdays new :/ 01:35:40 AumShivaya: get a USB audio interface. better physical interface and, from what i've seen, better support in FreeBSD as well (unless you go with a high end RME card) 01:36:05 *sigh* all these dongles 01:36:09 and cards 01:36:15 * AumShivaya wonders about the PeeC world 01:36:26 what is an RME? 01:36:42 thanks for the advice 01:36:54 RME is a manufacturer of (among other things) PCIe audio I/O cards designed for professional musicians / producers 01:36:56 but who makes the most compatable usb sound cards for F'BSD? 01:37:06 sounds expensive 01:38:43 yes, they are quite expensive: https://www.thomann.de/gb/rme_hdspe_raydat.htm 01:38:45 Title: RME HDSPe RayDAT – Thomann UK 01:38:55 USB interfaces are 98% as good for most purposes and much cheaper 01:40:18 consumer-level PCIe sound cards are basically a dead market since everything has hda on board now, but there's a big market for lower-end USB interfaces for hobbyist musicians, and those tend to work well 01:40:38 and being USB isn't really an issue since USB has more than enough bandwidth for audio 01:40:59 ok 01:41:06 I just find that my onboard sound is terrible 01:41:20 optical doesn't mix audio streams 01:41:32 3.5 mm jack crackles loudly like a few times a day 01:41:37 in general, or on freebsd specifically? i thought modern onboard hda was usually ok 01:41:39 bluetooth is a pita 01:41:55 These issues above exist on BOTH Linux and FreeBSD 01:42:16 I do not know though, if the issue is my onboard sound conclusively, or my Creative Stage soundbar 01:43:20 i've always had back luck with 3.5mm jacks. all my headphones are 6mm, except for the earphones i use with my ipad 01:43:53 unixwitch, got the approval for the first two prs 01:44:04 jbo: i saw! exciting times 01:44:12 jbo: sorry i forgot to add it to subdirs :-( 01:44:35 unixwitch, no problem. it's 100% my fault that I didn't check. but that is what reviews are there for :) 01:45:03 there are git hooks that check for this when you create a new port commit but as I painfully learned those hooks don't get invoked when you import a commit :p 01:45:07 perhaps it is time for a new computer 01:45:08 you'd think make could create a list of subdirs automatically tbh... 01:45:10 but again - 100% not your fault. 01:45:36 jbo: do you happen to have a link to those? i always commit ports to a branch locally so that might be handy when i submit patches 01:46:02 unixwitch, they are in the ports repo - you already have them. 01:46:30 look in the .hooks dir 01:46:33 git config core.hooksPath .hooks or something like that 01:47:14 and you're good to go :) 01:48:48 unixwitch, also, use of DISTVERSION is prefered over PORTVERSION wherever possible. Not sure whether you checked the reivew but I modified that. 01:49:28 ah interesting thanks (re: hooks) 01:49:30 unixwitch, also, much more importantly: did you run your ports through poudriere-testport? it failed here and I added the missing pieces accordingly but generally it's preferred if the submitter makes sure that poudriere-testport actually passes :) 01:49:57 jbo: i may have forgotten that since i didn't know it existed until i submitted then - i just did make stage / make install with DEVELOPER=yes 01:50:10 well 'forgotten' is not the right word there, but you know what i mean 01:50:22 yeah no worries - it's all good :) 01:50:35 I am still learning too - obviously. 01:51:23 the problem with not using poudrier is that you might be missing dependencies etc. for example, I had to add ${PY_SETUPTOOLS} and wheel stuff. your test builds worked because that was already present in the system. poduriere-testport builds in a clean jail so it catches those problems. 01:52:57 does anyone remember when were all complaining about the freebsd survey the other day (meena was that you)? emaste⊙Fo says he wants feedback on it 01:53:05 s/were all/we were all 01:55:34 i really should set up logging in my irc client so i don't forget all this stuff 01:56:07 there are more important things than logging IRC in my opinion :p 01:58:47 autolog_path = "~/.irssi/logs/$tag/${tag}-${0}-%F.log"; 01:59:05 that reminds me that I really want to check out irssi. I am still using horrible hexchat 01:59:10 rtprio: i think you use a different irc client than me 01:59:15 this is irssi 01:59:24 *** Client: ircII EPIC5-2.1.12 (Commit Id: 2078) (Internal Version: 20220615) 01:59:49 oh wow, haha 02:00:52 logs have certainly helped me recall something someone said many months ago 02:03:19 unixwitch, first two ports are commited now. I didn't look at the others yet that depend on those. I'd appreciate it if you could make sure that those ports build cleanly with poudriere-testport first. 02:03:42 jbo: i'll check now 02:04:16 meena: omg who is this igalic person on github nitpicking my commits, what a terrible person 02:09:05 unixwitch: when do you sleep?? 02:09:20 meena: what's that 02:09:55 * meena goes to wake her daughter to ask her about sleep 02:09:55 i usually go to sleep around 4-8AM and wake up around 12-4PM 02:10:00 (currently 2AM here) 02:10:06 unixwitch, +1 02:10:11 hello from the same time zone 02:10:20 3am here :D 02:10:21 i've tried to have a normal sleep schedule but i just can't do it, i always go back to this 02:10:34 yeah fuck sunlight :p 02:10:58 i usually goto bed around 00:00 and fall asleep agility after, but holidays have needed my rhythm up a bit 02:11:33 jbo: fascist island (UK) 02:11:54 lovely 02:12:01 oh, that was a PM, reading is hard 02:12:06 Also, my very good patch got merged, so i updated my ports patches for cloud-init. For FreeBSD & OpenBSD 02:12:21 meena, the python netlink stuff? 02:12:29 you use cloud-init? on freebsd? 02:12:48 unixwitch: i program cloud-init 02:13:10 well, i use it too,m 02:13:32 meena, ah, you work on "upstream cloud-init", not "just" the freebsd stuff? 02:13:50 yes 02:14:09 and no, the netlink stuff is still not merged 02:14:15 meena, that's nice! 02:14:18 meena, that's less nice :( 02:14:47 unixwitch: i live next door, https://glitch.social/@meena/111698011930126007 02:14:48 Title: eena meena me: "my two step plan for improving Ireland" - G L I T C H 02:16:10 * jbo stil hasn't "looked into" mastodon 02:16:53 oh god i have to set up a new poudriere ports tree for testport 02:16:58 so many commands 02:18:53 unixwitch, poudriere ports -c; poudriere jail -c; poudriere testport; :) 02:19:43 it's more all my ports are in different checkouts... i should probably fix that though 02:19:55 i thought that would be a good idea when i started doing this but it turns out it's not 02:20:08 aah 02:20:33 so what I do is usually having a manually managed ports tree (outside of poudriere), then just using branches for new port(s) and adding that ports tree to poudriere 02:21:19 this feels like a silly question but how do i download a patch from bugzilla? https://bugs.freebsd.org/bugzilla/attachment.cgi?id=247266&action=diff 02:21:22 Title: Attachment #247266 for bug #275947 02:21:22 275947 – [NEW PORT] net/py-pychromecast: Python module to talk to Google Chromecast https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275947 02:21:45 oh, 'View'. that was obvious 02:21:54 yep 02:21:56 and then just git-am that 02:22:12 pro tip: that doesn't invoke the pre-commit hooks :p 02:22:16 (for obvious reasons) 02:22:39 okay hang on, now i need to work out how to save a page in qutebrowser 02:24:09 just copy the URL and fetch 02:24:10 :p 02:24:12 okay, this works: ilythia /s/ports-development (main)> fetch -o- 'https://bz-attachments.freebsd.org/attachment.cgi?id=247266' | git am 02:24:14 Title: Invalid Attachment ID 02:24:41 wut? 02:24:58 wut? 02:25:00 ah, the %27 fucked it up for me, sry 02:25:08 irc client parsing crap... 02:25:16 all good - your approach is what I had in mind. 02:25:40 i did try right click > save but apparently Blink saves it in some sort of weird quoted-printable format? no idea what's going on there but i will mess with that later 02:29:34 omg testport is running 02:31:28 oh i see this builds everything the port depends on since it's a different tree 02:36:44 unixwitch, check the poudriere config file. options PACKAGE_FETCH_BRANCH and PACKAGE_FETCH_URL allow it to fetch packages from existing binary repositories if they happen to match what it would be building otherwise. 02:37:09 does that work on -current? i'm not sure how up to date the package builds are here 02:37:12 especially useful for things like rust etc. which might take a long time to build 02:44:55 meena: sounds good (regarding upcoming status report) 02:51:46 regarding sleep cycles, I need to improve my sleep quality but my sleep apnea gets in the way :P 02:52:39 voy4g3r2: https://cgit.freebsd.org/src/commit/?id=6c951b37170f1fb2ae8b4827070743e61b6eaed2 02:52:40 Title: src - FreeBSD source tree 02:54:39 wow that was real quick 02:54:47 awesome sauce 02:57:00 The simplest solutions are often the best ones. 02:58:51 yeah and even my zfs-snapshot periodic issues are resolved :) https://bsd.to/2t5K 02:58:52 Title: dpaste/2t5K (Plain Text) 03:07:36 jbo: py-chromecast (pr#275947) is fine in testport 03:07:50 py-pychromecast i mean (what a silly name) 03:09:16 good ole py 03:15:54 any reason why python ports that already have "py" prefixed to the project name can't be truncated out since we already use "py-" by convention, e.g. "py-chromecast" instead? 03:17:08 kenrap: i wondered about this but it makes more sense with a package name like "py311-pychromecast": this is "pychromecast" for "python 3.11" 03:17:19 if it was py311-chromecast, you might wonder why there's no "chromecast" package on pypi 03:18:00 I see, thanks 03:18:07 yeah, for the ability to install the same package for multiple python distributions 03:18:20 some have it suffixed 03:20:43 well loglevel = default:debug for afp.conf is very noisy 03:24:01 ls 03:24:15 Password: 03:24:43 * kenrap lets out a loud chuckle 03:25:31 apparently audio/sublime-audio depends on gcc12 *and* rust *and* llvm15 03:25:54 this proliferation of compilers is frankly getting ridiculous 03:26:42 [main-development] [2024-01-05_03h11m57s] [parallel_build] Queued: 296 Built: 198 Failed: 0 Skipped: 0 Ignored: 0 Fetched: 0 Tobuild: 98 Time: 00:11:48 03:26:51 296 packages for a fricking music player 03:27:50 I'm seriously considering getting a dedicated build server for my workstation and rpi systems 03:29:03 i tried cross-building rpi packages on amd64 for a bit, but some packages (like rust) are broken, and it wasn't really that much faster 03:29:46 obviously the solution to this is to replace my desktop and my server with arm64 boxes, but they're still so expensive 03:31:46 What kind of arm64 systems are you looking into? 03:33:36 for a desktop, something comparable to my Ryzen 5800X3D would be nice. for a server... i don't need much CPU but i guess 32-64GB RAM 03:34:18 Oh, yeah, that would be hellaciously expensive for arm64 03:34:53 yeah. if you want to spend $10k+ there's loads of options, then on the low end you have a bunch of stuff like rpi or the windows dev kit, but there's really nothing in the middle 03:36:33 i do have a spare M1 Mac Mini (since i gave up on macOS for desktop) which i will turn into a server as soon as freebsd gets the required device drivers :-) 03:37:21 Nice, or to put it in more modern terms: Noice! 03:37:23 unixwitch: is it just the cross compile overhead? since amd64 -> arm64 03:37:42 figure there is added "garbage" having a different cpu being the host verus destination 03:37:47 voy4g3r2: no, poudriere cross-build runs the entire build environment (jail) under user-mode qmenu 03:37:55 so the overhead is huge 03:38:03 s/qmenu/qemu/ 03:38:25 ah hence.. have a seperate box, so it is not "killing" the current box 03:39:36 it's more that even on a relatively fast amd64 cpu, it doesn't end up being much faster than doing a native build on a slow arm64 cpu 03:40:30 and 200+ packages along with 3 compilers does not help 03:40:56 oh, this is just a normal amd64 build 03:41:36 the arm64 comment was in response to kenrap talking about a build server for rpis 03:41:42 ah 03:41:51 i have a love hate relationship with my pis 03:42:02 i am using one for remote backups and zfs stuff 03:43:40 one thing that is very frustrating with the pi and freebsd, the random "freezes" 03:43:52 no matter if i was directly plugged into it or over a network but they are solid toys 03:44:48 it's so I can isolate any build threads/jobs away from my primary system and continue to enjoy my system without interactive lag getting in the way. I thought I would also have it do arm64 builds for my rpis as well. 03:45:30 also considering setting up a bouncer for one of them 03:48:06 I got one of those argon cases where you can use an nvme stick as storage with it 03:48:39 weird and random question when you refer to ELF objects, do you refer to them as elf or ELF? 03:49:05 i ask as i am trying to go through these manual pages.. the manualpage does .Xr ELF 3 but the filename is elf.3.gz 03:49:17 i have it "dinged" as a mismatch do to case sensitivity 03:52:09 voy4g3r2: the Executable and Linking Format is an acronym, so i would say ELF, but i would type "man elf" because i don't expect manpages names to have capital letters 03:52:35 yeah that is where my head is at 03:52:43 so if it is saying ELF object blah blah .. keep as ELF 03:52:53 but if it is .Xr ELF 3 it should be .Xr elf 3 03:53:18 because that is the convetion for everything else.. happens with NUMA NewFs and for all things Sendmail 03:54:00 yes.. that is the way because .Xr elf 5 is right just not the reference to 3 03:54:07 elf(5) has the lowercase version in .Sh NAME so that seems like the appropriate choice for .Xr as well 03:54:40 as does elf(3) 03:55:34 yeah even the filename is lower case 03:55:56 https://bughuntingfreebsd.wordpress.com/progress-report-what-has-been-addressed/ 03:55:58 Title: progress report – what has been addressed – FreeBSD Bug Hunting 03:56:03 it is just crazy how hard this is 03:56:05 i'd be less concerned about the filename and more about what the page actually says 03:56:26 imagine you printed out the manpages and put them in a ring binder, you don't care about the filename, right? because you can't see it 03:56:27 unixwitch: bug 108980 is all about broken links in manual pages 03:56:28 108980 – list of missing man pages https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=108980 03:57:11 so as i am trying to fix that bug.. i am going through and documenting what i am doing 03:57:21 so either some of gets rejected for whatever reason or they accept it all :) 04:09:37 good ole man vacation (had no idea this existed till 30 seconds ago) 04:24:58 jbo: new patch for #275959 (audio/sublime-audio), works in testport now 05:09:39 jbo: and new patch for #275962 (multimedia/mediaelch) which now builds in testport, i think that's everything 05:58:49 god i'm so bored of vnet jails. jails stuck in dying, epair interfaces randomly disappearing... 06:11:59 hm, a bunch of nfs fixed just landed in main, i wonder if this fixed mmap over nfs 07:20:58 Is "gateway_enable=YES" absolutely "net.inet.ip.forwarding=1" and nothing else? 07:28:17 got my reply here; https://freebsd-questions.freebsd.narkive.com/FXkIipAD/packet-forwarding#post3 - thanks anyways. 07:28:18 Title: packet forwarding 09:45:28 11:47:50 hey everyone, so we have moved on to zfs send | zfs recv to move some snapshots and experiencing some behavior i can not explain: I setup 2 users on both machines, called backups, gave them both permission to send/receive datasets through zfs allow and chown the directory on remote side. I have seemed to forgot to do an zfs allow permission which stopped the receiving machine to get the data. I fixed 11:47:56 that by adding 'create' but now when i try to redo the transfer.. the sending machine says the dataset exists on the remote machine. When I do a ls -lsa on the remote machine, the dataset DOES NOT exist.. has anyone seen this and if so, what would be the recommended solution to "fix" the ghost dataset snapshot: https://bsd.to/NYNQ 11:47:57 Title: dpaste/NYNQ (Plain Text) 11:50:38 use zfs to check the existens of the dataset, as it doesn't have to be mounted and then ls will not see it 11:52:56 ahhh 11:54:09 so when i fixed the issue.. i get that must destroy them to overwrite it 11:54:30 and since it is a readonly snapshot, it is like.. that's nice try to destroy and if i did not give that user the destroy ability.. zfs goes no bueno? 12:00:52 well it is letting me send after a zfs destory -f, lets see if works this time, thanks nimaje 12:04:19 i do have to say this is much quicker than rsync magic 13:21:32 hi all 13:58:38 hi adilix 14:11:05 using bhyve under FreeBSD 14, I wonder do we still need the "-w" switch (the 'bhyve_options="-w"' line in vm conf file, to ignore unimplemented MSRs), for let's say OpenBSD guests/VMs? 14:52:05 Is there a way to mitigate Terrapin vulnerability via config options? 14:52:13 Oracle Linux is. . . not exactly being timely with upgrades. 15:00:17 CrtxReavr: try 15:00:19 https://unix.stackexchange.com/questions/765347/how-do-you-mitigate-the-terrapin-ssh-attack 15:00:21 Title: security - How do you mitigate the Terrapin SSH attack? - Unix & Linux Stack Exchange 15:50:34 would spiped ssh mitigate 17:38:52 netatalk service is awfully chatty 18:10:40 tankf33der, I am simply curious... Are you actively noting a Terrapin attack against SSH on your site? Note that the OpenSSH upstream stated the impact of the attack was limited. https://www.openssh.com/txt/release-9.6 18:36:58 Hey everyone. FreeBSD's DTrace does not implement cwd, any idea on how to get the cwd of a process? 18:40:14 procstat -f pid has the cwd in there 18:45:10 isley did it that way, it's so weird what I'm getting here 18:45:24 this program keeps telling me that 18:45:38 [ coolwsd ] ERR #16: Failed to bind to Unix socket at [snap.hell.coolwsd-39xgqStZ] (ENOENT: No such file or directory)| net/Socket.cpp:1095 18:45:59 but I created the socket file manually in it's cwd, and it keeps complaining 18:46:18 maybe it chroots or chdirs, IDK, but what would be visible in procstat, right? 20:40:30 voy4g3r2: Well, it is called netaTALK 20:54:54 vkarlsen: this is true, still can not figure out why the time machine backups jsut stop working.. i figure with all this debug stuff, i would be able to... i think it is on mac side. 21:37:11 well zfs send | zfs recv are operational under a backup user.. now to only get the backups themselves NOT run as root 23:11:07 welp, acpiconf -s 3 just shutdown the PC instead of inducing a sleep state, is that normal? 23:11:47 ah t says so in the handbook nevermind 23:18:55 nmz I've always used the 'zzz' command