From owner-freebsd-questions Tue Sep 23 18:48:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA20679 for questions-outgoing; Tue, 23 Sep 1997 18:48:57 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA20672 for ; Tue, 23 Sep 1997 18:48:52 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id LAA01226; Wed, 24 Sep 1997 11:18:42 +0930 (CST) Message-ID: <19970924111842.37223@lemis.com> Date: Wed, 24 Sep 1997 11:18:42 +0930 From: Greg Lehey To: Keith Spencer Cc: freebsd-questions@FreeBSD.ORG Subject: Re:syslogd STILL not working! References: <199709240023.KAA24225@smmcroute.smmc.qld.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199709240023.KAA24225@smmcroute.smmc.qld.edu.au>; from Keith Spencer on Wed, Sep 24, 1997 at 11:38:17AM +1000 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Sep 24, 1997 at 11:38:17AM +1000, Keith Spencer wrote: > Hi Greg... > Hope you are feeling better from flu. > >>> During boot sequence: >>> syslog: bind: Can't assign requested address >>> syslog:child pid 59 exited with return code 1 >>> ....what does that mean : ^ o ? >> >> It means it stopped because of an error. >> >>>> Is syslogd running? If it isn't, what happens if you try to start it? >>>> Greg >>> .... How do I do that Greg? >> >> # syslogd >> >> But it will die again. >> >>> BTW I notice in rc.conf that there are no syslog flage set...does >>> this matter? >> >> You should have: > >> syslogd_enable="YES" # Run syslog daemon (or NO). >> syslogd_flags="" # Flags to syslogd (if enabled). > > I do have this. > >> Your problem looks like the lack of the file /var/run/log. You should >> have: >> # ls -l /var/run/log >> srw-rw-rw- 1 root bin 0 Sep 19 16:31 /var/run/log >> If you don't have it, do >> # mkfifo /var/run/log > I didn't have one! there was a /var/log directory but not a > /var/run/log file. : ^ ( Well, no, it's not a file, it's a fifo. Did you create it the way I said? > I feel discriminated against. Damn. You've found out :-) > Any way I created one and rebooted. You didn't need to reboot. Starting syslogd would have done it. > But appeared to give same boot messages. But then whilst in f bsd I > did do # syslogd and there were no complaints. I checked rrot mail > straight after and found no new error mail msgs. just the past ones > ...here are the old messages. Is this the newest message in the mail? I'd say that it hasn't complained again. But this comes from cron. > Do you think it is working now??? I don't know. What does the following command say? $ ps aux | grep syslog >> I'd like to know how you came not to have it, though. Did you move >> /var? >> Greg > As far as I know I did nothing of that sort. I installed and removed > bsd with a diskmanager several times...but the last and now > successful time was from a clean bsd partition. Strange. Greg