On 26.09.05 10:22:44, Martin Pitt wrote:
> Hi Andreas!
>
> Andreas Pakulat [2005-09-26 9:23 +0200]:
> > 60 Seconds doesn't work either, but 120 do:
> >
> > for (my $attempt = 0; $attempt < 240; $attempt++) {
>
> 120 seconds? Good grief, it takes 3 seconds even on my relatively slow
> iBook G4 (800 MHz) laptop (slow hd as well). I guess kdm *really*
> drains your I/O resources if it lasts that long.Don't know if you have a KDE installation at hand, but just checking the output of ldd `which kdm` gives you a very long library list to load, together with a thousand files for configs/icons/localization/whatever kdm is kind of a monster... > I don't want to default to such an exaggerated timeout just for a few > users, so I rather make this configurable with a sane default. The value 40 work here perfectly if I don't start kdm, not sure about 10 though. > It seems that this is purely cosmetical for you anyway. Yeah, and it wouln't bother me at all, I just thought about somebody who takes this failed and tries to find an error that just doesn't exist... (maybe with an equally set up kdm-early-start) > > Now PG doesn't give an error anymore. I'll try with values of 120 and 40 > > there while removing kdm from the runlevel.. > > That would be nice to cross-check. As I said above, 40 work great when I leave out kdm. Andreas -- You don't become a failure until you're satisfied with being one.
pgpDFQ1es9iDA.pgp
Description: PGP signature
