On Thu, 24 Nov 2016, Kai Krakow wrote:
Am Wed, 23 Nov 2016 09:14:34 +0100
schrieb Cédric BRINER :
Hi,
For the context, we are trying to stop a daemon launched by a user...
Hi,
sapRunning service contains a "After=user.slice". But at the
shutdown, a process
Am Wed, 23 Nov 2016 09:14:34 +0100
schrieb Cédric BRINER :
> Hi,
>
> For the context, we are trying to stop a daemon launched by a user...
>
> >> Hi,
> >>
> >> sapRunning service contains a "After=user.slice". But at the
> >> shutdown, a process (write-sysv-test.pl)
Hi,
>> But this has not the expected impact. We were wishing with the
>> "After=user.slice", that the stop sapRunning will occur before any user
>> commands are stopped.
>>
>> Does using "After=user.slice" propagate also on all the
>> *children*. That way we could ensure that our stop services'
On Wed, 23.11.16 09:14, Cédric BRINER (cedric.bri...@unige.ch) wrote:
> Hi,
>
> For the context, we are trying to stop a daemon launched by a user...
>
> >> Hi,
> >>
> >> sapRunning service contains a "After=user.slice". But at the shutdown, a
> >> process (write-sysv-test.pl) running in
Hi,
For the context, we are trying to stop a daemon launched by a user...
>> Hi,
>>
>> sapRunning service contains a "After=user.slice". But at the shutdown, a
>> process (write-sysv-test.pl) running in user.slice is killed before the
>> end of the sapRunning's stop.
>
> Slices are a concept
Hi,
sapRunning service contains a "After=user.slice". But at the shutdown, a
process (write-sysv-test.pl) running in user.slice is killed before the
end of the sapRunning's stop.
# cat sapRunning.service
[Unit]
Description=SAP Service to ensure stopsap during shutdown
After=local-fs.target