Linux Expert <[email protected]> writes: >> Again... appears to work. >> >> However the log file takes quite a long time to starting showing any >> action, and then stay well behind the console output. >> > > Try adding the following line after your 'use warnings' line: > $|++; > > That will disable output buffering on the currently-selected > filehandle (STDOUT be default).
Doesn't appear to make any difference whatever. using `logger' to write a dozen lines to syslog that the filter would grab like: logger "FAKE Temperature above Threshold FAKE" Then pressing the command a dozen or so times... I see each print coming from the script onto the console but the fail is still zero size. If I wait long enough or write a enough fake lines. Then finally the log file startes to show some data. AFter 50 fake lines... still nothing in the log file. I'm not sure when data showed up but somewhere between 60 and 100 lines were written thru the filter, to get any data in there. And then its a suspicious looking number like what a buffer might hold, exactly 4096: ls -l log/pipe1.log -rw-r--r-- 1 root root 4096 Mar 21 19:33 log/pipe1.log It appears even when it grows, its always a number exactly divisible by 1024 -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] http://learn.perl.org/
