syslogd

[Miguel Covas]

I have an installation with 4 N4000 servers and 3 L1000 auxiliary machines. We have been redirecting the system logs to one of the servers.
In that server we manage the log files: we log to syslog.log and to operator.log. Every business day we automatically make a backup of operator.log, truncate the file to zero, digitally sign the backup and there it goes to the vault.
Some months ago, the server which hosts the logging lost the network connection during then minutes AND during that time one of the communications machine failed to transfer a file to that same server AND the operator didn't notice AND we had a busy day after...

So I decided to add a new machine to receive all the logs, a cute small Linux.

It works, but we receive duplicate messages due to the forwarding that we put on the first "logging" server. It is very handy for us to maintain a centralized logging on the N server (If only for the easy way of making backups, signing, etc.) so I would like to know if there is a way to emulate the behavior of Linux syslogd which does not forward messages received from other hosts (except with -h option).

I can install a second Linux machine, but...I don't know.
I need a intellectual sparring!!

[Sandip Ghosh]

There is a software from 3com which act as a syslogd server. You can install that Software to any of the NT desktop and redirect all the syslogd messages to that Server.

Sandip