Hello, dear monks!

I want to store net-acct's logs in the PostgreSQL database.
Program itself doesn't allow this, so I used File::Tail to consequentally read it's logfile.
But now I have another idea, e.g. to substitute program's logfile with fifo and read the data from it.
I tested it with the following (very simple) script: 

#! /usr/bin/perl -w

use strict;

my $fifo = "/var/log/net-acct/net-acct.log";

while (1) {
        open(FIFO, "< $fifo") or die "Can't open fifo $fifo: $!\n";
        while (<FIFO>) {
                print;
        }
        close(FIFO) or die "Can't close fifo $fifo: $!\n";
}

[download]

Everything seems to work just fine, so I want to ask you is there are things I should be aware of then working with named pipes?
Or even more generally is it a good idea at all?

In reply to named pipe question by Kolyan

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.