On 06/27/2012 07:01 PM, Lennart Poettering wrote:
Hmm, well, not really. on-abort means that systemd would only restart
the service on actual crashes, i.e. where the main process exits with a
signal like SIGSEGV, SIGBUS or SIGABRT. This is different from
on-failure which is the behaviour you
On Wed, 27.06.12 20:21, Tom Lane (t...@redhat.com) wrote:
Well, it may be a hack rather than the nicest possible solution, but
here's the thing: every production installation of mysql in the world
runs underneath mysqld_safe, and has done for the last ten years or
more. The server's behavior
On Thu, 28.06.12 09:41, Honza Horak (hho...@redhat.com) wrote:
On 06/27/2012 07:01 PM, Lennart Poettering wrote:
Hmm, well, not really. on-abort means that systemd would only restart
the service on actual crashes, i.e. where the main process exits with a
signal like SIGSEGV, SIGBUS or
On 06/27/2012 02:50 PM, Honza Horak wrote:
Another issue is the PID file guessing. It usually works fine, but if we
want to be sure what pid is monitored, we should use PIDFile= option.
However, when we use this we don't know when the pidfile is created,
while waiting some sane time is not a
On Wed, 27.06.12 14:50, Honza Horak (hho...@redhat.com) wrote:
Hi guys,
Heya,
we've met some problems around mysqld and systemd's auto-restart
feature recently in Fedora, which has been fortunately fixed by
Michal few days ago [1]. However, there are still some doubts, which
convince us to
On Wed, Jun 27, 2012 at 1:06 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Wed, 27.06.12 16:49, Honza Horak (hho...@redhat.com) wrote:
On 06/27/2012 02:50 PM, Honza Horak wrote:
Another issue is the PID file guessing. It usually works fine, but if we
want to be sure what pid is
Am 28.06.2012 02:21, schrieb Tom Lane:
Lennart Poettering lenn...@poettering.net writes:
On Wed, 27.06.12 14:50, Honza Horak (hho...@redhat.com) wrote:
One of the issue is (in)ability to imitate the original behavior of
mysqld_safe, which restarts the main process only if it crashes and
the
On Thu, 2012-06-28 at 04:02 +0200, Reindl Harald wrote:
Am 28.06.2012 02:21, schrieb Tom Lane:
Lennart Poettering lenn...@poettering.net writes:
On Wed, 27.06.12 14:50, Honza Horak (hho...@redhat.com) wrote:
One of the issue is (in)ability to imitate the original behavior of
mysqld_safe,