I agree the PC-DOS-Windows industry has bastardised the concept of a syslog daemon.
Syslog-ng IS the Linux system log daemon, however it performs function in much the same way as a Mainframe Daemon works and depending on my audience I have to be very specific with the reference 'syslog daemon' due its multiple meanings. If I had a big enough business I would always go for a Main Frame and rock solid O/S in lieu of a blade server and clustering despite the O/S. I still have issues with insecure comms that we use every day in the form of the collection TCP/IP. SNA forever Keep smiling Scott Carlos E. R. wrote: > > The Monday 2007-04-23 at 05:17 +1000, Registration Account wrote: > > > Dear Carlos, With your already wonderful script I can log the file as > > received however as I am aware of the RFC which defines syslog rules > > and conventions found at > > > http://www.faqs.org/rfcs/rfc3164.html > > > I need to substitute the value in <?> for the following before the > log is created. > > Yes, I understand that, but the linux syslog daemong doesn't record it in > the files. > > > > After I succeed I will be happy to provide the result. There is an > > enormous requirement for a Linux Syslog. If you wish you may wish to > > publish on web. > > There is a linux syslog daemon, you will have to rename it somehow or > people will not understand you. I don't suppose it would be difficult to > modify the existing service to record the severity number: but don't > look > at me, I have never done serious programming in linux. >
smime.p7s
Description: S/MIME Cryptographic Signature
