Date: Wed, 28 Aug 1996 19:34:20 -0700 (PDT) From: Doug White <dwhite@gdi.uoregon.edu> To: "Neil C. Jensen" <njensen@salsa.habaneros.com> Cc: questions@freebsd.org Subject: RE: lost /dev/log Message-ID: <Pine.BSI.3.94.960828193302.361A-100000@gdi.uoregon.edu> In-Reply-To: <01BB949E.E1134260@jalapeno.habaneros.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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?Pine.BSI.3.94.960828193302.361A-100000>