On shutdown we need to stop a service before systemd begins to kill all processes it does not know. The service is a process supervisor similar to init, which controls all our applications. Our applications must be terminated by this supervisor, otherwise data loss and inconsistencies will occur.
The problem is: aside from background processes started by the supervisor, we have applications started in a user session, but which are also controlled by the supervisor. This is something systemd cannot know, and thus it kills these applications in parallel to shutting down our service. So we require systemd to wait for our service to terminate before it begins to kill other processes. From an arch-linux thread in 2017 I concluded this is not possible due to the design of systemd. But I cannot believe we are the only one requiring this. So my question is: is there nowadays some mechanism available to accomplish this? -- Hans-Dieter Doll Dr. Brunthaler Industrielle Informationstechnik GmbH Wilhelm-Kabus-Str 42/44, D-10829 Berlin Fon: +49.30.215081-0, Fax: +49.30.215081-88 mailto:[email protected] http://www.brunthaler.de Geschäftsführer: Prof. Dr.-Ing. Stefan Brunthaler Sitz der Gesellschaft: Berlin Handelsregister: HRB 27 337 Amtsgericht Charlottenburg -- Wir sind Mitglied des inilog Netzwerks - www.inilog.eu
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
