syslogyk wrote:

Hi!

Could you please help me with this question?

I have the following strings in my syslog-ng.conf:

source src { internal(); unix-dgram("/dev/log"); unix-dgram("/var/lib/named/dev/log"); }; ... skipped ... filter f_debug { level(debug); }; destination d_yuri { pipe("/dev/yuri_pipe"); }; log { source(src); filter(f_debug); destination(d_yuri); };

With this configuration, I execute the following commands in the first console:

mkfifo /dev/yuri_pipe cat /dev/yuri_pipe

On the other console I generate an event (for instance, "logger blablabla"). And cat /dev/yuri_pipe on the first console outputs nothing.

What's wrong in my syslog-ng.conf? Can I get events in my pipe?

Thank you in advance, Yuri P.S. Sorry, if you receive this message twice.

You have to create the pipe BEFORE starting syslog-ng, and set the priority of the log message: logger -p debug blabla -- Sandor Geller wildy@balabit.hu

On Thu, 2006-01-26 at 16:39 +0300, syslogyk wrote:

Hi!

Could you please help me with this question?

I have the following strings in my syslog-ng.conf:

source src { internal(); unix-dgram("/dev/log"); unix-dgram("/var/lib/named/dev/log"); }; ... skipped ... filter f_debug { level(debug); }; destination d_yuri { pipe("/dev/yuri_pipe"); }; log { source(src); filter(f_debug); destination(d_yuri); };

With this configuration, I execute the following commands in the first console:

mkfifo /dev/yuri_pipe cat /dev/yuri_pipe

On the other console I generate an event (for instance, "logger blablabla"). And cat /dev/yuri_pipe on the first console outputs nothing.

What's wrong in my syslog-ng.conf? Can I get events in my pipe?

You were directing only debug level messages to yuri_pipe, are you sending the test message with proper priority value? -- Bazsi