-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The Thursday 2007-05-31 at 14:35 -0600, Darryl Gregorash wrote:


> > > Restart syslog.
> Reload, actually, which simply suspends klogd's logging until syslog-ng
> receives a HUP, then resumes klogd -- sending syslog-ng a HUP causes it
> to re-read its config file. With a restart, both are stopped, then
> restarted, with a possible loss of some log information.
> >
> > Very probably that would work, but it is the last resource so that the 
> > bug can be investigated.
> My first guess is that somehow syslog-ng's internal data table has
> become corrupted, resulting in the firewall log messages somehow going
> to the current tty. I think that is going to be a very difficult bug to
> track down.

That's true.

> Suggest you simply restart, keep an eye on it, and see if
> the problem returns.

Somebody reported a very similar problem not a month ago, but I don't 
remember the message.

[...]

Here: 

<http://lists.opensuse.org/opensuse/2007-05/msg02084.html>


> BTW, are you still getting information logged to /var/log/firewall?

Now that you mention it, maybe no, then maybe there are no intrussions 
now. I'll fire up the donkey and see.

[...]

Yes, I get them into the firewall log, and if I switch to a tty, I get 
them too. in there.

I have reported this to bugzilla, #279904

- -- 
Cheers,
       Carlos E. R.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQFGX/B8tTMYHG2NR9URArVrAJ9myf4tfROadRHGl2E2dhk7MgTakACgjVOL
WxrtJ48CNDV2KOBeq2HIUTE=
=gIxa
-----END PGP SIGNATURE-----

-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to