Bacula-users

Re: [Bacula-users] Big log....

2010-04-01 10:56:18
Subject: Re: [Bacula-users] Big log....
From: Matija Nalis <mnalis+bacula AT CARNet DOT hr>
To: Gilberto Nunes <gilberto.nunes AT selbetti.com DOT br>
Date: Thu, 1 Apr 2010 16:53:57 +0200
On Thu, Apr 01, 2010 at 10:56:03AM -0300, Gilberto Nunes wrote:
> But now that I see... the Log.MYD is in bacula directory locate on 
> /var/lib/mysql...
> Then, i thing that this Log.MYD is onwer but bacula or not???

Yeah, I think Phil is wrong, you're not talking about same thing.

/var/lib/mysql/bacula/Log.MYD / MYI is bacula table, which contains
logged output for jobs (any errors etc., the stuff you get with 
"list joblog" bacula command), and not the MySQL SQL log.

See it's contents for yourself with something like:
mysql bacula -e 'select * from Log limit 30'

It should be purged automatically when the jobs themselves are
purged. I do not know what would happen if you decided to purge it
manually from SQL (maybe nothing, but...). 

So if should probably shrink by itself after some time if you reduce
your "Job Retention". Or maybe it is so big because some of your jobs
had a ton of messages - that should also expire by itself with such
jobs.

Alternatively, I think you could modify your "catalog" line in
"Messages" resources in config files, in order to log less (or
even nothing).


------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>