On Sun December 3 2006 08:31, Chuck wrote:
> On Sunday 03 December 2006 09:25, Michael S. Zick wrote:
>
>
> will check all this out. thanks... this is a production machine and when i
> reboot it on those rare occasions very late at night, i need it to boot fast
> as possible with no unnecessary delays as it takes a large number of our
> sevices down during that time. why someone would introduce a 2 second delay
> between ip assignments is beyond me. unless someone added a delay for reading
> diag messages then forgot to remove it.
>
Just guessing on insufficient knowledge -
This new udevd is part of the change to parallel initialization;
Which is supposed to speed up the boot process.
The parallel initialization is a dependency guided system;
Could be that does not have all the rough edges smoothed out.
I 'fixed' mine by building the required ethernet drivers into
the kernel rather than let the system auto-load the modules.
(Three nics, two pci, one usb)
Now that is not a 'fix' of the problem - but a work-around to
get my kernel to boot within a reasonable amount of time.
Since this is only a personal-use machine, not a production
machine; I just said: "good enough for now" and went on to
more pressing issues here without really running down the
prime cause.
Mike
>
> > On Sun December 3 2006 05:50, Chuck wrote:
> > > On Sunday 03 December 2006 00:28, Herbert Poetzl wrote:
> > >
> > >
> > > this is during boot when initializing the ethx adapters.
> > >
> >
> > I noticed that myself on a Debian/Etch system - I suppose
> > any distro that follows their lead (uses the same udevd)
> > might have the same symptoms;
> >
> > Look for: /etc/udev/rules.d/z25_persistent-net.rules
> > which is generated at runtime, during boot,
> > by /etc/udev/persistent-net-generator.rules
> >
> > If you do not intend to be changing nic's in the box
> > in-between boots, then that rule generator only needs
> > to run once per life-time of the machine - not once
> > per every boot.
> >
> > I don't have my hands on your set-up - so I can't say
> > what/how to make the changes to your configuration files,
> > but that is the 'slow to initialize' ethernet nics problem
> > area.
> >
> > Believe me, you do not want to plug in a usb-nic if you want
> > a fast boot - it will eventually boot but you could swear
> > the kernel hung while waiting.
> >
> > Mike
> > >
> > > > On Fri, Dec 01, 2006 at 10:32:12PM -0500, Chuck wrote:
> > > >
> > > > > i am assuming this behavior is in recent iproute2 changes. previously
> > > > > on an x86 machine last year, 140 ip addys on one nic would load very
> > > > > fast.
> > > > >
> > > > > now, on amd64 current versions, it pauses 2 whole seconds between ip
> > > > > addys!!
> > > >
> > > > when you add them? remove them? or just view them?
> > > >
> > > > could be an overeager nameservice reverse lookup
> > > > trying to find a name to your IPs :)
> > > >
> > > > HTH,
> > > > Herbert
> > > >
> > > > > it is intolerable. does anyone have a fix for this or know what causes
> > > > > it?
> > > >
> > > > too little information ...
> > > >
> > > > best,
> > > > Herbert
> > > >
> > > > > --
> > > > >
> > > > > Chuck
> > > > >
> > > > > _______________________________________________
> > > > > Vserver mailing list Vserver@list.linux-vserver.org
> > > > > http://list.linux-vserver.org/mailman/listinfo/vserver
> > > >
> > >
> > _______________________________________________
> > Vserver mailing list
> > Vserver@list.linux-vserver.org
> > http://list.linux-vserver.org/mailman/listinfo/vserver
> >
>
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Received on Sun Dec 3 15:15:46 2006