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)
ajs124 has quit [Quit: Bridge terminating on SIGTERM]
ajs124 has joined #nixos-systemd
Ox4A6F has quit [Quit: authenticating]
Ox4A6F1 has joined #nixos-systemd
ajs124 has quit [*.net *.split]
julm has quit [*.net *.split]
ajs124 has joined #nixos-systemd
julm has joined #nixos-systemd
qyliss has quit [Quit: bye]
qyliss has joined #nixos-systemd
<pie_> ok there needs to be a script that attempts to replicate a systemd unit's environment to help with debugging interactively
<pie_> or am i just thinking about this wrong
<pie_> because this is getting annoying x)
<pie_> do i need to do anything other than run the exec lines in order and purify/copy the environment?
<ajs124> pie_: there's systemd-run
<pie_> *hm
<pie_> oh mh
<pie_> ajs124: how can that help?
<pie_> ajs124: yeah no, i dont see if that helps with running existing services?
qyliss has quit [Quit: bye]
qyliss has joined #nixos-systemd
qyliss has quit [Quit: bye]
qyliss has joined #nixos-systemd
qyliss has quit [Quit: bye]
qyliss has joined #nixos-systemd