Another update. I made the mistake of setting the -C option once and syslog-ng had no problem creating the folders based on that options arguments. It would seem that it might be a filter issue - since those destinations never receive a message, they're never created (and I've increased the timeout it waits to open the file)? How can I verify this issue - and as you can see, about the only filter I use is netmask() which I had working at one time. I'm tried mkfifo and mknod to create the pipes - both create them but again, I still don't see any data going to them. Something is broken... On 9/26/06, Brian Loe <knobdy@gmail.com> wrote:
Okay, running it with debug and verbose (-d -v) this is all I get in the log (allmessages as defined by syslog-ng configuration): Sep 26 12:57:08 machine syslog-ng[151718]: syslog-ng starting up; version='2.0rc1' Sep 26 12:57:08 machine syslog-ng[151718]: Initializing destination file writer; template='/data/logs/$YEAR$MONTH$DAY.allmessages.log', filename='/data/logs/20060926.allmessages.log'