diff options
author | ajax <ajax@980ebf18-57e1-0310-9a29-db15c13687c0> | 2006-10-05 22:18:05 +0000 |
---|---|---|
committer | ajax <ajax@980ebf18-57e1-0310-9a29-db15c13687c0> | 2006-10-05 22:18:05 +0000 |
commit | ab0141a2e03542902fc0d83d76b55d5e4b8811d0 (patch) | |
tree | 722852178d52f9b2fe6993395f6fadf809561b9b /documentation | |
parent | c7a73812a84178425f774af0fa14d97c67469451 (diff) | |
download | puppet-ab0141a2e03542902fc0d83d76b55d5e4b8811d0.tar.gz puppet-ab0141a2e03542902fc0d83d76b55d5e4b8811d0.tar.xz puppet-ab0141a2e03542902fc0d83d76b55d5e4b8811d0.zip |
More specific configuration and argument documentation.
git-svn-id: https://reductivelabs.com/svn/puppet/trunk@1738 980ebf18-57e1-0310-9a29-db15c13687c0
Diffstat (limited to 'documentation')
-rw-r--r-- | documentation/documentation/reports.page | 21 |
1 files changed, 15 insertions, 6 deletions
diff --git a/documentation/documentation/reports.page b/documentation/documentation/reports.page index f341582be..f7b13e66d 100644 --- a/documentation/documentation/reports.page +++ b/documentation/documentation/reports.page @@ -33,20 +33,29 @@ With this setting enabled, the client will then send the data necessary for repo Next, the server must be configured to intepret the report results. We'll tell it which reports to run by giving it a comma-separated list of reports we want to run against the client-submitted data. Again, we can do this from the command line, like so: - $ puppetmasterd --reports tagmail, daily, security + $ puppetmasterd --reports tagmail,daily,security +or you might enclose the list of reports in quotes: + + $ puppetmasterd --reports "tagmail,daily,security" + +note that leaving spaces in between the report names will result in an error: + + $ puppetmasterd --reports tagmail, daily, security # Wrong. + or we can include these configuration parameters in the configuration file, typically `/etc/puppet/puppetmasterd.conf`. For example, # # /etc/puppetmasterd.conf # [puppetmasterd] - reports = tagmail, daily, security + reports = tagmail,daily,security +Note that in the configuration file, the list of reports should be comma-separated without spaces and not enclosed in quotes (which is otherwise acceptable for a command-line invocation). -You may also wish to specify the directory where reports will be stored with the `[reportdirectory](configref.html#reportdirectory)` parameter. Furthermore, transaction +You may also wish to specify the directory where reports will be stored with the [reportdirectory](configref.html#reportdirectory) parameter. Furthermore, transaction reports can optionally be sent to a special report server (not necessarily the server or -client). This server can be specified with the `[reportserver](configref.html#reportserver)`. +client). This server can be specified with the [reportserver](configref.html#reportserver). For more about configuring your server, take a look at the section on [Configuration Reference](configref.html). @@ -83,11 +92,11 @@ The server through which to send email reports. ### rrdgraph -The `rrdgraph` reports on the puppet system and its operations. The reports are stored as HTML in the rrd directory, so puppet must have write access to this directory. +The `rrdgraph` report reports on the puppet system and its operations. The reports are stored as HTML in the rrd directory, so puppet must have write access to this directory. #### rrddir The directory into which puppet will put the web-ready report files. Of course, this directory will need to be puppet-writable. -* $Id:$ +* $Id$ |