Re: [Vserver] iproute2 behavior problem
On Sunday 03 December 2006 11:13, Chuck wrote: > On Sunday 03 December 2006 10:48, Herbert Poetzl wrote: > > > > ahh no... these ips are for the mail server which runs on the host. they have > nothing to do with guests.. each guest brings up its own ip as it starts. > > once i can convert all our users to the change needed for namespace use, then > i will have only 2 ips for the name server and will place it into a guest. > until then it has to hog our host. > oops. just noticed.. mail server not name server :) > regardless 2 seconds between ip loading is not acceptable under any > conditions, so i want to find out what causes it and fix it. :) > > > > On Sun, Dec 03, 2006 at 07:08:30AM -0500, Chuck wrote: > > > On Sunday 03 December 2006 00:28, Herbert Poetzl wrote: > > > > > > i just tried an experiment. i placed 5 ips on an adapter on the older > > > dell x86 system and still the same behavior so it is not arch related. > > > > > > 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. > > > > what I do not understand here, why do you configure > > 140 ips when the host boots at all? wouldn't it be > > much easier to let util-vserver add the IPs per > > guest? I'd assume that this would speed up the > > configuration significantly too, as the tools do > > not run those funny scripts AFAIK :) > > > > HTH, > > Herbert > > > > > > > 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 > > > > > > > > > > -- > > > > > > Chuck > > > > > > "...and the hordes of M$*ft users descended upon me in their anger, > > > and asked 'Why do you not get the viruses or the BlueScreensOfDeath > > > or insecure system troubles and slowness or pay through the nose > > > for an OS as *we* do?!!', and I answered...'I use Linux'. " > > > The Book of John, chapter 1, page 1, and end of book > > > > > > > > > ___ > > > Vserver mailing list > > > Vserver@list.linux-vserver.org > > > http://list.linux-vserver.org/mailman/listinfo/vserver > > > > -- > > Chuck > > "...and the hordes of M$*ft users descended upon me in their anger, > and asked 'Why do you not get the viruses or the BlueScreensOfDeath > or insecure system troubles and slowness or pay through the nose > for an OS as *we* do?!!', and I answered...'I use Linux'. " > The Book of John, chapter 1, page 1, and end of book > > > ___ > Vserver mailing list > Vserver@list.linux-vserver.org > http://list.linux-vserver.org/mailman/listinfo/vserver > -- Chuck "...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. " The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] iproute2 behavior problem
On Sunday 03 December 2006 10:48, Herbert Poetzl wrote: ahh no... these ips are for the mail server which runs on the host. they have nothing to do with guests.. each guest brings up its own ip as it starts. once i can convert all our users to the change needed for namespace use, then i will have only 2 ips for the name server and will place it into a guest. until then it has to hog our host. regardless 2 seconds between ip loading is not acceptable under any conditions, so i want to find out what causes it and fix it. :) > On Sun, Dec 03, 2006 at 07:08:30AM -0500, Chuck wrote: > > On Sunday 03 December 2006 00:28, Herbert Poetzl wrote: > > > > i just tried an experiment. i placed 5 ips on an adapter on the older > > dell x86 system and still the same behavior so it is not arch related. > > > > 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. > > what I do not understand here, why do you configure > 140 ips when the host boots at all? wouldn't it be > much easier to let util-vserver add the IPs per > guest? I'd assume that this would speed up the > configuration significantly too, as the tools do > not run those funny scripts AFAIK :) > > HTH, > Herbert > > > > > 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 > > > > > > > -- > > > > Chuck > > > > "...and the hordes of M$*ft users descended upon me in their anger, > > and asked 'Why do you not get the viruses or the BlueScreensOfDeath > > or insecure system troubles and slowness or pay through the nose > > for an OS as *we* do?!!', and I answered...'I use Linux'. " > > The Book of John, chapter 1, page 1, and end of book > > > > > > ___ > > Vserver mailing list > > Vserver@list.linux-vserver.org > > http://list.linux-vserver.org/mailman/listinfo/vserver > -- Chuck "...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. " The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] iproute2 behavior problem
On Sunday 03 December 2006 10:14, Michael S. Zick wrote: we have all nic modules built into the kernel. we normally do not use modules at all for security reasons. this particular machine had to have a disk module so it would load that after the raid system since we are booting from the raid. so that is the only module loaded thanks anyway... > 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 > -- Chuck "...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. " The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] iproute2 behavior problem
On Sun December 3 2006 09:48, Herbert Poetzl wrote: > On Sun, Dec 03, 2006 at 07:08:30AM -0500, Chuck wrote: > > On Sunday 03 December 2006 00:28, Herbert Poetzl wrote: > > > > i just tried an experiment. i placed 5 ips on an adapter on the older > > dell x86 system and still the same behavior so it is not arch related. > > > > 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. > > what I do not understand here, why do you configure > 140 ips when the host boots at all? wouldn't it be > much easier to let util-vserver add the IPs per > guest? I'd assume that this would speed up the > configuration significantly too, as the tools do > not run those funny scripts AFAIK :) > I haven't done any debugging of this yet - but if I did, I would start by putting a break-point of some kind in udevd, then adding an address. What I would be looking for is if the adding of an address generates a 'udev event' similar to discovering a new card. I don't think it should, but it might be doing that. It could also just be funky scripting somewhere. Mike > HTH, > Herbert > > > > > 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 > > > > > > > -- > > > > Chuck > > > > "...and the hordes of M$*ft users descended upon me in their anger, > > and asked 'Why do you not get the viruses or the BlueScreensOfDeath > > or insecure system troubles and slowness or pay through the nose > > for an OS as *we* do?!!', and I answered...'I use Linux'. " > > The Book of John, chapter 1, page 1, and end of book > > > > > > ___ > > 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
Re: [Vserver] iproute2 behavior problem
On Sun, Dec 03, 2006 at 07:08:30AM -0500, Chuck wrote: > On Sunday 03 December 2006 00:28, Herbert Poetzl wrote: > > i just tried an experiment. i placed 5 ips on an adapter on the older > dell x86 system and still the same behavior so it is not arch related. > > 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. what I do not understand here, why do you configure 140 ips when the host boots at all? wouldn't it be much easier to let util-vserver add the IPs per guest? I'd assume that this would speed up the configuration significantly too, as the tools do not run those funny scripts AFAIK :) HTH, Herbert > > > 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 > > > > -- > > Chuck > > "...and the hordes of M$*ft users descended upon me in their anger, > and asked 'Why do you not get the viruses or the BlueScreensOfDeath > or insecure system troubles and slowness or pay through the nose > for an OS as *we* do?!!', and I answered...'I use Linux'. " > The Book of John, chapter 1, page 1, and end of book > > > ___ > 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
Re: [Vserver] iproute2 behavior problem
On Sunday 03 December 2006 09:25, Michael S. Zick wrote: honestly these have stumped me. i find nothing remotely resembling anything that would cause a delay.. i have a hard time reading all the greek in these things as many of these scripts make extensive use of regx.. i traced various scripts they call/use all the way through and could find nothing even remotely resembling a delay. guess ill have to try creating a script calling iproute2 directly for addr assignments and see if it still delays, and if so ill have to dig into the iproute2 code to see why. i really dont need these delays in my work as debugging this behavior is making me fall severely behind, but this boot problem is intolerable. i never noticed it before now because i didnt have to reboot the old machine in the past year, and updates have been done and just sit there for when it does get rebooted. since this is a new machine i'm working on now, it was quite noticable first time out. > 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 > -- Chuck "...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. " The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] iproute2 behavior problem
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
Re: [Vserver] iproute2 behavior problem
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. > 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 > -- Chuck "...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. " The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] iproute2 behavior problem
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
Re: [Vserver] iproute2 behavior problem
On Sunday 03 December 2006 00:28, Herbert Poetzl wrote: i just tried an experiment. i placed 5 ips on an adapter on the older dell x86 system and still the same behavior so it is not arch related. > 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 > -- Chuck "...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. " The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] iproute2 behavior problem
On Sunday 03 December 2006 00:28, Herbert Poetzl wrote: it also occurs any time i initialize them. if i take eth2 down and bring it back up same behavior. i tried switching adapters for experiment and it still is the same on a different chipset adapter. i first thought it could have been driver related to a specific chipset but no it behaves the same on each of these: 1 Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet 2 Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet 1 Intel Corporation 82557/8/9 [Ethernet Pro 100] > 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 > -- Chuck "...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. " The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] iproute2 behavior problem
On Sunday 03 December 2006 00:28, Herbert Poetzl wrote: this is during boot when initializing the ethx adapters. > 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 > -- Chuck "...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. " The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] iproute2 behavior problem
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] iproute2 behavior problem
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!! it is intolerable. does anyone have a fix for this or know what causes it? -- Chuck ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
