-* Prevent PROCESS services from being starts-on-console without also being runs-on-console.
-
-* shutdown command presently hangs if terminal output blocked (scroll lock
- via ^S). Should use a buffer as dinit does, and pipe output from subcommands
- via the buffer too.
-
-* Document utilities (particularly dinitctl) in the README
+For version 0.6.0:
+------------------
+* Refuse to start new services during shutdown.
+* On service failure (all services stop when no restart issued), allow user to interrupt/ctrl+alt+del when
+ they are prompted to press enter, to allow halt/rebooting instead of re-launching the boot service.
+* Basic resource limits setting.
+* per-service environment.
+For version 0.7.0:
+------------------
+? Not decided yet.
For version 1.0:
----------------
-* Man pages for all programs (done for dinit, not for dinitctl/shutdown/etc).
-* Better error handling, logging of errors (largely done, still some patches
- of code where it may be missing - check TODO's in code).
-* Write wtmp entry on startup (see simpleinit)
-* Allow running services as a different UID
-* Must be able to specify kill timeout (after which kill -9!)
* "triggered" service type: external process notifies Dinit when the service
- has started.
-* Ability to reload stopped services (reload service description)
-
+ has started. (maybe?)
+* on shutdown, after repeated intervals with no activity, display information
+ about services we are waiting on (or, do this when prompted via ^C or C-A-D).
+* Documentation must be complete (see section below).
+* Proper support for socket activation?
+* Be able to boot and shutdown Linux and FreeBSD.
For later:
----------
system initialisations that can't or shouldn't really be "undone" and so do
not need to be re-done).
* Internationalisation
-* More logging options. Can currently log to syslog only (well, with the
- syslog protocol, to /dev/log). Possibly should be able to log directly
- to a file, or input stream of another process.
* A service can prevent shutdown/reboot by failing to stop. Maybe make
multiple CTRL-ALT-DEL presses (or ^C since that's more portable) commence
immediate shutdown (or launch a simple control interface).
-* Interruptible scripted services - where it's ok to terminate the start
- script with a signal (and return the service to the STOPPED state). So a long-
- running filesystem check, for instance, need not hold up shutdown.
* When we take down a service or tty session, it would be ideal if we could kill
- the whole process tree, not just the leader process.
-* Investigate using cn_proc netlink connector (cn_proc.h) to receive process
- termination events even when running with PID != 1 (Linux only).
- Also, there is the possibility of having a small, simple PID-1 init which
- sends terminated process IDs over a pipe to Dinit. Finally, it may be possible
- to run dinit (and subprocesses) in a new PID namespace (again linux-only).
+ the whole process tree, not just the leader process (need cgroups or pid
+ namespace or other mechanism).
* Allow logging tasks to memory (growing or circular buffer) and later
switching to disk logging (allows for filesystem mounted readonly on boot).
But perhaps this really the responsibility of another daemon.
* Allow running services with different resource limits, chroot, cgroups,
namespaces (pid/fs/uid), etc
-* Make default control socket location build-time configurable
-* Allow specifying a timeout for killing services; if they don't die within
- the timeout (after a TERM) then hit them with a KILL.
-* A (perhaps limited) way(s) to modify a service description after it is loaded -
- eg add/remove dependencies, change properties.
-* Think about detecting runs-on-console dependency conflicts (i.e. if A runs-on-console and
- B depends on A and runs-on-consle then B can never start).
+* Support chaining service output to another process (logger) input; if the
+ service dies the file descriptor of its stdout isn't closed and is reassigned
+ when the service is restarted, so that minimal output is lost.
+ - even more, it would be nice if a single logger process could be responsible
+ for receiving output from multiple services. This would require some kind of
+ protocol for passing new output descriptors to the logger (for when a
+ service starts).
Even later / Maybe never:
+-------------------------
* Support recognising /etc/init.d services automatically (as script services, with
no dependency management - or upstart compatible dependency management)
Also BSD's rc.d style scripts (PROVIDE, REQUIRE).
Documentation:
+--------------
* Design philosophy/rationale document
* Coding style guidelines
projects / oweals / dinit.git / blobdiff