pyrox.dev / nixpkgs
lol
fork atom

nixos/alloy: set After=network.target

This prevents the network from being torn down before alloy itself it
stopped.

Alloy tries to flush its WAL on SIGTERM, and if the network stack is
already down, it tries to flush logs up to 90s during shutdown/reboot.

From https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/:

> network.target has very little meaning during start-up. It only
> indicates that the network management stack is up after it has been
> reached. Whether any network interfaces are already configured when
> it is reached is undefined. Its primary purpose is for ordering
> things properly at shutdown: since the shutdown ordering of units in
> systemd is the reverse of the startup ordering, any unit that is order
> After=network.target can be sure that it is stopped before the network
> is shut down if the system is powered off. This allows services to
> cleanly terminate connections before going down, instead of abruptly
> losing connectivity for ongoing connections, leaving them in an
> undefined state. […]

Florian Klink 5d094c23 f2b33de3

options
unified split
Changed files
+1
nixos
modules
services
monitoring
alloy.nix
+1
nixos/modules/services/monitoring/alloy.nix 
···

       
65

       
65

       
 

       



     

       
66

       
66

       
 

       
  config = lib.mkIf cfg.enable {


     

       
67

       
67

       
 

       
    systemd.services.alloy = {


     

       

       
68

       
+

       
      after = [ "network.target" ];


     

       
68

       
69

       
 

       
      wantedBy = [ "multi-user.target" ];


     

       
69

       
70

       
 

       
      reloadTriggers = lib.mapAttrsToList (_: v: v.source or null) (


     

       
70

       
71

       
 

       
        lib.filterAttrs (n: _: lib.hasPrefix "alloy/" n && lib.hasSuffix ".alloy" n) config.environment.etc