NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
I pour myself a cup of strong coffee. :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Logging (Score:1)
Just because you are on Windows does not mean you need to use the event log. I personally don't like it and just use Log4perl.
Re:Logging (Score:1)
my two worries on that idea is;
firstly a native windows person (the customer installing the application) may get confused about why this application logs differently than the normal windows apps
secondly, you then need to choose/install/maintain your own logrotate stuff, if you wish to stop logs growing forever. the event logger, as you would expect for a native operating system function, does it's own housekeeping by default.
Reply to This
Parent
Re: (Score:1)
What, does anyone actually use and/or like the Windows event log?
Re: (Score:1)
Normally, I hate it for logging. But things have changed in Vista/Server 2008.
Microsoft has tried to turn the Event log into a syslogd like system. You can have a central server receive and/or monitor all of the other servers events logs, and write monitoring rules (if you see x of y ad level z, email/netsend/script user $)
Now that it's easier to have a server to monitor logs (like in an ops or helpdesk area), I'm more inclined to use them, at least for Errors/Fatal level events.
Of course, if you're using s