Re: Giant logfile again

The remaining lines are only messages like shown in the last line: Skipping over finished thread 1 of 1: EHT 05944 ... rocketed the log file size up to 20GByte in less than 2 hours. Its an extremely rare case which I noticed about a month ago. I checked in a preventive measure (I dont

Re: Giant logfile

Debajyoti Bera wrote: BTW, this problem was fixed in the next bugfix release, 0.2.18. I've upgraded yesterday to 0.2.18 and will keep an eye on it. And you should up the max_watches limit; the value in /proc/sys/fs/inotify/max_user_watches should be significantly larger that the number of

Re: Giant logfile

Hi, On 10/13/07, Debajyoti Bera [EMAIL PROTECTED] wrote: I was referring to this part: // FIXME: We always turn on full debugging output! We are //still debugging this code, after all... //arg_debug ? LogLevel.Debug : LogLevel.Warn, LogLevel.Debug, ... which basically ignores the

Re: Giant logfile

Hi, On 10/14/07, Debajyoti Bera [EMAIL PROTECTED] wrote: Ya. Its possibly because of a lower inotify max_watches limit. It used to print too many warning messages in the past, even without --debug (besides causing other problems). BTW, this problem was fixed in the next bugfix release,

Re: Giant logfile

Hi Debajyoti, Debajyoti Bera wrote: The reason of the large log file is probably a known issue (and already fixed). But now this makes me thinking ... how to cap the log file size ?! - dBera IMO, there are two points to consider: First, there are always old log files floating around in

Re: Giant logfile

Hi, First, there are always old log files floating around in the Log directory. Do we really need them ? This is a good question. I am in favour of turning off the debug flag in the release build (i.e. the installed one). Instead debugging can be turned on when running uninstalled or by using

Re: Giant logfile

Hi, On 10/13/07, D Bera [EMAIL PROTECTED] wrote: First, there are always old log files floating around in the Log directory. Do we really need them ? Log files older than 14 days are removed automatically by Beagle, IIRC. This is a good question. I am in favour of turning off the debug

Re: Giant logfile

This is a good question. I am in favour of turning off the debug flag in the release build (i.e. the installed one). Instead debugging can be turned on when running uninstalled or by using some environment variable. Though debugging helps and some hard to find bugs were found because

Re: Giant logfile

Hi Debajyoti, Debajyoti Bera wrote: Did you mean all distributions (I know about OpenSUSE and Fedora, maybe Ubuntu also does) know about this and patch the code with a higher loglevel ? I don't think all distributions know about this; even if they do, what purpose does it serve us. Only

Re: Giant logfile

Did you mean all distributions (I know about OpenSUSE and Fedora, maybe Ubuntu also does) know about this and patch the code with a higher loglevel ? I don't think all distributions know about this; even if they do, what purpose does it serve us. Only users who install from source will

Giant logfile

Hi all, I've just noticed that I've run out of HD space. Looking around I've found in my $HOME/.beagle/Log: ... -rw-r- 1 steve users 146672805359 2007-10-10 04:41 2007-10-09-15-38-19-IndexHelper ... Wow, 140+ GByte. Can the size of those log files limited without putting them into an extra

Re: Giant logfile

Wow, 140+ GByte. Oops!!! Can the size of those log files limited without putting them into an extra partition ? Might be this a known issue. My beagle is a bit older, still version 0.2.17. The reason of the large log file is probably a known issue (and already fixed). But now this makes