No, suslogd is running OK because it is still logging to disk as well as to the
other machine, and now also to console.
Quoting dopey <[EMAIL PROTECTED]>:
> On Fri, 14 Sep 2001, Howard Lowndes <[EMAIL PROTECTED]> wrote...
>
> : ipchains on my gateway has suddenly taken to logging to the console.
> :
> : The syslog.conf file has the standard settings, but these are also
> mirrored to
> : log to another machine as well.
> :
> : The standard logging is happening, as is the logging to the other
> machine, but
> : additionally there is this logging to console.
> :
> : According to syslog.conf the only logging to console should be *.emerg
> messages.
> :
> : Has anyone any suggestions as to why, or how I can find out what is
> causing
> : ipchains to do this?
> :
> : Howard.
> `-
>
> This happens to me when syslogd dies- check to mske sure it can start
> up,
> I've had a few things inhibit this - such as a broken syslog.conf and
> no
> disk space free.
>
> hth.
>
> dopey
>
Howard.
____________________________________________________
LANNet Computing Associates <http://lannetlinux.com>
"...well, it worked before _you_ touched it!"
-------------------------------------------------
This mail sent through IMP: mail.lannet.com.au
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
