From 76055df52de56f92aad34c774e24d606722252fb Mon Sep 17 00:00:00 2001 From: Eelco Dolstra Date: Mon, 11 May 2015 17:25:51 +0200 Subject: [PATCH] Allow systemd-journald to be restarted With systemd 219, this is fine because systemd will cause the new journald to re-use the file descriptors of the old one. So existing connections to the journal are unaffected. --- nixos/modules/system/boot/systemd.nix | 1 - 1 file changed, 1 deletion(-) diff --git a/nixos/modules/system/boot/systemd.nix b/nixos/modules/system/boot/systemd.nix index 2a32c963e970..27ad1bdec329 100644 --- a/nixos/modules/system/boot/systemd.nix +++ b/nixos/modules/system/boot/systemd.nix @@ -747,7 +747,6 @@ in systemd.services."systemd-rfkill@".restartIfChanged = false; systemd.services."user@".restartIfChanged = false; systemd.services.systemd-journal-flush.restartIfChanged = false; - systemd.services.systemd-journald.restartIfChanged = false; # FIXME: shouldn't be necessary with systemd 219 systemd.services.systemd-random-seed.restartIfChanged = false; systemd.services.systemd-remount-fs.restartIfChanged = false; systemd.services.systemd-update-utmp.restartIfChanged = false;