Date: Wed, 28 Aug 1996 09:28:19 -0700 From: "Neil C. Jensen" <njensen@salsa.habaneros.com> To: "'dwhite@resnet.uoregon.edu'" <dwhite@resnet.uoregon.edu> Cc: "'questions@freebsd.org'" <questions@freebsd.org> Subject: RE: lost /dev/log Message-ID: <01BB94C3.40C97A20@jalapeno.habaneros.com>
next in thread | raw e-mail | index | archive | help
Problem solved. I had syslog commented out in /etc/services. Once I uncommented it and restarted inetd.conf, /dev/log appeared and logging started. The boot messages then appeared in the /var/log/messages file. One question, though; I had disabled syslog in services while following a security checklist from AUCERT. Why is syslog a security risk? Why won't syslog work without the TCP socket and just the /dev/log? Neil ---------- From: Doug White[SMTP:dwhite@gdi.uoregon.edu] Sent: Wednesday, August 28, 1996 12:34 PM To: Neil C. Jensen Cc: questions@freebsd.org Subject: RE: lost /dev/log On Wed, 28 Aug 1996, Neil C. Jensen wrote: > No, as a matter of fact, syslogd is not running. I have tried to start > it manually, but it will not run. All my /var/log files are empty. What do you mean by 'not run'? What error do you get? Sounds like the binary is corrupted. It is really odd that /var/log/messages is empty -- the boot messages should go there (maybe they can't because syslogd isn't running). > > For some some reason, I did not end up with a /dev/log during my install > > of 2.1.5R. I do have /dev/klog, though. > > /dev/log is a UNIX domain socket for syslogd(8). Is syslogd running? Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01BB94C3.40C97A20>