Fred Lotter 9a8586f5ea systemd: remove the systemctl stop timeout handling ...

This PR is somewhat related to:
https://github.com/snapcore/snapd/pull/11340

In the process of improving the systemd stop code to better track
the progress of stopping units, we also removed the snapd concept
of a timeout period in order to exclusively rely on
'systemctl stop' to return an error after its internal stop
escalation process failed.

We therefore no longer can produce a 'Timeout' error.

This patch removes code in the code base that used to deal
with this 'Timeout' condition.

The idea behind this patch is that we trust 'systemctl stop'
to tell us if it failed to stop a unit within its configured
timeout, and if it fails, there is nothing more we can do but
to return an error.

Signed-off-by: Fred Lotter <fred.lotter@canonical.com>

2022-05-20 17:45:04 +02:00

..

export_test.go

usersession/agent: killWait was unused, simplify dropping mocking

2022-05-20 17:45:04 +02:00

response.go

usersession: use an error response if any service fails to start/stop

2019-08-16 12:53:18 +08:00

rest_api_test.go

systemd: remove the systemctl stop timeout handling

2022-05-20 17:45:04 +02:00

rest_api.go

usersession/agent: killWait was unused, simplify dropping mocking

2022-05-20 17:45:04 +02:00

session_agent_test.go

Handle observing of notifications.

2021-11-04 11:56:31 +01:00

session_agent.go

Tweak the comment

2021-11-05 08:31:38 +01:00