[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[dmd] 01/01: doc: Mention the 'status' command in "Jump Start".

From: Ludovic Courtès
Subject: [dmd] 01/01: doc: Mention the 'status' command in "Jump Start".
Date: Thu, 19 Jun 2014 10:31:24 +0000

civodul pushed a commit to branch master
in repository dmd.

commit 3e516eaea4cb6833c5b9292dce80687541b1aedd
Author: Ludovic Courtès <address@hidden>
Date:   Thu Jun 19 12:30:05 2014 +0200

    doc: Mention the 'status' command in "Jump Start".
    * dmd.texi (Jump Start): Mention 'deco status dmd', 'deco
      detailed-status dmd', and 'deco status apache'.
 dmd.texi |   31 +++++++++++++++++++++++++++++--
 1 files changed, 29 insertions(+), 2 deletions(-)

diff --git a/dmd.texi b/dmd.texi
index 2b5138c..757a66e 100644
--- a/dmd.texi
+++ b/dmd.texi
@@ -136,7 +136,7 @@ your dmd installation for example resides in 
 instead, add this directory name in front of the absolute file names
 mentioned below.
address@hidden configuration file
address@hidden Configuration file
 When dmd gets started, it reads and evaluates a configuration file.  When it is
 started with superuser priviledges, it tries to use
 @code{/etc/dmdconf.scm}, when started as normal user, it looks for a
@@ -150,6 +150,7 @@ dmd --config=/etc/dmdconf.scm.old
 dmd -c /etc/dmdconf.scm.old
 @end example
address@hidden Starting a service
 As its name suggests, dmd is just a daemon that (usually) runs in the
 background, so you will not interact with it directly.  After it is
 started, dmd will listen on a socket special file, usually
@@ -161,11 +162,37 @@ straightforward: To start a service called @code{apache}, 
you use:
 deco start apache
 @end example
address@hidden Status (of services)
address@hidden Service status
 When you do this, all its dependencies will get resolved.  For
 example, a webserver is quite likely to depend on working networking,
 thus it will depend on a service called @code{networking}.  So if you
 want to start @code{apache}, and @code{networking} is not yet running, it
-will automatically be started as well.  In the same way, you can stop
+will automatically be started as well.  The current status of all the
+services defined in the configuration file can be queried like this:
+deco status dmd
address@hidden example
+Or, to get additional details about each service, run:
+deco detailed-status dmd
address@hidden example
+In this example, this would show the @code{networking} and @code{apache}
+services as started.  If you just want to know the status of the
address@hidden service, run:
+deco status apache
address@hidden example
address@hidden Stopping a service
+You can stop
 a service and all the services that depend on it will be stopped.
 Using the example above, if you stop @code{networking}, the service
 @code{apache} will be stopped as well---which makes perfect sense,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]