From owner-freebsd-hackers  Sun Mar 26 02:27:31 1995
Return-Path: hackers-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA09196 for hackers-outgoing; Sun, 26 Mar 1995 02:27:31 -0800
Received: from vmbb.cts.com (vmbb.cts.com [192.188.72.18]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA09185 for <hackers@freebsd.org>; Sun, 26 Mar 1995 02:27:28 -0800
Received: from io.cts.com by vmbb.cts.com with smtp
	(Smail3.1.28.1 #9) id m0rspXV-00005VC; Sun, 26 Mar 95 02:27 PST
Received: (from root@localhost) by io.cts.com (8.6.11/8.6.9) id CAA00220 for hackers@freebsd.org; Sun, 26 Mar 1995 02:27:18 -0800
From: Morgan Davis <root@io.cts.com>
Message-Id: <199503261027.CAA00220@io.cts.com>
Subject: syslogd error: bind: can't assign address
To: hackers@FreeBSD.org
Date: Sun, 26 Mar 1995 02:27:18 -0800 (PST)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 436       
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

I think there might be a glitch in the logic in the -current rc
script.  It appears to initiate syslogd before the system's hostname
has been set up.  When I boot up, I get an error like this just after
probing:

		syslogd: bind: cannot assign specified address

...and no syslogd process is to be found.  If I log in and manually
enter "syslogd", it dumps a screen of startup progress, and a syslogd
process is then in memory.

Ideas?