From owner-freebsd-questions Tue Dec 7 7:10:42 1999 Delivered-To: freebsd-questions@freebsd.org Received: from relay2.smtp.psi.net (relay2.smtp.psi.net [38.8.188.2]) by hub.freebsd.org (Postfix) with ESMTP id 5F0F614CA8 for ; Tue, 7 Dec 1999 07:10:40 -0800 (PST) (envelope-from chuck.burdick@tradingtechnologies.com) Received: from [38.157.25.10] (helo=tt-evanston-fw-1.) by relay2.smtp.psi.net with smtp (Exim 1.90 #1) id 11vMG7-00008u-00; Tue, 7 Dec 1999 10:10:32 -0500 Message-ID: From: "Chuck Burdick (TT)" To: 'Ben Smithurst' Cc: freebsd-questions@freebsd.org Subject: RE: /var/run/log missing Date: Tue, 7 Dec 1999 09:10:19 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 -----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