Am 14.08.2014 um 19:51 schrieb Lennart Poettering:
> On Thu, 14.08.14 21:38, Andrei Borzenkov (arvidj...@gmail.com) wrote:
>
>>> Which is what we do. Except when you specify ExecStop= which basically
>>> tells systemd that you want to do it instead. So there you go!
>>
>> Those daemons I have see
On Thu, 14.08.14 21:38, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> > Which is what we do. Except when you specify ExecStop= which basically
> > tells systemd that you want to do it instead. So there you go!
>
> Those daemons I have seen are terminated after receiving signal/command
> to do i
В Thu, 14 Aug 2014 19:24:54 +0200
Lennart Poettering пишет:
> On Thu, 14.08.14 21:16, Andrei Borzenkov (arvidj...@gmail.com) wrote:
>
> >
> > В Thu, 14 Aug 2014 14:24:49 +0200
> > Lennart Poettering пишет:
> >
> > > On Sun, 27.07.14 20:04, Reindl Harald (h.rei...@thelounge.net) wrote:
> > >
On Thu, 14.08.14 21:16, Andrei Borzenkov (arvidj...@gmail.com) wrote:
>
> В Thu, 14 Aug 2014 14:24:49 +0200
> Lennart Poettering пишет:
>
> > On Sun, 27.07.14 20:04, Reindl Harald (h.rei...@thelounge.net) wrote:
> >
> > > but that still don't explain why "ExecStopPost=/sur/bin/true" or
> > > w
В Thu, 14 Aug 2014 14:24:49 +0200
Lennart Poettering пишет:
> On Sun, 27.07.14 20:04, Reindl Harald (h.rei...@thelounge.net) wrote:
>
> > 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
Am 14.08.2014 um 14:24 schrieb Lennart Poettering:
> On Sun, 27.07.14 20:04, Reindl Harald (h.rei...@thelounge.net) wrote:
>
>> but that still don't explain why "ExecStopPost=/usr/bin/true" or
>> whatever "ExecStopPost" solves that and if it is not supported
>> why "systemctl" don't return after
Am 14.08.2014 um 14:22 schrieb Lennart Poettering:
> On Sun, 27.07.14 19:53, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>>
>> 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
On Sun, 27.07.14 20:04, Reindl Harald (h.rei...@thelounge.net) wrote:
> 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
Well, this is a misunder
On Sun, 27.07.14 19:53, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
> 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 enoug
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
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
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 MAINP
and it happended again
how can it be that if i have running mysqld-instances as
Type=simple directly starting mysqld that it is not safe
after "systemctl stop" returns to rsync the datadirs
i had over a long time in any mysqld-unit
ExecStopPost=/usr/bin/sleep 1
pretty sure because that happened i
13 matches
Mail list logo
