Hi Evan. I tryed the 1st configurration you advised, and got a pretty good result. Thanks much.
We do this all of the time. The only thing to ensure is that the "high availablity" instance does not open /dev/log or /proc/kmsg. You will have to get the "system" instance that is reading /dev/log and /proc/kmsg to send its logs through to the High Availablity instance. We do this in different ways for different purposes. Choose only one.
1. Have the high availability read messages from localhost:someport where someport is NOT 514. Then have the system instance have a TCP destination of localhost:someport
2. Have the high availablity read message from a pipe that has been setup with mkfifo prior to starting the instance. Then have the system instance write to the pipe as one of its outputs.
That should take care of it.
Evan. -- Takenaka Kazuhiro <takenaka.kazuhiro@oss.ntt.co.jp> NTT OSS Center