syslogd vs console

Subject: syslogd vs console
From: Christopher Svenstedt (svenstedt@yahoo.se)
Date: Mon Nov 27 2000 - 11:12:27 CET

• sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Next message: R. W. Rodolico: "Re: syslogd vs console"
• Previous message: Mirek Novak: "(no subject)"
• Next in thread: R. W. Rodolico: "Re: syslogd vs console"
• Reply: R. W. Rodolico: "Re: syslogd vs console"
• Reply: Christopher Svenstedt: "RE: syslogd vs console"

Hi,

Problem:

Syslogd always forces itself to log to /dev/console.
When using -d I get a message like:
"Called fprintlog, logging to CONSOLE /dev/console
.... No such file or directory".
It does not create /dev/log socket and if I use kill
-SIGHUP <pid> it leaves this world.
I do not use the /etc/services file.
Using v1.3-31 and Kernel 2.2.14-5

Anyone?

Regards,
Christopher Svenstedt
"Be liberal in what you accept, and conservative in
what you send." -- Jon Postel, RFC1122

_____________________________________________________
Do You Yahoo!?
Ditt_namn@yahoo.se - skaffa en gratis mailadress på http://mail.yahoo.se

• Next message: R. W. Rodolico: "Re: syslogd vs console"
• Previous message: Mirek Novak: "(no subject)"
• Next in thread: R. W. Rodolico: "Re: syslogd vs console"
• Reply: R. W. Rodolico: "Re: syslogd vs console"
• Reply: Christopher Svenstedt: "RE: syslogd vs console"

This archive was generated by hypermail 2b25 : Mon Nov 27 2000 - 11:19:15 CET