Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 May 2009 11:53:19 +0200
From:      Willem Jan Withagen <wjw@digiware.nl>
To:        Nicolas Blais <nicblais@clkroot.net>
Cc:        freebsd-current@freebsd.org
Subject:   Re: syslogd starting before IPv6 network is up
Message-ID:  <4A1BBC0F.2000502@digiware.nl>
In-Reply-To: <7061d9f50905250749n1c152f0fs41f7042ac374da82@mail.gmail.com>
References:  <7061d9f50905230958n5fd7d434t790a964e79511d6b@mail.gmail.com>	 <4A1853A7.8080606@digiware.nl>	 <7061d9f50905231257n29d9e75ehb827ffdc9c077353@mail.gmail.com>	 <4A1858CE.8050803@withagen.nl> <7061d9f50905250749n1c152f0fs41f7042ac374da82@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Nicolas Blais wrote:
> On Sat, May 23, 2009 at 4:13 PM, Willem Jan Withagen <wjw@withagen.nl 
> <mailto:wjw@withagen.nl>> wrote:
> 
>     Nicolas Blais wrote:
> 
>         On Sat, May 23, 2009 at 3:51 PM, Willem Jan Withagen
>         <wjw@digiware.nl <mailto:wjw@digiware.nl>>wrote:
> 
>             Nicolas Blais wrote:
> 
>                 I migrated one of my 8-CURRENT (Thu May 21) box to IPv6
>                 and since then, I
>                 get the following message at boot:
> 
>                 syslogd: bind: Can't assign requested address
>                 syslogd: bind: Can't assign requested address
>                 syslogd:
>                 child pid 250 exited with return code 1
> 
>                 and syslogd obviously fails to start. Apparently this
>                 problem has been
>                 reported before, but no actual solution other than start
>                 syslogd from
>                 rc.local was given.

> I tried disabling the firewall and it didn't  fix the problem.
> 
> I have attached a dmesg -a with RC_DEBUG="YES"

So you can run syslogd once the whole system is up and running?
Because that is what the rc.local suggests.

I'm not using the -s open, I've used the -A option to actually specify the 
addresses I want to listen on. And if you don't want to receive anything 
from other systems. You might also forgo the option of opening a network 
socket at all using -s -s.

--WjW



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A1BBC0F.2000502>