On Fr, 16.03.18 09:13, prashantkumar dhotre (prashantkumardho...@gmail.com)
wrote:
> Hi
> I see that default reboot/systemctl reboot command issues SIGTERM to my
> apps and hence it is doing graceful stop of apps and this may take some
> time and hence shutdown time may be little longer.
>
> I a
On Fr, 16.03.18 09:27, prashantkumar dhotre (prashantkumardho...@gmail.com)
wrote:
> Thanks but I want to sigkill my services only during system shutdown and
> not on normal service stop 'systemctl myservice stop'.
> so I can not use ' KillSignal' setting. Is there any other way ?
Nope there is
Am 16.03.2018 um 11:36 schrieb prashantkumar dhotre:
Thanks
I understand that
'systemctl isolate other.target' will stop all present services and
start services of other.target
My thinking is :
I can put all my apps in my.target
and my.target can start after multi-user.target.
that are all
Thanks
I understand that
'systemctl isolate other.target' will stop all present services and start
services of other.target
My thinking is :
I can put all my apps in my.target
and my.target can start after multi-user.target.
When shutting down , somewhere first i will do 'systemctl iso
multi-user
16.03.2018 10:19, aleivag пишет:
>>
>>
>> Won't work. Status changes only when job for a unit completes and jobs
>> are executed in order of dependencies. Actually, jobs are *queued* in
>> order of dependencies so nothing would indicate that you are going to
>> shutdown until it is too late (i.e. a
>
>
> Won't work. Status changes only when job for a unit completes and jobs
> are executed in order of dependencies. Actually, jobs are *queued* in
> order of dependencies so nothing would indicate that you are going to
> shutdown until it is too late (i.e. all normal services are stopped).
>
>
ye
16.03.2018 08:09, aleivag пишет:
> One other thing that may work, is that you could implement a ExecStop
> action in your service unit, that checks if the system is been shutting
> down (by checking status of {shutdown,reboot,halt}.target
Won't work. Status changes only when job for a unit complet
One other thing that may work, is that you could implement a ExecStop
action in your service unit, that checks if the system is been shutting
down (by checking status of {shutdown,reboot,halt}.target [or maybe also
the runlevel may work?]), and kill the unit if there is one of those
operations.
A
Hmm. This is probably not ideal, but you could hook a 'Type=oneshot'
service into shutdown.target which runs 'systemctl kill {your
service}.service'.
I'm not sure if there's a simpler way to do this using targets.
On Thu, Mar 15, 2018 at 8:57 PM prashantkumar dhotre <
prashantkumardho...@gmail.co
Thanks but I want to sigkill my services only during system shutdown and
not on normal service stop 'systemctl myservice stop'.
so I can not use ' KillSignal' setting. Is there any other way ?
On Fri, Mar 16, 2018 at 9:23 AM, Zeal Jagannatha
wrote:
> I think it would be better for the services y
I think it would be better for the services you define to specifically
define their own `KillSignal` so you can control how they shutdown.
https://www.freedesktop.org/software/systemd/man/systemd.kill.html#KillSignal=
It's may not be safe for all the services on the machine to be shut down
with SI
Hi
I see that default reboot/systemctl reboot command issues SIGTERM to my
apps and hence it is doing graceful stop of apps and this may take some
time and hence shutdown time may be little longer.
I am looking for safe and fastest shutdown/reboot method.
a) It is OK if my apps are stopped ungra
12 matches
Mail list logo
