From: oetiker <oetiker@a5681a0c-68f1-0310-ab6d-d61299d08faa>
Date: Wed, 24 Sep 2008 06:04:26 +0000 (+0000)
Subject: added section on error reporting -- Florian Forster
X-Git-Url: https://git.verplant.org/?a=commitdiff_plain;h=5bf8f29cfab14076fab38ac26a98fc4993a23b7e;p=rrdtool.git

added section on error reporting -- Florian Forster


git-svn-id: svn://svn.oetiker.ch/rrdtool/trunk/program@1519 a5681a0c-68f1-0310-ab6d-d61299d08faa
---

diff --git a/doc/rrdcached.pod b/doc/rrdcached.pod
index 7631351..e718791 100644
--- a/doc/rrdcached.pod
+++ b/doc/rrdcached.pod
@@ -128,6 +128,15 @@ the disk itself. All other commands can send a B<FLUSH> command (see below) to
 the daemon before accessing the files, so they work with up-to-date data even
 if the cache timeout is large.
 
+=head1 ERROR REPORTING
+
+The daemon reports errors in one of two ways: During startup, error messages
+are printed to C<STDERR>. One of the steps when starting up is to fork to the
+background and closing C<STDERR> - after this writing directly to the user is
+no longer possible. Once this has happened, the daemon will send log messages
+to the system logging daemon using L<syslog(3)>. The facility used it
+C<LOG_DAEMON>.
+
 =head1 HOW IT WORKS
 
 When receiving an update, B<rrdcached> does not write to disk but looks for an