From: Gene Matusovsky (gene@bdc.cv.net)
Date: Fri Aug 02 2002 - 17:57:52 EDT
Greetings Sun Managers,
Our team believes that we have found a bug in Solaris 2.7 Syslog daemon
when logging to named pipes/FIFOs.
We are using an application that is designed to output to syslog named
pipes. We created a FIFO named pipe file,
mknod /var/log/ourlogfile.log p
Created an entry in syslog.conf
local7.info /var/log/ourlogfile.log
We took care to avoid common pitfalls with syslog, by making sure to
delimit by tabs, have syslog.conf file under 20 lines, and having our
named pipe file previously created.
We then restart syslog, /etc/init.d/syslog stop or cat
/etc/syslog.pid|xargs kill;/etc/init.syslog start
Here is where the error occurs. We know that the Named Pipe FIFO file is
good because when we tail -f /var/log/ourlogfile.log and in another
window run echo "Test" > /var/log/ourlogfile.log, we see the test
message come through fine using echo. However, when we use the syslog
facility
logger -p local7.info "Test message".
Nothing comes through. We tried this on several Solaris 2.7 boxes with
the latest cluster patch installed without any success. Logging to a
regular text file seems to work just fine, the problem consistently
occurs using Named Pipes under Solaris 2.7.
Solaris 2.8 seems to support named pipes with no problems. Using tail -f
/var/log/ourlogfile.log and a logger statement, logger -p local7.info
"Test message". Works fine under Solaris 2.8.
Any suggestion would be appreciated,
Gene Matusovsky
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:42 EDT