1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
|
.TH started 7 2009-07-09 "Upstart"
.\"
.SH NAME
started \- event signalling that a job is running
.\"
.SH SYNOPSIS
.B started
.BI JOB\fR= JOB
.BI INSTANCE\fR= INSTANCE
.RI [ ENV ]...
.\"
.SH DESCRIPTION
The
.B started
event is generated by the Upstart
.BR init (8)
daemon when an instance of a job has finished starting and is now running. The
.B JOB
environment variable contains the job name, and the
.B INSTANCE
environment variable contains the instance name which will be empty for
single-instance jobs.
.BR 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
.BR stopping (7)
event by services declaring a dependency.
Job configuration files may use the
.B export
stanza to export environment variables from their own environment into
the
.B started
event. See
.BR init (5)
for more details.
.\"
.SH EXAMPLE
A service that wishes to depend on another service might use:
.RS
.nf
start on started apache
stop on stopping apache
.fi
.RE
A task that must be run after another task or service has been started might
use:
.RS
.nf
start on started postgresql
.fi
.RE
.\"
.SH SEE ALSO
.BR starting (7)
.BR stopping (7)
.BR stopped (7)
.BR init (5)
|