Thanks for catching the cut-n-paste typos. Yes, I see the last root logger setup prevails. However, I still don't see from reading the docs how to have a suite of programs sharing a common debug log, having their own info log, and sharing a common error log. And sure, logs can and should grab messages from higher levels -- eg debug log can and should log infos, warns, errors, fatals, etc.

Why are we trying to do this? When debugging, we set  $logger->level($DEBUG); in a script, or in a module, or both, as needed. This produces lots of output. Once things are working, we raise the level to $INFO. We log major program events at the info level ("Now initializing...", "Now working...", "Now complete."). We log fatal errors, and program startups, in the error log. (Think the apache log, which captures major events like errors and restarts). To see if all is well, scan the error log. To get details on a script, scan the script-specific info log. To debug, turn on the debugging level and stare and the debug log. (The debug log is common because the bug tracking might cross several modules.)

So, trying to do this and not understanding the docs:

how may a suite of programs and mods share a common debug log, each program have their own info log, and all share a common error log?

Thanks