stopped(7) - phpMan

Command: man perldoc info search(apropos)  

stopped(7)                                                          stopped(7)

       stopped - event signalling that a job has stopped


       The stopped event is generated by the Upstart init(8) daemon when an instance of  a
       job  has  stopped.   The  JOB  environment  variable contains the job name, and the
       INSTANCE environment variable contains the instance name which will  be  empty  for
       single-instance jobs.

       If the job was stopped normally, the RESULT environment variable will be ok, other-
       wise if the job was stopped because it has failed it will be failed.

       When the job has failed, the process that failed will be given in the PROCESS envi-
       ronment  variable.  This may be pre-start, post-start, main, pre-stop or post-stop;
       it may also be the special value respawn to  indicate  that  the  job  was  stopped
       because it hit the respawn limit.

       Finally  in  the case of a failed job, one of either EXIT_STATUS or EXIT_SIGNAL may
       be given to indicate the cause of the stop.  Either EXIT_STATUS  will  contain  the
       exit status code of the process, or EXIT_SIGNAL will contain the name of the signal
       that the process received.  The normal exit job configuration stanza can be used to
       prevent  particular  exit  status  values or signals resulting in a failed job, see
       init(5) for more information.

       If neither EXIT_STATUS or EXIT_SIGNAL is given for a failed process, it is  because
       the process failed to spawn (for example, file not found).  See the system logs for
       the error.

       init(8) emits this event as an informational signal, services and tasks started  or
       stopped  by this event will do so in parallel with other activity.  It is typically
       combined with the starting(7) event by services  when  inserting  themselves  as  a

       Job  configuration  files may use the export stanza to export environment variables
       from their own environment into the stopped event.  See init(5) for more details.

       A service that wishes to be running whenever  another  service  would  be  running,
       started before and stopped after it, might use:

              start on starting apache
              stop on stopped apache

       A task that must be run after another task or service has been stopped might use:

              start on stopped postgresql

       starting(7) started(7) stopping(7) init(5)

Upstart                           2009-07-09                        stopped(7)

Generated by $Id: phpMan.php,v 4.55 2007/09/05 04:42:51 chedong Exp $ Author: Che Dong
On Apache
Under GNU General Public License
2017-12-14 16:54 @ CrawledBy CCBot/2.0 (
Valid XHTML 1.0!Valid CSS!