On Thu, Sep 12, 2013 at 06:51:49PM +0200, Lennart Poettering wrote:
> On Fri, 19.07.13 09:17, Lukáš Nykrýn (lnyk...@redhat.com) wrote:
>
> > Hi,
> > when service has StopWhenUnneeded=yes and it is requested by forking
> > service, which fails during initialization, the first unit is not
> > stoppe
On Fri, 19.07.13 09:17, Lukáš Nykrýn (lnyk...@redhat.com) wrote:
> Hi,
> when service has StopWhenUnneeded=yes and it is requested by forking
> service, which fails during initialization, the first unit is not
> stopped.
I have added this to the TODO list for now, so that we don't
forget. I'll lo
Dne 18.7.2013 20:02, Lennart Poettering napsal(a):
On Thu, 18.07.13 17:04, Michal Sekletar (msekl...@redhat.com) wrote:
When dependency unit is configured with StopWhenUnneeded=yes and
activation of main unit fails, e.g. start timeout occurs, then
dependencies are never stopped. This happens b
On Thu, 18.07.13 17:04, Michal Sekletar (msekl...@redhat.com) wrote:
> When dependency unit is configured with StopWhenUnneeded=yes and
> activation of main unit fails, e.g. start timeout occurs, then
> dependencies are never stopped. This happens because start job for
> the main unit is still ar
When dependency unit is configured with StopWhenUnneeded=yes and
activation of main unit fails, e.g. start timeout occurs, then
dependencies are never stopped. This happens because start job for
the main unit is still around.
---
src/core/unit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(
