On Thu, 14 Jun 2012 14:44:57 -0400, Gilbert Sullivan wrote: > On 06/14/2012 01:34 PM, Camaleón wrote:
>> To be sincere, I don't know what's originating the problem. If you say >> the network settings are properly configured, why Exim4 is that lazy? >> :-? >> >> Searching for "exim boot speed up" in Google I found this: >> >> *** >> 1.3.7. Why does exim take such a long time to start? >> http://wiki.debian.org/PkgExim4UserFAQ#Why_does_exim_take_such_a_long_time_to_start.3F >> *** >> >> Check if any of the suggested tips helps to mitigate the pain. >> >> > Hi, Camaleón. > > I'm coming to the conclusion that, when Wicd is set to use a profile > with a fixed IP address, the system is actually only connecting to the > network as it actually comes up to the desktop (after login). That would > be why exim4 is timing out on the fixed IP address profiles and working > just fine on the profiles that are set to use DHCP. To me sounds a bit unrealistic the fact a static network configuration can take longer than a dynamic one... Does not compute :-) > The use of dc_minimaldns='true' didn't work to improve the situation, > but it did cause the boot process to squawk. (It said that > dc_minimaldns='true' will not work.) I've restored the exim4 > configuration and /etc/dhcp/dhclient.conf to their default settings for > now. The wiki article included more tips you can try from the Exim's side. Anyway, I'd also run the following tests: 1/ Just for testing purposes, you can momentary disable wicd and test with a static IP configuration defined at "/etc/network/interfaces". If this boost the booting process then we can center exclusively in WICD (I still have my doubts about what is causing this). (if 1/ makes no difference, stop here as we will have to find another culprit other than WICD, otherwise proceed with 2/) 2/ Ensure there's only one network daemon running (i.e., no n-m, no dhcpd, no networking services) to avoid any possible collision. 3/ Test with a fresh-new created user (configure WICD for him and boot), to discard something wrong with your current user configuration files for WICD. > I think that the problem I'm seeing is a temporary (I hope) glitch > between netscript and Wicd, and that it'll probably be resolved at some > point by upgrades. You look very optimistic :-P > That may take a while, though, because Wicd doesn't seem to be under > terribly active development. Maybe I'll try to get in touch with the > Debian maintainers for the two packages. Something tells me that the > packages aren't working together the way they expect them to, and that > it may be counterproductive to start changing default configurations > that have been working just fine for years. As you are running wheezy (and considering the freeze is going to be in about a few weeks) consider in opening a bug report. > In the meantime, until I get a chance to really get into it, I can just > continue to use <Ctrl>+<C> at the "configuring interface" prompt. The > system boots up as quickly as normal, and everything appears to be > working. If Exim4 is started afterwards, then there should be no other gotchas. > I'll let you know whether or not I learn anything. Okay :-) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jrfh6l$bf6$3...@dough.gmane.org
