>Thanks!  I didn't see that, although I thought that I had read all
>of the configure options...

That must have taken you hours!!!  :-).

Prior to 2.4.2p2, the debug files took one of two forms.  They either
had a fixed name (e.g. amandad.debug) that was overwritten every time
the program was run, or they included a PID (amandad.$$.debug).  In the
latter case, you needed another periodic process to clean out the files.

I got tired of people not having the right debug file still around to
help them with problems :-), so at 2.4.2p2 the names changed to always
be unique and datestamped (amandad.YYYYMMDDHHMMSS.debug, optionally
with a three digit sequence number as well, just in case).  At the same
time, --with-debug-days was added to let Amanda do its own cleanup.
The default value is four days to cover a long weekend.  I set mine to
10 days (the files are small and cheap, but not having them when you
need to figure something out is a real pain).

>Ricky

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Reply via email to