Date: Tue, 7 Dec 1999 00:24:34 +0000 From: Ben Smithurst <ben@scientia.demon.co.uk> To: "Chuck Burdick (TT)" <chuck.burdick@tradingtechnologies.com> Cc: freebsd-questions@freebsd.org Subject: Re: /var/run/log missing Message-ID: <19991207002434.B4038@strontium.scientia.demon.co.uk> In-Reply-To: <E9C5FE6F6ED8D111A87C00062B000D24B7A42F@chnapdc.tradingtechnologies> References: <E9C5FE6F6ED8D111A87C00062B000D24B7A42F@chnapdc.tradingtechnologies>
next in thread | previous in thread | raw e-mail | index | archive | help
Chuck Burdick (TT) wrote:
> For some reason, my system is missing /var/run/log. This is the Berkley
> socket device that /dev/log points to and what syslogd uses. Thus syslogd
> won't run (just exits w/ code 1).
You shouldn't need to create it. In fact, you can't in a way syslogd
would like: the only way to create a socket is with bind (correct me if
I'm wrong here), and if the socket exists syslogd's bind call would fail
with EADDRINUSE. syslogd should create it when it calls bind(2). If it's
not doing so, what error message is it giving?
--
Ben Smithurst | PGP: 0x99392F7D
ben@scientia.demon.co.uk | key available from keyservers and
| ben+pgp@scientia.demon.co.uk
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991207002434.B4038>