hey monks--

I'm working on the same database issue, and as I was looking through the logs that my script outputs, I realized I could probably be providing more useful information, especially in the names of the logs. right now I just do something like open CHANGE_LOG, "> ${table_name}-changes.log", and, if the log is one I want to hold on to, I usually end up renaming it so that it won't get overwritten. Appending might be nice, but the logs would get too big.

what conventions have you developed in naming your logs that give an easily readable but informative title to each separate file? code examples of open statements (i.e. open FOO_LOG, "> foo.log") would be appreciated.

thanks in advance,
--au