stopped(7)

1stopped(7)             Miscellaneous Information Manual             stopped(7)
2
3
4

NAME

6       stopped - event signalling that a job has stopped
7

SYNOPSIS

9       stopped   JOB=JOB   INSTANCE=INSTANCE  RESULT=RESULT  [PROCESS=PROCESS]
10       [EXIT_STATUS=STATUS] [EXIT_SIGNAL=SIGNAL] [ENV]...
11

DESCRIPTION

13       The stopped event is generated by the Upstart init(8)  daemon  when  an
14       instance  of  a job has stopped.  The JOB environment variable contains
15       the job name,  and  the  INSTANCE  environment  variable  contains  the
16       instance name which will be empty for single-instance jobs.
17
18       If  the  job was stopped normally, the RESULT environment variable will
19       be ok, otherwise if the job was stopped because it has failed  it  will
20       be failed.
21
22       When  the  job has failed, the process that failed will be given in the
23       PROCESS environment variable.  This may be pre-start, post-start, main,
24       pre-stop  or  post-stop;  it  may  also be the special value respawn to
25       indicate that the job was stopped because it hit the respawn limit.
26
27       Finally in the case of a failed  job,  one  of  either  EXIT_STATUS  or
28       EXIT_SIGNAL  may  be  given  to indicate the cause of the stop.  Either
29       EXIT_STATUS will contain the  exit  status  code  of  the  process,  or
30       EXIT_SIGNAL  will  contain  the  name  of  the  signal that the process
31       received.  The normal exit job configuration stanza can be used to pre‐
32       vent  particular  exit  status  values or signals resulting in a failed
33       job, see init(5) for more information.
34
35       If neither EXIT_STATUS or EXIT_SIGNAL is given for a failed process, it
36       is  because  the process failed to spawn (for example, file not found).
37       See the system logs for the error.
38
39       init(8) emits this event as an informational signal, services and tasks
40       started  or  stopped  by  this  event will do so in parallel with other
41       activity.  It is typically combined with the starting(7) event by  ser‐
42       vices when inserting themselves as a dependency.
43
44       Job configuration files may use the export stanza to export environment
45       variables from their own  environment  into  the  stopped  event.   See
46       init(5) for more details.
47

EXAMPLE

49       A  service  that wishes to be running whenever another service would be
50       running, started before and stopped after it, might use:
51
52              start on starting apache
53              stop on stopped apache
54
55       A task that must be run after another task or service has been  stopped
56       might use:
57
58              start on stopped postgresql
59

NAME

SYNOPSIS

DESCRIPTION

EXAMPLE

SEE ALSO