Mailinglist Archive: opensuse (4626 mails)
| < Previous | Next > |
RE: [opensuse] syslog stuff
- From: "Greg Wallace" <gregwallace@xxxxxxxxxxx>
- Date: Thu, 18 Jan 2007 01:02:14 -0600
- Message-id: <000d01c73ace$95ff9ee0$6501a8c0@Twr745>
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
A list of about 40 files
>>> 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
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@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
>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
A list of about 40 files
>>> 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
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@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |