Hi, Sorry - maybe I misunderstood. On the machine you want to send the log data from you have an entry like *.* @receiving_machine_name in /etc/syslog.conf This sends all messages to UDP port 514 IIRC. On the remote machine you wish to store the logs on you start the syslog daemon with 'syslogd -r' to accept the output. Isn't that what you've done? Actually I've just realised that the receiving machine selector field in /etc/syslog.conf is the important mechanism - not the sending machines file. Sorry about that. Maybe it's going to be simpler to simply write a sed/grep/awk script to pick out the sending machines data and save it into a file every hour or so using cron. Andy On Monday 04 August 2003 15:35, Markus Hochmann wrote:
Andy Bennett wrote:
On Monday 04 August 2003 15:03, Markus Hochmann wrote:
I set up a loghost on a SuSE 8.2 prof. (syslogd -r). Another pc sends its logs to it, thats all ok. But know I get all these msgs and want them to be filtered for each host. <date> <client> <sometext> eg: Aug 4 15:57:12 abakus markus: The text of a logger command (But ofcourse all other msgs, too, not only the ones of logger!) So that eg. there is a log 'abakus.log' which consists of all logs from abakus.
What happens when you simply change the name of the output files in /etc/syslogd.conf on machine abakus?
Then it will be locally logged, but I want it to be logged remotely:
Client1-------Loghost----Client1.log Client2---´ `---Client2.log
Greetz Markus