comment on

Dear Monks,

I'm working on an application that creates many (e.g. 100) forks to do some OS related work (e.g. make some kind of backups).

I'd like to provide a verbose debug log. Each of my forks' output should end up in one logfile after my script has finished.

How should I implement this?

If I just fork w/ the open filehandle I'll end up having garbage and/or duplicate lines in my logfile.

I could close the logfile after each write and use Flock.

Or I could create a dedicated logging child that communicates with the other by the means of a pipe().

Anything else?

And if the solution would integrated nicely with Log::Dispatch I'd be super happy.

Please note that using the syslog is not an option here. I alreay have syslog logging in place for the more severe issues, but I don't want to put the debugging information into the syslog.

Thanks, tex

In reply to Logging in a multi-process environment by tex

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks