SG/MC syslogd in pak?

[Kai Bergmann]

There are two L-class running HA SG/MC. I like to run the syslogd as HA-Solution listening for other hosts writing logs to the pak.
How can i run the syslogd in MC/SG listening to the clusternodes and the other hosts?

Kai Bergmann, work-center gmbh, bremen, germany

[Rainer von Bongartz]

syslogd collects messages from the UNIX domain socket /dev/log.un, the named pipe /dev/log, and from the kernel log device /dev/klog.

theese devices are specific to your box so you cannot share them with MC/SG

[Kai Bergmann]

Thanks, I know the prob about hte socket.
In comp.os.hpux..? i?ve read before to start the syslogd to listen to another port than 514.
Maybe from a chroot,or should we try to take the syslog_ng to our hpux11.0 ? Any other suggestion for runnig logs in pak?

[Alex_17]

Hi, I think you can't do that because the syslogd only works with your machine.

[James R. Ferguson]

Hi Kai:

The 'syslogd' daemon has the capability of forwarding messages to another host.

For instance, as the man pages (1M) for 'syslogd' indicate, the following entries in /etc/syslog.conf :

*.emerg *
*.emerg @admin

would enable "emerg" messages to be written to all logged-in users' terminals, and forwarded to the host "admin".

I'm note sure for what use you would like to leverage this capability in an MC/ServiceGuard cluster. The normal configuation does, of course, write package state changes into the syslog; and for debugging problems, the amount of diagnostic logging can be increased (see KB document #UXSGKBAN00000040).

I suppose you could forward all 'daemon' facility traffic to each node's syslog file. The setup would have to be specified in every node's /etc/syslog.conf for every host (node) by hostname.

Hopefully you find this helpful.

...JRF...