I'm trying to figure out under what conditions a text file would not be readable on the filesystem while a perl script is writing to that file.

Here is some test code:

===================================
#!/usr/bin/perl -w

use strict;

print "Begin...\n";
for ( my $i = 0; $i < 5; $i++ )
{
        print "$i...\n";
        sleep 2;
}
===================================
[download]

I execute this script like this:

$ ./populate.pl > data.txt&
[download]

So I background it, because I expect that the script will continue writing while I execute this next command:

$ tail -f data.txt
[download]

Now 'tail' just sits there, and doesn't output anything until the populate.pl script is complete.

~HOWEVER~

If I do this with a straight bash script, as follows:

while [ 1 ]; do echo "some text..."; done > data.txt&
[download]

..and then do a 'tail -f' on the data.txt file, I can see it's content while the bash script is writing to it.
In both cases I am using '>' to continuously write, and not '>>' to append.

I currently do have other perl scripts which are executed as './script.pl > output.txt', and I am able to do a 'tail' on the output file while the script is running, without any problems.

But the first script above doesn't allow me to tail the data.txt file, so I'm trying to understand the difference, or what would prevent the 'tail' command from working in the first scenario. Anyone have any ideas?

(Please note, I know there are many other ways to accomplish reading from a file while it is being written to; this is just an exercise to increase my understanding of what exactly is going on in this particular situation :)

Bobby