Am 25.06.2012 15:57, schrieb Gary Kotton:
My understanding is that if there is a entry in the Service section
Restart=always, then we can rely on systemd to restart the service if
it dies.
true and that is why i am change each systemd-unit from early
F15 days on
Can someone please explain
On 06/26/2012 11:01 AM, Lennart Poettering wrote:
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
On Wed, 27.06.12 13:34, Honza Horak (hho...@redhat.com) wrote:
On 06/26/2012 11:01 AM, Lennart Poettering wrote:
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
On Mon, 25.06.12 15:40, Tom Lane (t...@redhat.com) 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
Hi,
I recently encountered a problem with the Openstack Quantum service. The
service was installed by doing the following steps:
- sudo yum install openstack-quantum
- sudo systemctl enable quantum-server.service
- sudo systemctl start quantum-server.service
Due to a bug the service
On Mon, 25.06.12 16:57, Gary Kotton (gkot...@redhat.com) wrote:
Hi,
I recently encountered a problem with the Openstack Quantum service. The
service was installed by doing the following steps:
- sudo yum install openstack-quantum
- sudo systemctl enable quantum-server.service
On Mon, 25.06.12 16:13, Lennart Poettering (mzerq...@0pointer.de) wrote:
I think it would be great if somebody would file an FPC ticket about
this, so that the policy gets amended. But for that we'd first have to
make our mind up what the best option to recommend is.
Hmm, ok, I decided to be
Lennart Poettering mzerq...@0pointer.de writes:
On Mon, 25.06.12 16:57, Gary Kotton (gkot...@redhat.com) wrote:
My understanding is that if there is a entry in the Service section
Restart=always, then we can rely on systemd to restart the service if
it dies.
Can someone please explain or
On Mon, Jun 25, 2012 at 10:30:00 -0400,
Tom Lane t...@redhat.com wrote:
See also bug #832029 before being in too much of a hurry to decide that
this Must Be A Good Thing. At minimum, it currently seems that we might
need per-service tuning of the restart timing parameters before being
sure
Tom Lane (t...@redhat.com) said:
Well, simply because we have no policy about it.
See also bug #832029 before being in too much of a hurry to decide that
this Must Be A Good Thing. At minimum, it currently seems that we might
need per-service tuning of the restart timing parameters before
On Mon, 25 Jun 2012, Tom Lane wrote:
Subject: Re: service restart question
(1) systemd is not able to distinguish a crash that should be restarted
(2) Right now it appears that there is a bug in systemd that causes
it to ignore its respawn limits
(3) Even if StartLimitInterval
Paul Wouters (pwout...@redhat.com) said:
On Mon, 25 Jun 2012, Tom Lane wrote:
Subject: Re: service restart question
(1) systemd is not able to distinguish a crash that should be restarted
(2) Right now it appears that there is a bug in systemd that causes
it to ignore its respawn
12 matches
Mail list logo
