On 12/19/06 11:52:50AM +0100, Gabor Gombas wrote:
> On Mon, Dec 18, 2006 at 06:36:49PM -0500, Jim Crilly wrote:
>
> > I would agree, when I did an install of etch a few weeks ago the use of
> > allow-hotplug caused the network to come up later in the boot process and
> > caused problems with syslog-ng remote logging. Apparently when syslog-ng
> > can't connect to one of it's destinations on startup it fails completely,
> > this is probably a bug in syslog-ng but it's definitely been exacerbated by
> > the default ifupdown configuration in etch.
>
> Yes, that's a can of worms that will have to be dealt with in the
> future. Basically any network service that supports binding to just one
> specific IP address needs to use /etc/network/if-{up,down}.d or similar
> mechanisms.
>
> Probably we'll need a mechanism saying that "service X depends on hw
> devices Y and Z, so X should be started if and when Y and Z are both
> available".
>
Isn't that what the upstart stuff Ubuntu is migrating to in fiesty is
supposed to take care of? Obviously that won't happen for etch, but since
Ubuntu's working out the kinks now it could easily work for etch+1.
Jim.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
