Syntactic Confectionery Delight | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I usually pay real close attention to logs when i'm writing/debugging something.
My standard way of doing this has become
Occassionally I throw in '>>'.__FILE__.'.'.$$.'.err.log'); or '>>'.__FILE__.'.'.time.'.err.log');, but very very rarely. Lately I tend to add "verbosity" levels to things I write so that in "production" environment, verbosity is off (only if hell breaks loose, does the error log get filled). I rarely "rotate" logs, as i've not written anything that gets massively used. Since my logging needs have been simple, every once in a while I check on me logs and if they're bigger then a 100k, i remove them (after looking closely, and quieting warnings, usually use of unitialized this or that, cause not all perl's have the "warnings" pragma)
____________________________________________________ In reply to Re: naming conventions for logs
by PodMaster
|
|