If we introduced the desired behavior by including an ExecStop script to the systemd unit configuration file, we would introduce a regression since stopping the service for erroneous configuration files would not be allowed (this was not the behavior for sysV).
Ideally, this should be supported by systemd somehow. There is this (old) discussion upstream, which is relevant here: https:/ /github. com/systemd/ systemd/ issues/ 2175
If we introduced the desired behavior by including an ExecStop script to the systemd unit configuration file, we would introduce a regression since stopping the service for erroneous configuration files would not be allowed (this was not the behavior for sysV).