TODO 4.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990
  1. For version 0.7.0:
  2. ------------------
  3. * dinitctl: Warn when stopping a service would cause a dependent to stop. Require a force flag to proceed.
  4. * dinitctl: implement "restart" command.
  5. * provide a way to check configuration for errors (maybe a dinitctl command)
  6. - eg. check a service and all dependencies.
  7. * report process launch failure reason (stage & errno) via dinitctl.
  8. * "chain-to" can result in an unbreakable loop if the chain is circular. Chained services should not be
  9. started during shutdown to prevent this (also avoids a race condition where the chained service is left
  10. running when everything else has shutdown).
  11. For version 1.0:
  12. ----------------
  13. * "triggered" service type: external process notifies Dinit when the service
  14. has started. (maybe?)
  15. - key thing is we want some way to eg mount filesystem once the disk comes up,
  16. configure network when device comes up, etc, potentially relying an an external
  17. tool/daemon.
  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. * Chaining of service process input/output?
  23. * Be able to boot and shutdown Linux and FreeBSD (or OpenBSD).
  24. For later:
  25. ----------
  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
  51. service starts).
  52. Even later / Maybe never:
  53. -------------------------
  54. * Support recognising /etc/init.d services automatically (as script services, with
  55. no dependency management - or upstart compatible dependency management)
  56. Also BSD's rc.d style scripts (PROVIDE, REQUIRE).
  57. * Place some reasonable, soft limit on the number of services to be started
  58. simultaneously, to prevent thrashing. Services that are taking a long time
  59. to start don't count to the limit. Maybe use CPU/IO usage as a controlling
  60. factor.
  61. * Cron-like tasks (if started, they run a sub-task periodically. Stopping the
  62. task will wait until the sub-task is complete).
  63. * Allow to run services attached to virtual tty, allow connection to that tty (ala "screen").
  64. * SystemD-like handling of filesystem mounts (see autofs documentation in kernel)
  65. i.e. a mount point gets an autofs attached, and lazily gets mounted when accessed
  66. (or is mounted in parallel). Probably put the functionality in a separate daemon.
  67. Documentation:
  68. --------------
  69. * Design philosophy/rationale document
  70. * 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").
  73. * Figure out the ConsoleKit/logind / PolicyKit mess & how dinit needs to fit into it.
  74. * Consolekit/logind tracks "sessions". Provides a mechanism to mark a session starting,
  75. associates processes with sessions, provides calls to terminate sessions etc (why?!!)
  76. Can use environment variable or cgroups to track processes in a session.
  77. A PAM module exists to create/destroy sessions.
  78. * Consolekit/logind also allows for requesting shutdown, reboot, and inhibiting reboot
  79. (via dbus API).
  80. * "seats" are a set of input/output hardware (mouse/keyboard/monitor) on which a session
  81. can be run. You can have multiple sessions on a seat - one is in the foreground
  82. (eg linux virtual ttys implement multiple sessions on a single seat).
  83. Sessions can run without a seat (eg ssh session).