[Box Backup] Configurable syslog facility

[Chris Wilson]

On Tue, 24 Mar 2009, Kenny Millington wrote:

>> I do wish maintainers would try to push stuff upstream instead of just 
>> distributing their code with a random local patches and then forgetting 
>> about them.
>
> Sorry, the way I originally phrased that might have been a tad unfair. 
> As a first port of call I e-mailed the maintainer to suggest a use case 
> for local6. His reply was to contact the box dev list to suggest it be 
> user-configurable. (I was going to anyway, but thought I'd do things in 
> the maintainer --> upstream order.)

Well, I accept the need for the option, but as I had no idea that 
maintainers were distributing Box Backup with such a patch, it could have 
caused considerable confusion while trying to help users to configure 
syslog for logging, and also I had no idea that the configuration option 
was needed until now.

> As far as Debian/Ubuntu goes LOG_DAEMON is "right" in the majority of 
> cases, just not when using LogAllFileAccess to report on since it 
> clutters the logs somewhat.

I'm not sure that I approve of the use of syslogs as an intermediate 
storage for this kind of logging. It's already possible to log to a file 
and specify a different verbosity level when doing so, so that debug level 
logging doesn't end up in syslog, only in that file. I would have thought 
that handling a backup-finish event, parsing and then deleting that file 
would be more reliable.

> I take it this means it'll hit 0.12 - whenever that is? ;)

actually 0.11, whenever that is :)

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 |