author | oetiker <oetiker@a5681a0c-68f1-0310-ab6d-d61299d08faa> | |
Mon, 8 Mar 2010 17:13:16 +0000 (17:13 +0000) | ||
committer | oetiker <oetiker@a5681a0c-68f1-0310-ab6d-d61299d08faa> | |
Mon, 8 Mar 2010 17:13:16 +0000 (17:13 +0000) | ||
commit | f34b8c9f42f4b2de0b669d228572fef73339e938 | |
tree | bca9b695276dd0b6eec595ab38bc318f8917753b | tree | snapshot |
parent | 6b3375c53f5e3f7bc88b16d667d7b773b7f4445f | commit | diff |
Obviously this will only work if rrdcached is running as root which in
my case it has to be (as upstart can't currently monitor non-root
daemons). As you may have RRD data sources (data loggers) and RRD
consumers (e.g. CGI scripts) that both need to talk to the cache
daemon one solution is to set the group permissions of the socket.
This offer some flexibility over trying to get every RRD user/daemon
running under the same user context. -- Alex Bennee ajb pitcairn.cambridgebroadband.com
git-svn-id: svn://svn.oetiker.ch/rrdtool/trunk@2029 a5681a0c-68f1-0310-ab6d-d61299d08faa
my case it has to be (as upstart can't currently monitor non-root
daemons). As you may have RRD data sources (data loggers) and RRD
consumers (e.g. CGI scripts) that both need to talk to the cache
daemon one solution is to set the group permissions of the socket.
This offer some flexibility over trying to get every RRD user/daemon
running under the same user context. -- Alex Bennee ajb pitcairn.cambridgebroadband.com
git-svn-id: svn://svn.oetiker.ch/rrdtool/trunk@2029 a5681a0c-68f1-0310-ab6d-d61299d08faa
program/doc/rrdcached.pod | diff | blob | history | |
program/src/rrd_daemon.c | diff | blob | history |