On Mon, 25.06.12 15:40, Tom Lane (tgl@xxxxxxxxxx) wrote: > (1) systemd is not able to distinguish a crash that should be restarted > from, say, failure due to misconfiguration in /etc/my.cnf. (It's not > clear whether restart settings other than "always" would help here, > but in general it seems obvious that there are likely to be service- > specific reasons for restarting after some failures and not others.) Hmm, it can actually do that. For example if you set Restart=on-abort we'll restart mysql only if it crashes abnormally, via a signal -- but it wouldn't be if mysql exits with exit(x) regardless what that x is. Also, if you use Restart=always and a service terminates during its initialization phase then we don't try restarts either (well, at least in theory, there might be a bug in this, too). We'd only restart it if it terminates during the normal runtime. Anyway, I will spend some time today to make sure this all works properly, as intended. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
