Am 13.08.2013 13:36, schrieb Paul J Stevens: > On 08/13/2013 12:51 PM, Reindl Harald wrote: > >>> I think that apart from reopening the logsfiles on SIGHUP, I'll also add >>> resetting the loglevels >> >> is SIGHUP not supposed normally to re-read the complete >> configuration without closing client connections? > > No. Signals are just that, signals. Only SIGKILL implies killing the > program. All other signals are up to the program to deal with.
that's clear, i did not say SIGHUP is supposed to kill processes :-) > SIGHUP was ignored. Now I've modified the code to reopen the logfiles > once as soon as a new connection arrives. In signal handlers you can't > do much else other then setting some global variables, so I'll leave it > to the event handling code to check against those variables. sounds good the question was: in that case can the handlers re-read dbmail.conf and adjust changed timeout-params at least for new connections > Some things are easier than others to change while a process is running. > Adding code to update the log-levels is trivial. But for example, > changing the IP addresses dbmail listens on, is not! that's clear > In the past (dbmail-2) on a sighup, all child-processes were terminated, > the configuration re-read, and everything restarted. But for dbmail-3 > that doesn't make sense. If we have to shut down everything, we might as > well do a complete restart. Keeps things much simpler terminate is a no-go, that's clear the idea behind a SIGHUP is *not* to terminate connections :-)
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
