when startup delays become bugs
dcbw at redhat.com
Wed May 15 12:45:15 UTC 2013
On Wed, 2013-05-15 at 12:52 +0200, Lennart Poettering wrote:
> On Tue, 14.05.13 17:30, Dan Williams (dcbw at redhat.com) 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.
> Dan, could you please implement these recommendations for F19:
> This really shouldn't be pulled in unconditionally...
The changes you suggest there seem fine; one question about
After=syslog.target being removed though: intentional? I pretty much
just take your guidance on the .service files.
More information about the devel