This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C1EA1B.17FDF360 Content-Type: text/plain; charset="iso-8859-1" I'm running syslog-ng on AIX 4.3.3 and while it works fine for system log calls, it doesn't seem to connect to a defined pipe and send information to it based on a logger call... below is a test conf file that I'm using. Send a message with logger is shows up in the d_mesg, but not to the d_pipe (Netcool is attached to the pipe. lsof shows the /var/adm/messages file being open, and again not the pipe... source s_sys { unix-dgram ("/dev/log"); internal (); } destination d_mesg { file("/var/adm/messages"); }; destination d_pipe { pipe("/var/adm/mypipe"); }; log { source (s_sys); destination (d_mesg); destination (d_pipe); }; Any one seen this, or something like it? TIA, Andrew ------_=_NextPart_001_01C1EA1B.17FDF360 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">AIX 4.3.3 and pipe problem? I'm running syslog-ng on AIX 4.3.3 and while it works = fine
for system log calls, it doesn't seem to connect to = a defined
pipe and send information to it based on a logger = call...below is a test conf file that I'm using. Send a = message with
logger is shows up in the d_mesg, but not to the = d_pipe (Netcool
is attached to the pipe. lsof shows the = /var/adm/messages file
being open, and again not the pipe...
source s_sys {
= = unix-dgram = ("/dev/log");
= = internal = ();
= }
destination d_mesg {
= = = file("/var/adm/messages");
= = };destination d_pipe {
= = = pipe("/var/adm/mypipe");
= = };log {
source = (s_sys);
destination (d_mesg);
destination (d_pipe);
};
Any one seen this, or something like it?
TIA,
Andrew
------_=_NextPart_001_01C1EA1B.17FDF360--