On 07/13/2011 10:28 PM, Soren Hansen wrote:
> 2011/7/13 gholt <email address hidden>:
>> As far as 'shutdown' I meant that the command keyword should be added to
>> the list, not replacing 'stop' with it. Both commands exist.
>
> I understand.
>
> "stop" is mandatory, so it's what people default to calling when they
> want to shut something down.
Well, more when you go on the shutdown runlevel, and the system is
calling each init.d scripts! People can adapt to different kind of
commands, but insserv can't.
> Don't you think letting existing
> connections finish is the better default action?
Unfortunately, I don't. If you have a remote connection that is taking a
lot of time until done, you really don't want it to prevent your server
from rebooting (said otherwise: you don't want to wait forever).
On 07/13/2011 10:28 PM, Soren Hansen wrote:
> 2011/7/13 gholt <email address hidden>:
>> As far as 'shutdown' I meant that the command keyword should be added to
>> the list, not replacing 'stop' with it. Both commands exist.
>
> I understand.
>
> "stop" is mandatory, so it's what people default to calling when they
> want to shut something down.
Well, more when you go on the shutdown runlevel, and the system is
calling each init.d scripts! People can adapt to different kind of
commands, but insserv can't.
> Don't you think letting existing
> connections finish is the better default action?
Unfortunately, I don't. If you have a remote connection that is taking a
lot of time until done, you really don't want it to prevent your server
from rebooting (said otherwise: you don't want to wait forever).
Thomas