Quote:
Originally Posted by
dannytrinh
My company has a strictly policies, and doesn't like the idea to install another syslog program into the system. And I try to get the log to separate off to every daemon for easy troubleshooting/debug. Is it meant I can't separate each daemon log, under Solaris 10 by using syslogd?
Thanks,
I don't think you can do (easily) this with syslogd. Of course you can simply
pipe syslog into a filter (via a named pipe), but most people would not do that, they would use syslog-ng. That is why I recommended you use syslog-ng
Actually, if you had of posted these details first, you would have saved a lot of peoples time. For example, why not begin your post (?)
My company has a strict policy and only permits syslogd, running on Solaris 10 ......
Instead, we post answers for you, then you slowly describe your infrastructure and requirements. How about describing your requirements first next time?
Thanks.
---------- Post updated at 19:19 ---------- Previous update was at 18:38 ----------
Hint:
Quote:
A named pipe (fifo), beginning with a vertical bar (‘‘|’’) followed by a pathname. The pipe must be created with mkfifo(8) before syslogd reads its configuration file. This feature is especially useful for debugging.