summary refs log tree commit diff
path: root/nixos/modules/services/blockchain
diff options
context:
space:
mode:
authorDavid Anderson <dave@natulte.net>2022-04-24 23:31:35 -0700
committerDavid Anderson <dave@natulte.net>2022-04-24 23:31:35 -0700
commitc9a1647adeef403328f7b222666648bf8bfa0320 (patch)
treed64d7856822e558c485a99fb6b7a0b34386aa6e6 /nixos/modules/services/blockchain
parenta5774e76bb8c3145eac524be62375c937143b80c (diff)
downloadnixpkgs-c9a1647adeef403328f7b222666648bf8bfa0320.tar
nixpkgs-c9a1647adeef403328f7b222666648bf8bfa0320.tar.gz
nixpkgs-c9a1647adeef403328f7b222666648bf8bfa0320.tar.bz2
nixpkgs-c9a1647adeef403328f7b222666648bf8bfa0320.tar.lz
nixpkgs-c9a1647adeef403328f7b222666648bf8bfa0320.tar.xz
nixpkgs-c9a1647adeef403328f7b222666648bf8bfa0320.tar.zst
nixpkgs-c9a1647adeef403328f7b222666648bf8bfa0320.zip
nixos/tailscale: use systemctl restart during activation.
This avoids the scenario where you activate a new config over Tailscale,
and a long delay between the "stop services" and "start services" phases
of the activation script lead to your terminal freezing for tens of
seconds, until tailscaled finally gets started again and the session
recovers.

Per the documentation of stopIfChanged, this is only safe to do if the
service definition is robust to stopping the old process using the new
service definition. As the maintainer of the upstream systemd unit, I
can confirm that Tailscale is robust to this scenario: it has to be
in order to work right on several other distros that just do
unpack-then-restart, rather than the more complex stop-unpack-start
dance.

Signed-off-by: David Anderson <dave@natulte.net>
Diffstat (limited to 'nixos/modules/services/blockchain')
0 files changed, 0 insertions, 0 deletions