From owner-freebsd-questions Tue Sep 23 18:39:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA20113 for questions-outgoing; Tue, 23 Sep 1997 18:39:13 -0700 (PDT) Received: from smmcroute.smmc.qld.edu.au (smmcdialin.ultra.net.au [203.56.101.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA20108 for ; Tue, 23 Sep 1997 18:39:07 -0700 (PDT) Received: from station1.ultra.net.au (cyan.colour.ultra.net.au [203.20.237.160]) by smmcroute.smmc.qld.edu.au (8.7.5/8.7.3) with SMTP id KAA24225; Wed, 24 Sep 1997 10:23:26 +1000 (EST) Message-Id: <199709240023.KAA24225@smmcroute.smmc.qld.edu.au> Comments: Authenticated sender is From: "Keith Spencer" Organization: St Margaret Marys College To: freebsd-questions@FreeBSD.ORG, Greg Lehey Date: Wed, 24 Sep 1997 11:38:17 +1000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re:syslogd STILL not working! Priority: normal X-mailer: Pegasus Mail for Win32 (v2.53/R1) Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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. : ^ ( I feel discriminated against. Any way I created one and rebooted. 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. Do you think it is working now??? > 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. Thanks >From daemon Sun Sep 21 19:00:01 1997 Received: (from root@localhost) by smmc2.smmc.qld.edu.au (8.8.5/8.8.5) id TAA00188; Sun, 21 Sep 1997 19:00:01 +1000 (EST) Date: Sun, 21 Sep 1997 19:00:01 +1000 (EST) Message-Id: <199709210900.TAA00188@smmc2.smmc.qld.edu.au> From: root (Cron Daemon) To: root Subject: Cron /usr/sbin/newsyslog X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: Status: O newsyslog: could not restart syslogd: No such process Keith Spencer Teacher...St Margaret Marys College Townsville Australia