when startup delays become bugs

Daniel J Walsh dwalsh at redhat.com
Thu May 16 13:10:18 UTC 2013

Hash: SHA1

On 05/14/2013 06:30 PM, Dan Williams wrote:
> On Tue, 2013-05-14 at 15:51 -0600, Chris Murphy wrote:
>> This is not intended to be snarky, but I admit it could sound like it is.
>> When are long startup times for services considered to be bugs in their
>> own right?
>> [root at f19q ~]# systemd-analyze blame 1min 444ms sm-client.service 1min
>> 310ms sendmail.service 18.602s firewalld.service 13.882s
>> avahi-daemon.service 12.944s NetworkManager-wait-online.service
> Is anything waiting on NetworkManager-wait-online in your install?  That 
> target is really intended for servers where you want to block Apache or 
> Sendmail or Database from starting until you're sure your networking is 
> fully configured.  If you don't have any services that require a network to
> be up, then you can mask NetworkManager-wait-online and things will be more
> parallel.
>> 12.715s restorecond.service
I have no idea why restorecond would take this much time, and it really should
not be enabled for most machines, with file name transitions.

Not sure why it is enabled.  Could someone check on a fresh install if it is

Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/


More information about the devel mailing list