Am 21.06.2011 04:29, schrieb Garry T. Williams:
On Monday, June 20, 2011 19:48:53 Reindl Harald wrote:
>
> Am 21.06.2011 01:30, schrieb Lennart Poettering:
>> On Tue, 21.06.11 01:07, Reindl Harald (h.reindl(a)thelounge.net) wrote:
>> On F15, an admin who types "systemctl stop mysqld.service" will get
just
>> that, since socket activation is not used.
>
> I HAVE TO USE IT SINCE YOU ARE STARTING SERVICES PARALLEL
I think you misunderstand. The documentation is clear:
http://0pointer.de/public/systemd-man/daemon.html
-------------------------------------------------
Socket-Based Activation
...
In a socket-based activation scheme the creation and binding of
the listening socket as primary communication channel of daemons
to local (and sometimes remote) clients is moved out of the daemon
code and into the init system.
In other words, the daemon *must* be changed to support socket
activation.
Unless you changed the code in mysqld, this configuration is doomed to
fail.
i miss nothing because i want only that if mysql is started BEFORE
dbmail showing in /var/log/boot.log dbmail is not throwing errors
that connection to mysqld is not possible
if you follow these bug-reports (primary the first) you will
see that the idea with the socket was not mine and that i spent
many hours in the problem and days later someone will tell me
"this works even with sysv/lsb-scripts"
https://bugzilla.redhat.com/show_bug.cgi?id=714486
https://bugzilla.redhat.com/show_bug.cgi?id=714426
F15 misses anything to use mysql-driven services, not more, not less