SVN: rc-scripts/trunk/doc/upstart.txt
jajcus
jajcus at pld-linux.org
Wed Jun 15 12:51:39 CEST 2011
Author: jajcus
Date: Wed Jun 15 12:51:39 2011
New Revision: 12243
Modified:
rc-scripts/trunk/doc/upstart.txt
Log:
- upstart usage docs updates
Modified: rc-scripts/trunk/doc/upstart.txt
==============================================================================
--- rc-scripts/trunk/doc/upstart.txt (original)
+++ rc-scripts/trunk/doc/upstart.txt Wed Jun 15 12:51:39 2011
@@ -71,11 +71,14 @@
starting(7) started(7) stopping(7) stopped(7) (see man pages)
As relying on job name is not good enough when several alternative
-implementations of a service are available, the start*/stop* jobs
-may have extra 'SERVICE' variable attached. SERVICE variable contains
-the generic service name, which can be used like this::
+implementations of a service are available. In such case
+each of the alternative jobs should have an extra 'SERVICE_syslog=y'
+variable exported. In van then be used like this::
- start on started SERVICE=syslog
+ start on started SERVICE_syslog=y
+
+Please note that using 'SERVICE=something' will not work, as the value
+will be inherited by any other job with 'export SERVICE'.
Job events and enabling/disabling event-base service startup
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -117,6 +120,16 @@
exec /usr/sbin/syslog-ng -F -f /etc/syslog-ng/syslog-ng.conf
+Checking upstart configuration
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Since Upstart 1.3 one can check current configuration with::
+
+ initctl check-config
+
+Also, with an 'initctl2dot' tool the configuration may be visualised in
+a graphical diagram.
+
Tracking startup progress
~~~~~~~~~~~~~~~~~~~~~~~~~
More information about the pld-cvs-commit
mailing list