http://www.perlmonks.org?node_id=1141061


in reply to Re^3: combine logentries with Log::log4perl
in thread combine logentries with Log::log4perl

Windows has a central repository where all kinds of system messages, erors, warnings, ... are kept, not only OS messages, but apps can write to that repository too

Like syslogd ?

  • Comment on Re^4: combine logentries with Log::log4perl

Replies are listed 'Best First'.
Re^5: combine logentries with Log::log4perl
by CountZero (Bishop) on Sep 05, 2015 at 08:05 UTC
    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
[reply]

      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]
        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]

In Section Seekers of Perl Wisdom