Date: Tue, 7 Dec 1999 09:10:19 -0600 From: "Chuck Burdick (TT)" <chuck.burdick@tradingtechnologies.com> To: 'Ben Smithurst' <ben@scientia.demon.co.uk> Cc: freebsd-questions@freebsd.org Subject: RE: /var/run/log missing Message-ID: <E9C5FE6F6ED8D111A87C00062B000D24B7A432@chnapdc.tradingtechnologies>
next in thread | raw e-mail | index | archive | help
I found the problem. By running 'syslogd -d', I saw that it was complaining about udp. Then I remembered that I had hacked (in the butcher sense) through my /etc/services. Apparently I had inadvertantly commented the syslog entry. Thus syslogd didn't know which port to bind and crapped out. Thanks, Chuck <EDITED> -----Original Message----- From: Ben Smithurst [mailto:ben@scientia.demon.co.uk] Sent: Monday, December 06, 1999 6:25 PM 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? 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?E9C5FE6F6ED8D111A87C00062B000D24B7A432>