system-services.conf - Issue 6879062: Add boot-services milestone marker for boot; fixed udev-addon init time.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: system-services.conf

Issue 6879062: Add boot-services milestone marker for boot; fixed udev-addon init time. (Closed) Base URL: ssh://gitrw.chromium.org:9222/init.git@master

Patch Set: Created 9 years, 8 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

« boot-services.conf ('K') | « syslog.conf ('k') | udev.conf » ('j') | no next file with comments »

OLD	NEW
1 # Copyright (c) 2010 The Chromium OS Authors. All rights reserved.	1 # Copyright (c) 2010 The Chromium OS Authors. All rights reserved.

2 # Use of this source code is governed by a BSD-style license that can be	2 # Use of this source code is governed by a BSD-style license that can be

3 # found in the LICENSE file.	3 # found in the LICENSE file.

4	4

5 description "Job to trigger standard system services"	5 description "Job to trigger standard system services"

6 author "chromium-os-dev@chromium.org"	6 author "chromium-os-dev@chromium.org"

7	7

8 # This job is used as a milestone marker for other jobs that want to	8 # This job is used as a milestone marker for other jobs that want to

9 # start once at system boot, but don't want to delay bringing up	9 # start once at system boot, but don't want to delay bringing up

10 # the login screen. Jobs depending on this job should provide a	10 # the login screen. Jobs depending on this job should provide a

11 # service that is not needed at login and not specific to a user	11 # service that is not needed at login and not specific to a user

12 # session, but that should start once at boot time, possibly staying	12 # session, but that should start once at boot time, possibly staying

13 # up for the life of the system.	13 # up for the life of the system.

14 #	14 #

	15 # NOTE: jobs depending on this job can assume that boot-services

	16 # have been started.
	jrbarnette 2011/04/20 00:04:39 A comment like this should be added to the 'failsa A comment like this should be added to the 'failsafe' job as well. diandersAtChromium 2011/04/20 16:10:02 Done. Show quoted text On 2011/04/20 00:04:39, jrbarnette wrote: > A comment like this should be added to the 'failsafe' job as well. Done.
	17 #

15 # Standard usage:	18 # Standard usage:

16 # start on starting system-services	19 # start on starting system-services

17 # stop on stopping system-services	20 # stop on stopping system-services

18 # Jobs that normally terminate in a bounded time (i.e. don't use	21 # Jobs that normally terminate in a bounded time (i.e. don't use

19 # 'respawn') should omit the 'stop on' stanza.	22 # 'respawn') should omit the 'stop on' stanza.

20	23

21 start on stopped boot-complete	24 start on stopped boot-complete and started boot-services

22 stop on starting halt or starting reboot	25 stop on starting halt or starting reboot

23	26

24 # We only want to start once, but 'stopped boot-complete' happens	27 # We only want to start once, but 'stopped boot-complete' happens

25 # every time Chrome displays the login screen. To avoid firing	28 # every time Chrome displays the login screen. To avoid firing

26 # every time, we omit the main process: upstart marks us running	29 # every time, we omit the main process: upstart marks us running

27 # on the first event, and ignores all subsequent events until we	30 # on the first event, and ignores all subsequent events until we

28 # stop.	31 # stop.

OLD	NEW