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)
andi- has quit [Ping timeout: 248 seconds]
andi- has joined #nixos-systemd
<lukegb> Yeah, NixOS migrating to system extension images when
<lukegb> Units acquired a new property "Markers" that takes a list of zero,
<lukegb> one or two of the following strings: "needs-reload" and
<lukegb> "needs-restart". These markers may be set via "systemctl
<lukegb> set-property". Once a marker is set, "systemctl reload-or-restart
<lukegb> --marked" may be invoked to execute the operation the units are
<lukegb> marked for. This is useful for package managers that want to mark
<lukegb> units for restart/reload while updating, but effect the actual
<lukegb> operations at a later step at once.
<lukegb> ....thanks, irccloud, I was expecting you to pastebin that
<makefu> lookin good , no problem :)
<lukegb> Anyway, do we know if using unit markers resolves any of the problems with unit reload/restart at activation time?
<lukegb> I'm assuming it doesn't because systemd still doesn't want to do the graph stuff we want :P
<Mic92> This markers stuff sounds interesting for our activation script
<Mic92> Hopefully systemd is smart enough to respect ordering
<andi-> Worth testing *after* we migrated to the new version
<andi-> I wouldn't make that part of the initial upgrade process.
<lukegb> Oh yeah, definitely don't combine the two
<flokli> I also think we can't do the bump until we branched off
<flokli> there was an RFC/issue/comment from some of the release managers about this
<flokli> and I'm not too eager to push too much for it