linuxdad wrote:Certainly, specific Use case below.
Program B, relies on Program A, C and Z to be running before it can operate properly. Disturbing any of these systems requires a complete reset to Program Z, then Program A, Program C and then Program B. This was all accomplished by customized the Startup sequencing (the Start/Stop numbers), as well as the contents of the startup and shutdown scripts.
Yoo probably have to adapt the systemd units and provide the dependency information for your use case. For the ordered restart, not sure if that can be achieved, you may have to google around for that or ask on the systemd mailing lists. There are ways to specify similar stuff, e.g. the Requires, Wants, Before, After, PartOf, OnFailure, PropagatesReloadTo=, ReloadPropagatedFrom= and the verious Condition* stanzas. Cf
- Code: Select all
man systemd.unit
linuxdad wrote:Another Example:
Program Swatch (System Watcher), relies on the Syslogd process to record logfile information in the /var/log/swatch file. If the syslogd is restarted (every Sunday of course), then swatch does not have the correct position in the logfile.
In this case swatch is dependant on syslog, and needs to be restarted every time syslogd is refreshed or recycled.
Do these help?
One alternative could be to switch to native journal-triggerd. This is available in cauldron and can be easily rebuilt for Mageia 3
See also
http://jjacky.com/2013-10-06-run-trigge ... -messages/ Another would be to fiddle with systemd-notify for the rsyslogd service to notify systemd, which then should restart swatch.
But also best ask on systemd mailing list for better alternatives.