The collegue of mine came across a problem that developed into an interesting solution that I decided to share with the world. Actually, I think the world is pretty much aware of the solution, but just in case that I will ever be looking for this solution again, I’ll have it handy here.<\/p>\n
The task at hand was to do some processing of the logs on the fly. The The original piece of code looked something like this:<\/p>\n The problem came with <\/p>\n First approach was to nest the pipe reading into an endless loop like this:<\/p>\n While it worked, it wasn’t a very nice looking solution. A couple of alternative ideas that involved signal handling and A much better looker approach was found in the book by W. Richard Stevens ” UNIX Network Programming, Volume 2, Second Edition: Interprocess Communications”. The idea is simpe – the same script that opens the named pipe for reading, should open the same pipe for writing. This way, the pipe will stay open as long as the script is working.<\/p>\n The following code works:<\/p>\n A minor improvement was made after reading Simple and elegant – just as code should be.<\/p>\n Drop me a line if you know of any other ways to improve the snippet above.<\/p>\n\n","protected":false},"excerpt":{"rendered":"\nsyslog<\/code> was configured to filter the appropriate logs into a named pipe and a Perl script was written to read from the said pipe and do all the processing.<\/p>\n\r\nopen (SYSLOG, \"<$named_pipe\") \r\n or die \"Couldn't open $named_pipe: $!\\n\";\r\n\r\nwhile (
syslog<\/code> daemon restarts. Every time the syslog<\/code> was stopped, the EOF was sent to the pipe and the script stopped reading it.<\/p>\n\r\nwhile (1) {\r\n open (SYSLOG, \"<$named_pipe\") \r\n or die \"Couldn't open $named_pipe: $!\\n\";\r\n\r\n while (kill -HUP<\/code> came around but were also disregarded.<\/p>\n\r\nopen (SYSLOG, \"<$named_pipe\") \r\n or die \"Couldn't open $named_pipe for reading: $!\\n\";\r\n\r\nopen (SYSLOG_W, \">$named_pipe\") \r\n or die \"Couldn't open $named_pipe for writing: $!\\n\";\r\n\r\n\r\nwhile (
perldoc -f open<\/code> which suggested that the same file can be open for both reading and writing with a single open<\/code>. Here is the changed code:<\/p>\n\r\nopen (SYSLOG, \"+<$named_pipe\") \r\n or die \"Couldn't open $named_pipe: $!\\n\";\r\n\r\nwhile (