Am 27.07.2014 19:53, schrieb Zbigniew Jędrzejewski-Szmek: > On Sat, Jul 26, 2014 at 02:46:05PM +0200, Reindl Harald wrote: >> after that happend a few minutes ago systemd on F19: >> https://bugzilla.redhat.com/show_bug.cgi?id=1123557 >> >> since the "sleep 1" was enough over months and now "sleep 6" >> between "systemctl stop" and rsync is also not relieable my >> only conclusion is that systemd don't care about the still >> running MAINPID of "type=simple" and in case of a existing >> "ExecStopPost" the logic is correct > Hi, > > PIDFile with Type=simple is not supported
accepted > Adding support would be tricky, because with Type=simple there's > no obvious mechanism to notify systemd *when* to read the file. > With Type=forking, when the first process exits, systemd knows > it can read the file. It could be done with inotify maybe all understood but that still don't explain why "ExecStopPost=/sur/bin/true" or whatever "ExecStopPost" solves that and if it is not supported why "systemctl" don't return after the one and only process exited the "hmm no idea what happened, try ExecStopPost=/usr/bin/sleep 1" any so try at least give a little time masked it and in fact was not the additional second, it's the existence maybe somebody should explain the Fedora/RHEL maintainers that that continued use of "mysld_safe" is nonsense since systemd itself can do that monitoring and restarting and systemd should warn about that unsupported combination to force them fix it - ExecStart=/usr/bin/mysqld_safe + ExecStart=/usr/libexec/mysqld --defaults-file=/etc/my.cnf
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
