informations about boot sequence (Re: F15 - mysql start problem)

[Tom Lane]

Lennart Poettering <mzerqung at 0pointer.de> writes:
> So, instead of making mysql/postgres start up slower for everybody, i'd
> rather see this solution:

> a) people who manually change the IP address fo mysql to bind on
> specific ip addresses, manually also enable
> NetworkManager-wait-online.service.

> or:

> b) the servers are fixed to listen to netlink.

> or:

> c) They get fixed to use IP_FREEBIND.

> All three of the solutions are nicer than adding unnecessary
> dependencies for them.

I think you've failed to grasp the point.  What you are proposing is to
hack the servers with patches that are rather unlikely to be accepted by
either upstream, in order to solve *one* of the possible configuration
issues that might cause them to not start correctly before the basic
expected network support services are available.  In particular, so far
as I can tell from the discussion at bug #703215, systemd is entirely
incapable of supporting services that need to do DNS lookups at start.
It's not acceptable to tell people that they mustn't use configurations
that require that; they'll just go looking for another solution that
does do what they want.

I grow weary of systemd apologists saying that services should be hacked
to work around systemd's limitations.  systemd exists to serve the
daemons, not vice versa.  If you can't fix these problems, people are
going to decide that systemd is a failed experiment.

			regards, tom lane