The only problem is to use a logging framework that is advanced enough to make it easy for admins when deciding what goes into the file and how size is managed. Look at log4j as a model. I see there's a version for Perl also ( http://mschilli.github.com/log4perl/ ). If it's good enough and it has followed the log4j mantra (as expected from any log4* project) then it is the perfect tool for the job.
That would be a good compromise solution. It disconnects the application log API from the sinks used to receive it, so we could make the choice w/o the app having to know or care.
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
