From owner-freebsd-questions Mon Sep 22 22:17:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA17998 for questions-outgoing; Mon, 22 Sep 1997 22:17:47 -0700 (PDT) Received: from gdi.uoregon.edu ([128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA17988 for ; Mon, 22 Sep 1997 22:17:44 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id WAA06451; Mon, 22 Sep 1997 22:17:32 -0700 (PDT) Date: Mon, 22 Sep 1997 22:17:32 -0700 (PDT) From: Doug White Reply-To: Doug White To: Keith Spencer cc: freebsd-questions@FreeBSD.ORG Subject: Re: syslogd not working! In-Reply-To: <199709230254.MAA22674@smmcroute.smmc.qld.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Sep 1997, Keith Spencer wrote: > Hi all, > I have noticed (I can't help but notice...my fbsd root keeps sending > me mailto the effect) that my syslogd may not be working. > at boot the report is...syslogd can't bind to something > and says it isn't able to take requests or something. The error probably looks like: syslogd: can't bind to socket: (some other error probably) I need to know the entire error message so I can pin down the cause. Usually this comes up if the ethernet interface isn't set properly. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major Spam routed to /dev/null by Procmail | Death to Cyberpromo