Observe the following code: 

use IO::Handle;
use strict;

$|=1;

my $io=new IO::Handle;
open LOG,">> mylofile.txt" or die "mylogfile.txt: $!";

$io->fdopen(fileno(LOG),"w+") or die $!;

$io->autoflush(1);

my $foo=0;
while(1){

        $foo++;
        printf "Iteration: %d\n",$foo;
        $io->printf("Looped in %d\n",$foo);
        sleep 2;
}

[download]

I normally don't do Windows, but since I had a VMWare session going I fired up a quick test of your problem. Ran the above code and killed it with the Task Manager and no data was harmed in the making of rhis node. (Everything I expected was in the log file!)

Peter L. Berghold -- Unix Professional
Peter -at- Berghold -dot- Net; AOL IM redcowdawg Yahoo IM: blue_cowdawg

In reply to Re: writing to logfile in a loop by blue_cowdawg
in thread writing to logfile in a loop by jarthda

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.