upstart proposal on "kill signal/timeout" stanzas

[Thomas Perschak]

I am complaining about the confusing terminology.
"kill signal" specifies the signal send for termination while "kill timeout" 
has nothing to do with termination - it is about killing.

Example:
kill signal SIGxxx
kill timeout 120

Looking at the example one thinks that SIGxxx is send after 120 seconds - 
which is wrong - it is send automatically after 5 seconds.

So I thought it more logic if "kill signal" was renamed to "term signal", in 
addition there should be a "term timeout".
The "kill timeout" should stay as it is.

Example:
term signal SIGxxx
term timeout 30
kill timeout 120


thx

-----Original Message----- 
From: Clint Byrum
Sent: Tuesday, May 14, 2013 5:02 PM
To: upstart-devel at lists.ubuntu.com
Subject: Re: upstart proposal on "kill signal/timeout" stanzas

On 2013-05-14 07:49, Thomas Perschak wrote:
> I would like to propose two new stanzas:
> term signal
> term timeout
>
> Currently, in upstart 1.5, the SIGTERM is send after 5 seconds and
> the SIGKILL is send after the timeout specified with "kill timeout".
> That is very confusing.
>
> If one wants to avoid beeing terminated one has to use "kill signal
> SIGCONT" - but SIGKILL cannot be worked around.
>

The SIGKILL is absolutely necessary for system shut down. If your
program must never be killed with SIGKILL, then you probably don't want
a 'stop on' and need to have constructed your program in a way where it
will not prevent the system from shutting down cleanly.

However, perhaps you can provide a concrete example of a program which
should be given special privileges to delay a system shutdown
indefinitely?

-- 
upstart-devel mailing list
upstart-devel at lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/upstart-devel