Modules
Modules are the heart of initng. They can
- add commands for services (*.i files)
- add options to the ngc command
- react to signals like SIGINT, SIGHUP
- control the output of initng
- add states to the list of possible states of a service
... and more :-) They are the heart of !InitNG, the initng binary is (almost) only a loader for modules and provides the framework for information flow between the modules and internal objects.
In the future, this and other pages describing the plugins will be automatically created from the source's repo.
List
- also tie services together and start/stop them as a set
- bash_launcher launcher for shell scripts
- chdir change Directories
- chroot change Root Directory
- conflict mark conflicting services
- cpout initng's colorful output
- critical mark system-critical services
- ctrlaltdel handle Ctrl-Alt-Del and SIGINT
- daemon manage daemons (start, fork, respawn etc)
- daemon_clean
- dbus_event
- debug_commands
- envparser parse shell environment files, e.g. from /etc/default
- event?
- find
- fmon?
- fstat wait for existence of files
- history store and query initng's action history
- idleprobe wait until CPU is idle
- initctl main control of initng, e.g. for Halt, Reboot and Runlevels.
- interactive ask if a service should be started/stopped
- iparser parser for /etc/initng/*/*.i files
- last
- limit set resource limits
- lockfile
- logfile
- netdev?
- netprobe
- ngc4
- ngcs
- nge
- pause
- provide creates virtual services
- reload
- renice
- rlparser? parser for /etc/initng/*.runlevel files
- runlevel
- selinux?
- service run and manage services
- service_file?
- simplelauncher
- stcmd
- stdout
- suid
- syncron
- syslog
- sysreq?
- unneeded
