Thanks for both suggestions.

I used the "print join" suggestion to see what was going on and used single quotes in the string to prevent GetOptions splitting the log command.

I then saw that the script was tring to open the log file with ">>$log", which of course failed with a pipe for a log file. I removed the ">>" and it now works as desired.

Is there a foolproof way to only add the ">>" if the log file is a file rather than a pipe?

Is it as simple as checking for the pipe character at the start of the string? Something like:

$logfilename = $log;
if (substr($log, 0, 1) ne "|") {
  $logfilename = ">>" . $log;
}
if (!open STDOUT, $logfilename) { die "Can't write to $logfilename: $!
+";}
[download]

Thanks,

R.

---

---

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.