Re: [systemd-devel] Failed at step RUNTIME_DIRECTORY spawning /usr/bin/true: File exists

[Reindl Harald]

Am 06.08.2015 um 14:15 schrieb Lennart Poettering:

On Thu, 06.08.15 12:38, Reindl Harald (h.rei...@thelounge.net) wrote:

Am 06.08.2015 um 12:16 schrieb Lennart Poettering:

On Thu, 06.08.15 10:57, Reindl Harald (h.rei...@thelounge.net) wrote:

So, you'll get this EEXIST error only if there's already something at
the place of the runtime dir that is either:

NOBODY but systemd creates that directory
it don't exist at all before the service is started

the problem is that SOMETIMES at stop is
seems not to be removed and so the next start
fails

Whether it is removed or not should not matter really, the code is
completely fine already exists as long as the uid/gid/mode match (as
mentioned before).

no, the code is *not* fine

"Failed at step RUNTIME_DIRECTORY spawning" for the *ExecStartPost* in
nonsense since it is already created *before* ExecStart

See:

https://github.com/systemd/systemd/pull/896

thanks - hopefully there will be soon a fedora update



MariaDB seems to be happy with that........

[Service]
Type=simple
User=mysql
Group=mysql

ExecStartPost=/usr/libexec/mysqld-wait-ready $MAINPID

in the meantime i worked around that issue by remove the RuntimeDirectory stuff from all mysql instances and just point the pid-file which systemd don't need anyways to /dev/null ExecStart=/usr/libexec/mysqld --defaults-file=/etc/my.cnf --pid-file=/dev/null

signature.asc
Description: OpenPGP digital signature

_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel