When the reboot program runs, it sends SIGHUP right after SIGTERM, so we
need to handle it as well.
Also fix a few spelling errors.
Signed-off-by: Mike Frysinger <[EMAIL PROTECTED]>
---
user/watchdogd/watchdogd.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/user/w
Mike Frysinger ha scritto:
When the reboot program runs, it sends SIGHUP right after SIGTERM, so we
need to handle it as well.
Hi Mike,
I'm not sure that SIGHUP signal should be handled while rebooting system.
IMHO: sending SIGHUP signal while reboot system is not correct. Maybe,
only rebo
On Mon, Sep 29, 2008 at 08:59, damico wrote:
> Mike Frysinger ha scritto:
>> When the reboot program runs, it sends SIGHUP right after SIGTERM, so we
>> need to handle it as well.
>
> I'm not sure that SIGHUP signal should be handled while rebooting system.
> IMHO: sending SIGHUP signal while reboo
Mike Frysinger ha scritto:
On Mon, Sep 29, 2008 at 08:59, damico wrote:
Mike Frysinger ha scritto:
When the reboot program runs, it sends SIGHUP right after SIGTERM, so we
need to handle it as well.
I'm not sure that SIGHUP signal should be handled while rebooting system.
IMHO:
Hi Mike,
Mike Frysinger wrote:
When the reboot program runs, it sends SIGHUP right after SIGTERM, so we
need to handle it as well.
Also fix a few spelling errors.
Signed-off-by: Mike Frysinger <[EMAIL PROTECTED]>
Looks good, applied.
Thanks
Greg
user/watchdogd/watchdogd.c |5 +++--
On Tue, Sep 30, 2008 at 05:30, damico wrote:
> Mike Frysinger ha scritto:
>> On Mon, Sep 29, 2008 at 08:59, damico wrote:
>>> I was looking for some specification on shutdown and signals in the net
>>> but I haven't found any reliable note on that topic.
>>
>> there is no such spec
>>
>>>
>>> Just
