-* License
-* Complete control socket handling and protocol
- - support for pinned-start and pinned-stop
- - support for listing all services
-* Implement a control utility to start/stop services after dinit has started
- - very basic version exists, needs thorough cleanup
+* 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 1.0:
----------------
-* Perhaps need a way to prevent script services from re-starting.
- (eg there's no need to mount filesystems twice; there might be various other
- system initialisations that can't or shouldn't really be "undone" and so do
- not need to be re-done).
-* Add command line arg to start in "PID 1" mode (even if PID != 1).
- Basically, allow running as a system service monitor, without
- requiring that dinit runs as PID 1.
-* if PID != 1, choose a more sensible service definition directory
- (something like $HOME/dinit.d)
-* Documentation including sample service definitions
-* Better error handling, logging of errors
+* 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)
+
For later:
+----------
+* On linux when running with PID != 1, write PID to /proc/sys/kernel/cad_pid so
+ that we still receive SIGINT from ctrl+alt+del (must be done after /proc is
+ mounted, possibly could be left to a service script)
+* Perhaps need a way to prevent script services from re-starting.
+ (eg there's no need to mount filesystems twice; there might be various other
+ 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.
+ 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).
* Allow logging tasks to memory (growing or circular buffer) and later
- switching to disk logging (allows for filesystem mounted readonly on boot)
-* Rate control on process respawn
-* Maybe re-implement "shutdown" ("halt", "reboot") from util-linux to better work
- with dinit.
+ 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).
-Even later:
+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).
factor.
* Cron-like tasks (if started, they run a sub-task periodically. Stopping the
task will wait until the sub-task is complete).
-* Socket activation of services? Not sure if enough non-SystemD derived
- daemons actually support this to warrant implementing it.
* Allow to run services attached to virtual tty, allow connection to that tty (ala "screen").
* SystemD-like handling of filesystem mounts (see autofs documentation in kernel)
i.e. a mount point gets an autofs attached, and lazily gets mounted when accessed
Documentation:
+* Design philosophy/rationale document
+* Coding style guidelines
* What's the best TERM setting? gogetty gives me "linux" but I think other variants may be
better (eg "linux-c").
projects / oweals / dinit.git / blobdiff