On Wed, 15 Nov 2000, R. W. Rodolico wrote:
> Ran syslogd with the -d flag set, captured the output to the attached
> file. Only problem I noted was that it errored when trying to open a
> file named /dev/log. I can find no entry /dev/log in /etc/syslogd.conf.
>From your attachment:
Called logerr, msg: cannot create /dev/log
logmsg: syslog.err<43>, flags 4, from stargazer, msg syslogd: cannot
create /dev/log: Invalid argument
syslogd reads the messages from the Unix domain socket /dev/log.
Why can't it create /dev/log?
Stop your syslog and make sure no /dev/log file exists; if it does it will
get in the way.
pilchuck:/home/reed# ls -l /dev/log
srw-rw-rw- 1 root root 0 Nov 15 06:28 /dev/log
pilchuck:/home/reed# /etc/init.d/sysklogd stop
Stopping system log daemon: klogd syslogd.
pilchuck:/home/reed# ls -l /dev/log
ls: /dev/log: No such file or directory
pilchuck:/home/reed# /etc/init.d/sysklogd start
Starting system log daemon: syslogd klogd.
pilchuck:/home/reed# ls -l /dev/log
srw-rw-rw- 1 root root 0 Nov 15 22:24 /dev/log
> executed following command:
> sudo logger -f /var/log/syslog This Is A Test
> sudo logger -f /tmp/joe This is a Test
To test, try something like:
$ logger -p user.info This is a test
$ tail /var/log/user.log
Nov 15 22:29:09 pilchuck reed: This is a test
It is weird that some of your logs work and some don't.
Jeremy C. Reed
....................................................
BSD software, documentation, resources, news...
http://bsd.reedmedia.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]