[rrd-developers] rrdcached shutdown

Tobias Oetiker tobi at oetiker.ch
Thu Sep 25 23:43:48 CEST 2008


Today Florian Forster wrote:

> Hi Kevin,
> On Thu, Sep 25, 2008 at 12:11:41PM -0500, kevin brintnall wrote:
> > We could catch SIGTERM for expedited shutdown and SIGINT for full-flush
> > shutdown?  Then, each operator can decide which makes the most sense.
> I see your point, I'm in the same situation myself. However, I feel
> somehow uncomfortable about making this ``fast exit'' feature the
> default behavior. Can't tell you precisely why, it just doesn't feel
> ``right'' ;)
> In any case, the user should have a choice. Using a different signal for
> this is a good idea, though I'd use SIGUSR1 or SIGUSR2 for this. SIGTERM
> and SIGINT aren't really different enough for this to make much sense
> (imho).
> Another, possibly additional, idea would be to add `SHUTDOWN' and
> `BUGGEROFF'[*] commands.

the point of using TERM is that as a system goes down, normally
processes that are still hanging around are sent TERM and shortly
after KILL, so it is a good thing for a process to quickly get
ready to die when he gets TERM.

also when a user does kill PID the process should die and not
suddenly start using the disk like mad for 20 minutes ... if it
does that the user will send it a kill -KILL and this may not be
what we want at all ...


Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900

More information about the rrd-developers mailing list