Hi! Alexey Abramov <leven...@mmer.org> skribis:
[...] >> I’m not sure. IIUC, a “networking target” here could translate to a >> Shepherd service that depends on all the relevant DHCP and static >> networking services. The question the becomes how to express that >> grouping conveniently. > > Yes, I also would like to point out that their must be a way to > establish a firewall, for example, *before* any network interface is up > (After=network-pre.target in systemd [1]). And the same thing during the > shutdown procedure (Before=network-pre.target in systemd). I would do that by having ‘networking’ depend on ‘firewall’ (say). Does that make sense? It’d be interesting to see whether we need something beyond this. > Applications have to be able to gracefully shutdown their network > connections. Is it the case right now, I don't know? What do you mean? > I am checking (shepherd services) where `shutdown-services' defined, and > seems like it just walks across %services hash table. Am I missing > something? Correct, there’s nothing fancy going on there. Thanks, Ludo’.
