Seth Woolley's Man Viewer

initctl(8) - initctl, initctl - utility to control simpleinit(8) - man 8 initctl

([section] manual, -k keyword, -K [section] search, -f whatis)
man plain no title

INITCTL(8)                                                          INITCTL(8)

       initctl - utility to control simpleinit(8)

       need [-r] service
       provide service

       The initctl programme is designed to help improve the robustness, scal-
       ability and readability of system boot scripts. It is now  possible  to
       write(1,2) a modularised set(7,n,1 builtins) of boot scripts without the complex and fragile
       numbered symlink scheme used in(1,8) SysV-style boot  scripts.  Each  script
       can simply declare, using need(8), what must run before them.

       The  need  programme  is  a utility that tells simpleinit(8) to start a
       service (usually a script in(1,8) /sbin/init.d) and will wait for  the  ser-
       vice  to become available. If the service is already available, it will
       not be started again.

       The -r option is used to tell simpleinit(8) to "roll back" (stop)  ser-
       vices  up  to (but not including) service. If service is not specified,
       all services are stopped. The -r option thus allows the  system  to  be
       partially  or  wholly  shut down in(1,8) an orderly fashion. The shutdown(2,8)(8)
       programme still needs to be run.

DESCRIPTION for display-services
       When invoked as display-services it will write(1,2) the  list  of  currently
       available services and the list of failed services to the standard out-

DESCRIPTION for provide
       When invoked as provide it tells simpleinit(8) that the  parent  (call-
       ing)  process  will  be  providing  a service with name service. If the
       calling process exits successfully (status 0) the service is deemed  to
       be available. Only one instance of service may be started, so alternate
       providers will block and may fail.

       Using provide it is possible to have multiple potential  providers  for
       the  same (generic) service (e.g. sendmail(1,8) and qmail both provide a mta
       service), where only one actually provides the  service.  This  may  be
       used by service startup scripts which check for configuration files.

       The exit(3,n,1 builtins) code from need is 0 if(3,n) the service was successfully started, 1
       if(3,n) the service failed badly, and 2 if(3,n) the service is unavailable  (i.e.
       disabled  in(1,8)  configuration  files).  These exit(3,n,1 builtins) codes reflect the exit(3,n,1 builtins)
       codes from the service startup scripts.

       The exit(3,n,1 builtins) code from need  -r  is  0  if(3,n)  the  service  was  successfully
       stopped,  1  if(3,n)  the service could not be stopped, and 2 if(3,n) the service
       was not available to start with. The service shutdown(2,8) scripts may  only
       return 0 (for success) or 1 (for failure).

       The exit(3,n,1 builtins) code from provide is 0 if(3,n) the service may be provided, 1 if(3,n) it
       may not, and 2 if(3,n) the parent process is not a child  of  init.  It  may
       block waiting for another provider which is initialising the service.

       initctl(8)  uses  SIGUSR1,  SIGUSR2  and SIGPOLL for communication with
       simpleinit(8). Don't send(2,n) these signals to it.

       /dev/initctl        This is the control FIFO, created by simpleinit(8),
                           which initctl(8) writes commands to.
       simpleinit(8), init(8)
       A  more  complete  discussion  of  the new boot script system, based on
       need(8),               is                available                from:
       Richard Gooch (
       The   Util-Linux   package   is   available   from:   ftp://ftp.??.ker-

Util-Linux Package                21 Feb 2001                       INITCTL(8)

References for this manual (incoming links)