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

[Michał Piotrowski]

W dniu 9 maja 2011 17:34 użytkownik Michał Piotrowski
<mkkp4x4 at gmail.com> napisał:
> 2011/5/9 Tom Lane <tgl at redhat.com>:
>> =?ISO-8859-2?Q?Micha=B3_Piotrowski?= <mkkp4x4 at gmail.com> writes:
>>> Ok, I know what is happening. I looked at the init script and I
>>> realized that it doesn't have any LSB header info about boot process
>>> order.
>>
>> No, it's assuming that the chkconfig numbering takes care of that.
>
> Do you mean these numbers before script name in /etc/rc.d/rc*.d/ ?
>
>> Are you saying that systemd no longer honors the chkconfig ordering?
>
> It seems to me that mysql starts before NetworkManager here
> http://eventhorizon.pl/images/bootchart17.png
>
>> That doesn't leave me with a warm feeling about how much testing the
>> systemd stuff has gotten, because there is all kinds of stuff that's
>> liable to fall over without that.
>>
>>> I also looked at other services and here are some of them that
>>> needs fixing:
>>> - memcached - (I created systemd service for it) - I can provide a
>>> patch for classic init script
>>> - smb - as above
>>> - nmb - as above
>>> - mysql - I can provide a patch for classic init scrip
>>> - postgresql - as above
>>
>> Yes, mysql and postgresql are both certainly broken by this.  Please
>> send the info, I'll take care of those two.
>
> I'll create bug reports and send proposed patches later.
>

Patch for MySQL
https://bugzilla.redhat.com/show_bug.cgi?id=703214

for PostgreSQL
https://bugzilla.redhat.com/show_bug.cgi?id=703215

Bootchart shows me that now MySQL starts in the right order.

What about the rest of the mentioned init scripts? For the samba there
is a native systemd service in bugzilla - the same for memcached.

-- 
Best regards,
Michal

http://eventhorizon.pl/