* Darryl Gregorash
Very strange, everything looks just fine. Is that options {} statement in the original config file, or did you add it?
No, it was in the original and was working as is ???
If the latter, try commenting it out and restarting syslog-ng. If firewall logging returns, then you can play with the options parameters to see if one of those is responsible.
If it has already been working with that options statement, then I am totally baffled.
me toooo. Restarting the firewall and/or restarting syylog-ng even specifing the config file, all have no apparent effect. The firewall log is still stopped on Friday 13th at 23:14 GMT -5 :^( The ONLY thing that I can think of that I haven't tried is restarting the entire system, which I do VERY infrequently, ie: kernel change which has bit me several times recently so I have shied away from that. Using a kernel built for 10.2 on a 10.1 system (only way to get support for my usb devices, at the time). If I don't see logs by tomorrow morning, I *will* reboot, but that doesn't look promising either. Will switch to 10.3 when it is published. Toooo many particular local configurations to change at each distro issuance :^) tks, -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org