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