On 2008-07-16 23:03, David Schultz wrote: > A niftier trick would be to actually denote the shutdown > dependencies between apps. Then SIGTERM (or whatever the > appropriate shutdown operation is) can happen in parallel as much > as possible, without accidentally shutting down a service before > dependent services have had a chance to clean up. There's probably > not as many interesting deps for shutdown as there are for > startup... Possibly just the "reverse" of the startup deps? For example, if baz is dependent on foo and bar, the startup order is: 1. foo & bar (possibly parallel) 2. baz at shutdown, we'd get the reverse: 1. baz 2. foo & bar (possibly parallel) However, this may not be so easy for the total dependency graph of everything under /etc/rc.d (not to forget /usr/local/etc/rc.d). ;)Received on Wed Jul 16 2008 - 20:09:59 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:32 UTC