[Box Backup-dev] Re: [Box Backup-commit] #20: bbackupctl reload reports prior settings, 0.10 Win vchris_general_1280

Chris Wilson boxbackup-dev@fluffy.co.uk
Thu, 12 Apr 2007 23:56:55 +0100 (BST)


Hi all,

On Thu, 12 Apr 2007, trac@fluffy.co.uk wrote:

> Change bbackupd.conf timing settings.
> Run bbackupctl reload.
> The "Daemon configuration summary" incorrectly reports the settings from
> before the changes.  Running it again reports the correct settings.
>
> Used notepad to make changes to bbackupd.conf to return timers from short
> test settings to longer default settings.  Then ran bbackupctl reload to
> set them:
>
> C:\Program Files\Box Backup>bbackupctl.exe reload
>
> Using configuration file C:\Program Files\Box Backup\bbackupd.conf
> Daemon configuration summary:
>   AutomaticBackup = true
>   UpdateStoreInterval = 3 seconds
>   MinimumFileAge = 4 seconds
>   MaxUploadWait = 24 seconds
> Succeeded.
>
> C:\Program Files\Box Backup>bbackupctl.exe reload
>
> Using configuration file C:\Program Files\Box Backup\bbackupd.conf
> Daemon configuration summary:
>   AutomaticBackup = true
>   UpdateStoreInterval = 3600 seconds
>   MinimumFileAge = 21600 seconds
>   MaxUploadWait = 86400 seconds
> Succeeded.

This is an interesting one. The daemon's settings are sent in the summary 
line, which is sent before the reload takes effect.

Why are the settings sent on each command? Couldn't we have an "info" 
command which returns them, which is sent by "bbackupctl reload" after the 
reload command?

Cheers, Chris.
-- 
_____ __     _
\  __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |