On Wednesday, January 17, 2007 @ 11:51 PM, Darryl Gregorash wrote:
On 2007-01-17 22:10, Greg Wallace wrote:
On Wednesday, January 17, 2007 @ 8:24 PM, Darryl Gregorash wrote:
<snip> > grep SFW2 /var/log/messages | grep IN= >
Thousands of lines of output
OK, so much for that idea. I'm sure glad, though, that no bug report has to be filed against the kernel :-)
<note to self: send Greg a typing tutor program :-) >
grep IN= /etc/syslog-ng/syslog-ng.conf.in
No such file or directory
Say what? What's the output of
rpm -ql syslog-ng
BTW, what is the result of this: ls -l /var/log/firewall
ls: cannot access /var/log/firewall: No such file or directory
Maybe that's the problem. There is no separate log file set up for the firewall so all of the firewall messages get dumped into messages. Is
A list of about 40 files there
somewhere where you can define a specific separate log file for firewall messages? If the file does not exist, the syslog daemon will create it -- assuming, of course, that it is given any reason to do so.
So having thousands of lines of output generated by the firewall isn't reason enough to create the file? How can I give it a reason to create it? Greg W -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org