From owner-freebsd-hackers Sun Mar 26 02:52:44 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA10865 for hackers-outgoing; Sun, 26 Mar 1995 02:52:44 -0800 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA10821 for ; Sun, 26 Mar 1995 02:52:25 -0800 Received: from localhost (localhost [127.0.0.1]) by grunt.grondar.za (8.6.11/8.6.9) with SMTP id MAA24852; Sun, 26 Mar 1995 12:51:35 +0200 Message-Id: <199503261051.MAA24852@grunt.grondar.za> X-Authentication-Warning: grunt.grondar.za: Host localhost didn't use HELO protocol To: Morgan Davis cc: hackers@FreeBSD.org Subject: Re: syslogd error: bind: can't assign address Date: Sun, 26 Mar 1995 12:51:35 +0200 From: Mark Murray 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. I get this too, and I reported it in PR conf/273. The solution is to load syslogd _after_ the 'netstart' section in /etc/rc. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200