3 * Man pages for all programs (done for dinit and dinitctl, not for shutdown/halt etc).
4 * The DINIT_ROLLBACK_COMPLETED acknowledgement is never sent, since
5 control_conn_t::rollback_complete() is not currently called. Fix.
6 * Write wtmp entry on startup (see simpleinit). Investigate.
7 * Support S6-style startup notification (write to fd).
11 * "triggered" service type: external process notifies Dinit when the service
13 * on shutdown, after repeated intervals with no activity, display information
14 about services we are waiting on (or, do this when prompted via ^C or C-A-D).
15 * Documentation must be complete (see section below).
16 * Proper support for socket activation?
17 * Be able to boot and shutdown Linux and FreeBSD.
18 * Refuse to start new services during shutdown.
22 * On linux when running with PID != 1, write PID to /proc/sys/kernel/cad_pid so
23 that we still receive SIGINT from ctrl+alt+del (must be done after /proc is
24 mounted, possibly could be left to a service script)
25 * Perhaps need a way to prevent script services from re-starting.
26 (eg there's no need to mount filesystems twice; there might be various other
27 system initialisations that can't or shouldn't really be "undone" and so do
28 not need to be re-done).
29 * Internationalisation
30 * A service can prevent shutdown/reboot by failing to stop. Maybe make
31 multiple CTRL-ALT-DEL presses (or ^C since that's more portable) commence
32 immediate shutdown (or launch a simple control interface).
33 * When we take down a service or tty session, it would be ideal if we could kill
34 the whole process tree, not just the leader process (need cgroups or pid
35 namespace or other mechanism).
36 * Allow logging tasks to memory (growing or circular buffer) and later
37 switching to disk logging (allows for filesystem mounted readonly on boot).
38 But perhaps this really the responsibility of another daemon.
39 * Allow running services with different resource limits, chroot, cgroups,
40 namespaces (pid/fs/uid), etc
41 * Support chaining service output to another process (logger) input; if the
42 service dies the file descriptor of its stdout isn't closed and is reassigned
43 when the service is restarted, so that minimal output is lost.
44 - even more, it would be nice if a single logger process could be responsible
45 for receiving output from multiple services. This would require some kind of
46 protocol for passing new output descriptors to the logger (for when a
49 Even later / Maybe never:
50 -------------------------
51 * Support recognising /etc/init.d services automatically (as script services, with
52 no dependency management - or upstart compatible dependency management)
53 Also BSD's rc.d style scripts (PROVIDE, REQUIRE).
54 * Place some reasonable, soft limit on the number of services to be started
55 simultaneously, to prevent thrashing. Services that are taking a long time
56 to start don't count to the limit. Maybe use CPU/IO usage as a controlling
58 * Cron-like tasks (if started, they run a sub-task periodically. Stopping the
59 task will wait until the sub-task is complete).
60 * Allow to run services attached to virtual tty, allow connection to that tty (ala "screen").
61 * SystemD-like handling of filesystem mounts (see autofs documentation in kernel)
62 i.e. a mount point gets an autofs attached, and lazily gets mounted when accessed
63 (or is mounted in parallel). Probably put the functionality in a separate daemon.
68 * Design philosophy/rationale document
69 * Coding style guidelines
71 * What's the best TERM setting? gogetty gives me "linux" but I think other variants may be
72 better (eg "linux-c").
74 * Figure out the ConsoleKit/logind / PolicyKit mess & how dinit needs to fit into it.
75 * Consolekit/logind tracks "sessions". Provides a mechanism to mark a session starting,
76 associates processes with sessions, provides calls to terminate sessions etc (why?!!)
77 Can use environment variable or cgroups to track processes in a session.
78 A PAM module exists to create/destroy sessions.
79 * Consolekit/logind also allows for requesting shutdown, reboot, and inhibiting reboot
81 * "seats" are a set of input/output hardware (mouse/keyboard/monitor) on which a session
82 can be run. You can have multiple sessions on a seat - one is in the foreground
83 (eg linux virtual ttys implement multiple sessions on a single seat).
84 Sessions can run without a seat (eg ssh session).