On Mon, Oct 6, 2008 at 08:49, (private) HKS <[EMAIL PROTECTED]> wrote: > In general, I understand HUP to be exactly what you're talking - a > reload rather than a restart. I see little to lose by enforcing that > in rsyslogd.
Ditto - IMHO SIGHUP has come to signify 'change what you can without restarting' or a "hot restart". Some daemons are capable of fully re-configuring on the fly, i.e. "warm restart". It would be rather complex but one could mark particular configuration pragmas as requiring a full tear-down and issue a warning if a warm restart was issued and those had changed. The third option (which many poorly-written init scripts do anyway) is a "cold restart", where the process is killed off and manually re-started, allowing full-blown reconfiguration. I don't care what signals are used for what, beyond the [de facto?] standard of 'skip a beat' when given SIGHUP. Beyond the scope of this discussion, I've not looked at your configuration parsing but wonder if you're not parsing it into an internal, static structure and handling bits from there. If you were, it would be trivial to parse your new configuration, see how/whether it differs from the running one, and shift over if able - like failsafe firmware in embedded systems. That would also offer interesting implications for alternative configuration syntaxes. RB _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
