when startup delays become bugs

Farkas Levente lfarkas at lfarkas.org
Wed May 15 12:58:09 UTC 2013

On 05/15/2013 02:48 PM, Lennart Poettering wrote:
> On Wed, 15.05.13 07:45, Dan Williams (dcbw at redhat.com) wrote:
>>>> 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:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=787314#c37
>>> 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.
> After=syslog.target is unnecessary these days and should be removed from
> all unit files, to keep things simple.
> We nowadays require syslog implementations to be socket activatable, and
> that socket is around before normal services start, and that's
> guaranteed, hence nobody has to depend on syslog explicitly anymore. All
> services will have logging available anyway, out-of-the-box, as default,
> with no manual configuration necessary, and without any referring to
> syslog.target.

is it documented?

in many of your mails in this thread you wrote "nowadays", "anymore",
"default", "modern system", "modern hardware", etc...
does it documented anywhere? what are the assumptions and how nowadays
fedora should have to work?

  Levente                               "Si vis pacem para bellum!"

More information about the devel mailing list