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

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.