16.06.2020 07:36, Kamal Rathi пишет:
> The fact that you need RemainAfterExit at all hints that processes that
> belong to your service are not running as part of service control group.
> Knowing how Oracle has traditionally been managed, I suspect that you
> perform "su - oracle_owner" or similar
Hi,
I would like to assign a static IP address to a server in a way that survives
hardware replacement. Basically I want the configuration to say: “Find the only
physical interface present and assign this static IP address to it. In the
unexpected case of finding multiple interfaces, assign
Am 15.06.20 um 10:51 schrieb Kamal Rathi:
> Thanks Reindl for the response, but from the man page of systemd.service
> even oneshot is a kind of simple service as default is
> RemainAfterExit=no for simple.
simple: long running processes
oneshot: expected to completly exit
this are completly
>>.what about just remove "RemainAfterExit" and look again?
I have tried the above option by removing that option and also tried to
change it to oneshot and RemainAfterexit=yes and then tried it but the
issue still remains.
can you answer the question why you did put that option at all into the
can you plesse only respond to the list to not break reply-to
Am 15.06.20 um 11:49 schrieb Kamal Rathi:
> can you answer the question why you did put that option at all into the
> unit file and why do you add random options to your units like
> "After=syslog.target systemd-user-sessions.service
Hi Team,
I have two services which are dependent on each other and are working fine
at boot up but at shutdown / reboot , the processes get killed as shutdown
got initated.
Services are running fine in particular order but processes got killed .I
have enabled lingering on both users and changed
Am 15.06.20 um 10:01 schrieb Kamal Rathi:
> Hi Team,
>
> I have two services which are dependent on each other and are working
> fine at boot up but at shutdown / reboot , the processes get killed as
> shutdown got initated.
>
> Services are running fine in particular order but processes got
Thanks Reindl for the response, but from the man page of systemd.service
even oneshot is a kind of simple service as default is RemainAfterExit=no
for simple.
But if we talk about the original problem that processes are killed even if
ordering of services is there, .
from what it seems that
>> can you plesse only respond to the list to not break reply-to
I will use reply to all
>> useless unless you set "DefaultDependencies=no" which you shouldn't do
for normal services
>> if i remove all the service and only put After=grid.service, so it will
work similar way that how it is
15.06.2020 11:01, Kamal Rathi пишет:
> Hi Team,
>
> I have two services which are dependent on each other and are working fine
> at boot up but at shutdown / reboot , the processes get killed as shutdown
> got initated.
>
> Services are running fine in particular order but processes got killed
10 matches
Mail list logo
