Hi Lennart, THe suggestion you have offered for design stop service was successfully integrated but the issue is still same as the User session in User.slice still got kill.
I am pasting my service here grep -v ^# /etc/systemd/system/stop.service [Unit] Description=Service to auto stop the EBS application After=-.slice system.slice user.slice [Service] ExecStart= ExecStop=/startdb/stop/stop.sh RemainAfterExit=true [Install] WantedBy=user.slice Now service runs but still issue is that I want my service to stop the processes not systemd Issue might be similar like this https://lists.freedesktop.org/archives/systemd-devel/2016-November/037916.html Regards, Kamal On Thu, Jan 2, 2020 at 6:34 PM Lennart Poettering <[email protected]> wrote: > On Di, 31.12.19 11:04, Kamal Rathi ([email protected]) wrote: > > > Hi Git-Hub Mailing List, > > > > I am designing a stop service which has to be run before the kill of > user's > > scope / session . > > How could this work? Users can log out or be terminated any time, > i.e. their scope/sessions can go away during runtime all the time, and > they won't tell us beforehand about it beforehand, hence how could we > run something beforehand? > > Lennart > > -- > Lennart Poettering, Berlin >
_______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
