For those interested, the fix that perrin refers to above is as follows:

Found this somewhere back when this bug first appeared in mod_perl:

# work-around for mod_perl
my $tie_stdin = tied *STDIN;
untie *STDIN if $tie_stdin;

# insert open2() or open3() statement after the above
[download]

Gerald,

It is a mod_perl bug, but I would consider putting it in the FAQ. Would probably be very helpful to people.

I started work on converting the existing code to use IPC::Run, but hadn't finished by the end of the day today .. so I may put that on hold and try this fix instead.

++beer!

Update: Added clarification in first paragraph as to the source of the fix.

---

---

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.