- upstart usage docs updates

svn-id: @12243

diff --git a/doc/upstart.txt b/doc/upstart.txt
index 13001832991913d7780846f3ff46ed2af37da274..6431675d91671a740f4f8d894adbbd77024731a5 100644 (file)
--- a/doc/upstart.txt
+++ b/doc/upstart.txt
@@ -71,11 +71,14 @@ The standard Upstart events are available for job control:
 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 @@ Simple example, the job description for syslog-ng::
   
   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
 ~~~~~~~~~~~~~~~~~~~~~~~~~