[systemd-devel] start / stop daemon

Lennart Poettering lennart at poettering.net
Tue Aug 19 13:51:24 PDT 2014

On Tue, 19.08.14 14:44, Bonno Bloksma (b.bloksma at tio.nl) wrote:

> I wonder if the people developing systemd are paying attention to a
> development in de Windows environment where the latest thing is that
> de service can report back that it is indeed still trying to stop and
> not just hung or not reporting back. Windows will now kill a service
> after a certain time when shutting down, in some cases it is killing a
> database that took A LONG TIME to shut down and cause the database to
> become inconsistent. The new development is to make sure that does not
> happen.  If systemd is trying to become smart about stopping services
> it might be a good idea to have this built in. Also not just have the
> service report back "I am still busy" but also with a progress
> indicator which NEEDS to increase at each report so systemd can detect
> whether the service is indeed progressing towards a stopped state or
> hung in the getting there.  >From the past I have seen things go wrong
> in communication when the only thing reported back is "I am busy"
> while there was no progress being made toward the finish.

I am not sure I understand what the big benefit of having an overall stop
timeout applied (as we already have) is?

What's on the TODO list is that a service can actually let systemd know
when it shuts down. Currently systemd knows that only if it is the one
requesting the shutdown.


Lennart Poettering, Red Hat

More information about the systemd-devel mailing list