I haven't tested this, but this is how I would write it based on what you have provided.

#!/usr/bin/perl
use strict;

# split-logfiles

# you don't need to test if it is open
#$isopen = 0;

my $myfile = "/var/tmp/test.log";

# no reason to do this testing
#    unless($isopen and -f $myfile) {

# open the happy file here, but you may want to use >> if
# you need to append rather then overwrite on each run
open MYHAPPYFILE, ">$myfile" or 
    die "Error opening $myfile";

# don't need to test if it is open because we 
# are dying if it isn't
#      $isopen = 1;
#    }

while (my $log_file = <STDIN>) {
    printf MYHAPPYFILE "%s", $log_line;
}
exit 0;
[download]

And without commments:

#!/usr/bin/perl
use strict;

my $myfile = "/var/tmp/test.log";

open MYHAPPYFILE, ">$myfile" or 
    die "Error opening $myfile";

while (my $log_file = <STDIN>) {
    printf MYHAPPYFILE "%s", $log_line;
}

exit 0;
[download]

---

---

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.