Re^5: combine logentries with Log::log4perl

Yes, indeed. I stand corrected. Somehow I always thought the syslog only had OS or kernel messages.

Of course, that begs the question, why do most programs still use their own logging system?

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

My blog: Imperial Deltronics

Comment on Re^5: combine logentries with Log::log4perl

Replies are listed 'Best First'.
Re^6: combine logentries with Log::log4perl by SimonPratt (Friar) on Sep 07, 2015 at 11:58 UTC
If you're writing a multi-platform program, do you invest in learning about and using all of the various logging systems for each environment, or do you log with a single format into a single location?	[reply]
Re^7: combine logentries with Log::log4perl by CountZero (Bishop) on Sep 07, 2015 at 14:17 UTC
I'd write a logging module that sends things to syslog, event-log or a old-fashioned text-log file depending on the OS. Think of DBI-for-logging, with DBD-like modules for each OS. CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James My blog: Imperial Deltronics	[reply]


Just another Perl shrine
	PerlMonks