diff options
| author | Eelco Dolstra <eelco.dolstra@logicblox.com> | 2014-07-17 20:59:25 +0200 |
|---|---|---|
| committer | Eelco Dolstra <eelco.dolstra@logicblox.com> | 2014-07-17 21:01:25 +0200 |
| commit | 1a1442db7426262fdc23890c61c0be22cc3e1e51 (patch) | |
| tree | 8631ae740575955233abaeb81ba14d5d3bc409ed /nixos | |
| parent | b4c971b14a7e46a7e96cd42e4fe790b2531a2d65 (diff) | |
| download | nixpkgs-1a1442db7426262fdc23890c61c0be22cc3e1e51.tar nixpkgs-1a1442db7426262fdc23890c61c0be22cc3e1e51.tar.gz nixpkgs-1a1442db7426262fdc23890c61c0be22cc3e1e51.tar.bz2 nixpkgs-1a1442db7426262fdc23890c61c0be22cc3e1e51.tar.lz nixpkgs-1a1442db7426262fdc23890c61c0be22cc3e1e51.tar.xz nixpkgs-1a1442db7426262fdc23890c61c0be22cc3e1e51.tar.zst nixpkgs-1a1442db7426262fdc23890c61c0be22cc3e1e51.zip | |
Don't restart systemd-journal-flush
It only needs to be started during boot. Starting it at other times shouldn't hurt, except that if systemd-journald is restarting at the same time, the latter might not have a SIGUSR1 signal handler installed yet, so it might be killed by systemd-journal-flush. (At least that's my theory about the dead systemd-journald instances in the build farm...)
Diffstat (limited to 'nixos')
| -rw-r--r-- | nixos/modules/system/boot/systemd.nix | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/nixos/modules/system/boot/systemd.nix b/nixos/modules/system/boot/systemd.nix index c6c0021ba6d..14caa5d360d 100644 --- a/nixos/modules/system/boot/systemd.nix +++ b/nixos/modules/system/boot/systemd.nix @@ -825,6 +825,7 @@ in systemd.services."user@".restartIfChanged = false; systemd.services.systemd-remount-fs.restartIfChanged = false; + systemd.services.systemd-journal-flush.restartIfChanged = false; }; } |