I would put an strace (or whatever bsd has for that) on syslogd. Whenever your program generates a message, you should see activity in that process. If yes, there is something wrong with syslogds config, if no, the fault lies with Sys::Syslog.
In reply to Re: Sys::Syslog Troubles
by jethro
in thread Sys::Syslog Troubles
by pileofrogs
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |