On 2007-05-31 14:09, Carlos E. R. wrote:
The Thursday 2007-05-31 at 22:30 +0700, Fajar Priyanto wrote:
<snip>
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. Suggest you simply restart, keep an eye on it, and see if the problem returns. BTW, are you still getting information logged to /var/log/firewall? -- Hypocrisy is the homage vice pays to virtue. -- François de La Rochefoucauld -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org