ChanServ changed the topic of #nixos-systemd to: NixOS <3 systemd | https://jitsi.nixcon.net/systemd | Next meeting 08.12.2020 14:00 UTC (every two weeks)
elvishjerricco has quit [Ping timeout: 264 seconds]
elvishjerricco has joined #nixos-systemd
<andi->
heads up regarding the seccomp issue from above: our service confinement might not work as it did before the seccomp upgrade. Apparently systemd doesn't properly use the seccomp api anymore. I've just filed an upstream bug to see how they judge the situation https://github.com/systemd/systemd/issues/18089
<{^_^}>
systemd/systemd#18089 (by andir, 3 minutes ago, open): systemd unit isolation different after libseccomp upgrade (2.5.0 -> 2.5.1)
<Mic92>
hexa-: also now the bug is happening again
<Mic92>
Activated service 'org.freedesktop.systemd1' failed: Launch helper exited with unknown return code 1
<Mic92>
this is from dbus daemon
Mic92 has quit [Quit: WeeChat 3.0]
Mic92 has joined #nixos-systemd
<flokli>
Mic92: is this on nixpkgs master?
<Mic92>
flokli: yes, but it was still 247. Now I am on 247.2
<Mic92>
let's see if it comes up again
{^_^} has quit [Remote host closed the connection]
{^_^} has joined #nixos-systemd
<andi->
Ugh, I've a system (on 20.09) where networkd doesn't set the network interface to up on startu... WHY