On Tue, 20 Jan 2009, Karsten Heymann wrote: > We did that before but ran into problems with file rights (cgi-scripts > running with www-data, developers testing the scripts as themselves) > so we decided to go to use syslog as main logging target.
You can fix the permission problem with the file appender's permission settings, but using a syslog appender is certainly an elegant solution to consolidate all logs on a single host. > This also allows us to use a centralized loghost, which together with > a web syslog front end, should make searching the logs much easier in > the long run. Although this would mean that a separate log file would > be created for *all* scripts called with this setup. Depends on your Log4perl and syslog settings, you can have it either way. You just need to find a way to set 'filename' (or the syslog category) in a way that makes sense for your environment -- you can cluster certain groups of scripts together by classifying them into the same categories and subcategories. -- Mike Mike Schilli m...@perlmeister.com ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ log4perl-devel mailing list log4perl-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/log4perl-devel
