X-Git-Url: https://git.tokkee.org/?a=blobdiff_plain;f=doc%2Frrdcached.html;h=1ad399ac6f643f751ecc133be2c43f43cccf7e02;hb=7d65d8085aa7dd49a1267371e0963bd567656f10;hp=717be17ef38ce967e2c5f135a3527a9264351b43;hpb=2d7eb66e602a5c53dc2fafd70aa6ec4d7b447be9;p=pkg-rrdtool.git diff --git a/doc/rrdcached.html b/doc/rrdcached.html index 717be17..1ad399a 100644 --- a/doc/rrdcached.html +++ b/doc/rrdcached.html @@ -86,7 +86,7 @@ force writing of values to disk, so that graphing facilities and similar can work with up-to-date data.

The daemon was written with big setups in mind. Those setups usually run into IO related problems sooner or later for reasons that are beyond the scope -of this document. Check the wiki at the RRDTool homepage for details. Also +of this document. Check the wiki at the RRDtool homepage for details. Also check SECURITY CONSIDERATIONS below before using this daemon! A detailed description of how the daemon operates can be found in the HOW IT WORKS section below.

@@ -101,7 +101,7 @@ section below.

Tells the daemon to bind to address and accept incoming connections on that socket. If address begins with unix:, everything following that prefix is interpreted as the path to a UNIX domain socket. Otherwise the address or node -name are resolved using getaddrinfo.

+name are resolved using getaddrinfo.

For network sockets, a port may be specified by using the form [address]:port. If the address is an IPv4 address or a fully qualified domain name (i. e. the address contains at least one dot @@ -256,28 +256,38 @@ containing ../ will also be blocked.

AFFECTED RRDTOOL COMMANDS

The following commands may be made aware of the rrdcached using the command line argument --daemon or the environment variable RRDCACHED_ADDRESS:

-
-
dump
- -
fetch
- -
flush
- -
graph
- -
graphv
- -
info
- -
last
- -
lastupdate
- -
update
- -
xport
- -
+

The update command can send values to the daemon instead of writing them to the disk itself. All other commands can send a FLUSH command (see below) to the daemon before accessing the files, so they work with up-to-date data even @@ -290,7 +300,7 @@ if the cache timeout is large.

are printed to STDERR. One of the steps when starting up is to fork to the background and closing 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 syslog(3). The facility used is +to the system logging daemon using syslog(3). The facility used is LOG_DAEMON.

@@ -305,7 +315,7 @@ diagram below) are appended to the tree node.

When appending a value to a tree node, it is checked whether it's time to write the values to disk. Values are written to disk if now() - First >= timeout, where timeout is the timeout specified -using the -w option, see OPTIONS. If the values are "old enough" they +using the -w option, see OPTIONS. If the values are "old enough" they will be enqueued in the "update queue", i. e. they will be appended to the linked list shown below. Because the tree nodes and the elements of the linked list are the same data structures in memory, any update to a file that @@ -436,7 +446,7 @@ files will be messed up good!

PROTOCOL

The daemon communicates with clients using a line based ASCII protocol which is easy to read and easy to type. This makes it easy for scripts to implement the -protocol and possible for users to use telnet to connect to the daemon +protocol and possible for users to use telnet to connect to the daemon and test stuff "by hand".

The protocol is line based, this means that each record consists of one or more lines. A line is terminated by the line feed character 0x0A, commonly @@ -675,8 +685,8 @@ updates WILL BE LOST.

AUTHOR

-

rrdcached and this manual page have been written by Florian Forster -<octo at verplant.org>.

+

Florian Forster <octo at verplant.org>

+

Both rrdcached and this manual page have been written by Florian.