wt/finit
1
0 Fork 0
mirror of https://github.com/troglobit/finit.git synced 2026-10-29 12:40:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update and clarify TODO items, e.g., add info on new "task" and "run" stanzas

Browse Source 
Signed-off-by: Joachim Nilsson <troglobit@gmail.com>
This commit is contained in:
Joachim Nilsson committed 2013-06-04 07:21:00 +02:00
1 parent f690767507
commit bf0cfe0693
1 file changed
+20 -12
Download Patch File Download Diff File Expand all files Collapse all files
TODO.rst
+20 -12
View File
@@ -40,14 +40,14 @@ Runlevels
--------- ---------
* Add support for "runlevel N" to finit.conf * Add support for "runlevel N" to finit.conf
* Improve support for runlevels: startup, running (services from * Improve support for runlevels: startup, running (services from
finit.conf), and shutdown as well as hooks when switching RL, finit.conf), and shutdown as well as hooks when switching RL, startup
startup at RL 1 and a default run level. at RL 1 and a default run level.
* Implement initctl stop|start|restart|reload|status <SVC> and * Implement initctl stop|start|restart|reload|status <SVC> and service
service <SVC> stop|start|restart|reload|status on top <SVC> stop|start|restart|reload|status on top
* Add PRE and POST hooks for when changing runlevels * Add PRE and POST hooks for when changing runlevels
* SysV init in Debian uses an rcS.d/ for scripts that should run once * SysV init in Debian uses an rcS.d/ for scripts that should run once at
at boot. These scripts are run before the actual runlevel set in boot. These scripts are run before the actual runlevel, which is set
inittab. In finit we could use "task [S]" and "boot [S]" for this. in inittab. We could use "task [S]" and "run [S]" (below) for this.
* Add support for a new runlevel 'S' that is started before all other * Add support for a new runlevel 'S' that is started before all other
services in the selected runlevel. services in the selected runlevel.
@@ -57,18 +57,26 @@ Both the "task" and "boot" stanzas below are like "service", share the
same mechanism for registering callbacks. These callbacks can be used same mechanism for registering callbacks. These callbacks can be used
to check a configuration db and return 1 (RUN), 2 (STOP), or 3 (RELOAD). to check a configuration db and return 1 (RUN), 2 (STOP), or 3 (RELOAD).
* Add support for "task [RUNLVL] ..." similar to services, but * Add support for "task [RUNLVL] ..." similar to services, but one-shot.
one-shot. Needs a trigger/when * Add support for "run [RUNLVL] ..." similar to task, but waits for
* Add support for "boot [RUNLVL] ..." similar to services, but completion before continuing with the next task/service
waits for completion before continuing with the next line * Add support for service/task/run dependencies
* Add support for service/task dependencies
* Add support for "init list" to show running services * Add support for "init list" to show running services
It is tempting to say that a task called at runlevel S would be a
blocking call, like run, but there are likely use-cases when you want to
call on-shot tasks in parallell with something else, even at boot. Hence
the differentiation between "task" and "run", which are essentially the
same, except for the "pause and wait for completion" that "run" has.
Miscellaneous Miscellaneous
------------- -------------
* Add support for "init -v,--version | version" * Add support for "init -v,--version | version"
* Cleanup move sources from top-level directory to src/ and include/ * Cleanup move sources from top-level directory to src/ and include/
* Make sure to install queue.h to $(PREFIX)/include/finit/queue.h * Make sure to install queue.h to $(PREFIX)/include/finit/queue.h
* Move finit.conf "check" command to plugin which checks /etc/fstab
instead. This is the de-facto practise. But keep the check command
for really low-end systems w/o /etc/fstab.
Documentation Documentation
------------- -------------