ChanServ changed the topic of #nixos-systemd to: NixOS <3 systemd | | Next meeting 08.12.2020 14:00 UTC (every two weeks)
<flokli> hexa-: no, it's a bit of a mess
<flokli> Upstream moved to dlopen()ing more stuff, and we have no easy way to figure out in which compilation unit that call ends up in
<flokli> There might appear a semi-standard to figure these out automatically:
<{^_^}> systemd/systemd#17453 (by keszybz, 8 weeks ago, open): Insert custom .so file as "dlopen plugin" for libraries we want to load dynamically
<{^_^}> systemd/systemd#17416 (by poettering, 9 weeks ago, open): dlopen: add some ELF section magic for declaring dlopen() deps
<andi-> How about (for now) we just replace all the .so(\.\d)* occurrences with the absolute path? I believe the code would be similar to how we currently implement patchShebangs and dlopen just does the right thing if we pass absolute paths.
<andi-> Nix will also carry the right references as long as that path is in the binary..
Mic92 has quit [Quit: WeeChat 3.0]
Mic92 has joined #nixos-systemd
<hexa-> so, I have this system where `systemctl status` results in "Failed to read server status: Connection timed out"
<hexa-> anything I should check before rebooting?
<hexa-> it gets into this state every few days
<hexa-> this is on 21.03pre259253.9232d4168e2 with systemd 247.
<hexa-> also this > Failed to read server status: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
<hexa-> dbus is still running and I'm forcing a reboot now. Good things like these will return