[Box Backup] version 0.06PLUS2
Jérôme Schell
boxbackup@fluffy.co.uk
Fri, 25 Jun 2004 17:51:16 +0200
Ben Summers a écrit :
>>
>> Just sent a SIGHUP, no reaction :(
>>
>> In fact it seems to react to the signal but only when the sync is
>> over. Just after I sent my last message bbackupd stopped in response
>> to the SIGTERM I sent long time before :)
>
>
> Are you sure?
>
> I've just compiled the latest version on my Linux Debian 3.0 install,
> and it worked fine, responding to both SIGHUP and SIGTERM immediately.
>
> Can you try again for me? Make sure you have logging of local6.info in
> syslog.conf enabled, and then see if there are any messages like
> "Exception (7/41) due to signal" in the logs. Check there's only one
> daemon running too.
>
Mmmm, just try on two different machines (one Debian Woody and the other
Debian testing) and I always have the same result. In fact the daemon
responds fine to signals when _no sync_ is in progress. But as soon as
some transfert occurs, the response is delayed.
The logs i've got:
Jun 25 17:37:10 deus bbackupd[16968]: Starting daemon (config:
/etc/boxbackup/bbackupd.conf) (version 0.06PLUS2)
Jun 25 17:37:10 deus bbackupd[16968]: Beginning scan of local files
Jun 25 17:37:10 deus bbackupd[16968]: Opening connection to server
myserver.mydomain.com...
Jun 25 17:37:11 deus bbackupd[16968]: Connection made, login successful
An now I'm waiting for it to react to the signals I've sent :)
Thanks anyway for your test,
--
Jérôme