Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
`systemctl` should not consider active->failed as a successful operation #6478
systemd version the issue has been seen with
In case of bug report: Expected behaviour you didn't see
The documentation explicitly mentions services with
If saving the backlight fails when running
Even if ExecStop is just doing some cleanup, failures are still interesting.
It's possible the ExecStop failure could be a factor in the failure of a service restart, but only the later error would be shown, which would be misleading. I'm not certain what the correct behaviour is in this case, however. I want restart to show the ExecStop error... but if it then goes ahead with running ExecStart anyway, we need a message to say that. Otherwise, if ExecStart succeeds, we will keep quiet in traditional Unix fashion, but the user will see the previous error message and assume the service was not restarted. If we could redefine restart so it doesn't proceed after ExecStop fails, that would also solve the problem, but that doesn't quite sound like a good idea to me.
In case of bug report: Unexpected behaviour you saw
In case of bug report: Steps to reproduce the problem
Note: However it looks wrong that
I wondered how