[Box Backup] version 0.06PLUS2

[Ben Summers]

On 25 Jun 2004, at 16:51, J=E9r=F4me Schell wrote:

> Ben Summers a =E9crit :
>>>
>>> Just sent a SIGHUP, no reaction :(
>>>
>>> In fact it seems to react to the signal but only when the sync is=20
>>> over. Just after I sent my last message bbackupd stopped in response=20=

>>> 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,=20=

>> and it worked fine, responding to both SIGHUP and SIGTERM=20
>> immediately.
>> Can you try again for me? Make sure you have logging of local6.info=20=

>> in syslog.conf enabled, and then see if there are any messages like=20=

>> "Exception (7/41) due to signal" in the logs. Check there's only one=20=

>> daemon running too.
>
> Mmmm, just try on two different machines (one Debian Woody and the=20
> other Debian testing) and I always have the same result. In fact the=20=

> daemon responds fine to signals when _no sync_ is in progress. But as=20=

> 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:=20
> /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=20
> 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 :)

I've just had an off list exchange with J=E9r=F4me, and it appears this=20=

problem isn't entirely repeatable.

I would appreciate reports from others, especially if you're running it=20=

on Linux. While it's connected to the server, does sending bbackupd a=20
-HUP signal restart it immediately, and does sending it a normal kill=20
signal stop it immediately?

Thanks,

Ben