From c6d82dd775c633f8c60e54c9376d37b5f28ea3b0 Mon Sep 17 00:00:00 2001 From: Davin McCall Date: Wed, 1 Jan 2020 13:35:48 +1000 Subject: [PATCH] Update TODO --- TODO | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/TODO b/TODO index 4c8a40d..a90c4a7 100644 --- a/TODO +++ b/TODO @@ -1,18 +1,19 @@ -For version 0.8.0: +For version 0.9.0: ------------------ -* provide a way to check configuration for errors (dinitcheck command) [DONE] -* Easy way to reload service description (including if service is running, where possible). [DONE] +* "chain-to" can result in an unbreakable loop if the chain is circular. Chained services should not be + started during shutdown to prevent this (also avoids a race condition where the chained service is left + running when everything else has shutdown). +* Check that desired_state is getting set correctly. (Currently we don't decide whether a service + will restart until it stops...) +* Add dinit command line option to run as pid 1 but not as system manager (i.e., in a container). + Currently dinit can be used as pid 1 in a container but it may try to shut down the system when + it terminates. (This results in a harmless warning, but is not ideal). -For version 0.9.+: +For version 0.10.+: ------------------ * for non-system init, fail if the control socket exists, with option to override this and re- create the socket instead (as system init does). -* Check that desired_state is getting set correctly. (Currently we don't decide whether a service - will restart until it stops...) * report process launch failure reason (stage & errno) via dinitctl. -* "chain-to" can result in an unbreakable loop if the chain is circular. Chained services should not be - started during shutdown to prevent this (also avoids a race condition where the chained service is left - running when everything else has shutdown). * Show "activated" state in "dinitctl list" output * Service description sanity checks: - Service type not specified -- 2.25.1