Daniel, the SIGUSR2 trick is very nice, but as comment #6 point out,
it is *very* verbose (can fill 100MB in minutes), so it will exhaust
any reasonable partition pretty quickly, and the fact that it writes
in /tmp means bad consequences for the system when this fills up.
So it is not currently usable as a way to track gamin permanently. I
have to turn it on only for short periods of time, and sure enough,
these are not the times when things go bad.
I suggest two improvements:
1- Have the log directory configurable (defaults to /tmp)
2- Configure a MAX_SIZE for a log file, after which logs are
rotated, possibly with compressing old ones automatically.
Daniel, the SIGUSR2 trick is very nice, but as comment #6 point out,
it is *very* verbose (can fill 100MB in minutes), so it will exhaust
any reasonable partition pretty quickly, and the fact that it writes
in /tmp means bad consequences for the system when this fills up.
So it is not currently usable as a way to track gamin permanently. I
have to turn it on only for short periods of time, and sure enough,
these are not the times when things go bad.
I suggest two improvements:
1- Have the log directory configurable (defaults to /tmp)
2- Configure a MAX_SIZE for a log file, after which logs are
rotated, possibly with compressing old ones automatically.
Thanks,
Philippe