>>>>> Joey Hess <jo...@debian.org> writes:
(Oh, I see I've missed this one while filing Bug#544311...)
> My observations in setting up collectd for my machines are:
> * The default rrd setup was appropriate for only one or two out of
> dozens of machines collectd was installed on.
> * On all the rest, by the time I edited the config file to enable
> network reporting and disable rrd, /var/lib/collectd had already had
> a dozen or more MB of rrd files written to it, which added another
> step of going around and cleaning that up, which I have yet to finish
> doing.
[...]
> Splitting the package to collecd and collectd-core would better
> address my needs. I don't know if an additional collectd-client type
> package would be useful, since I'd still have to edit the config file
> to configure the host to log to (AFAIK my vpn doesn't support
> multicast).
My opinion is to have a base collectd package, which in turn
Recommends: collectd-rrdtool containing just the aforementioned
plugin.
As it was noted, the configuration file as it's currently
supplied is going to be useless with the rrdtool plugin removed.
Therefore, and also to avoid the ``disk full'' situation, I ask
for an explicit activation for collectd, like it's done, e. g.,
for the smartmontools package:
$ ar p smartmontools_5.38-3_amd64.deb data.tar.gz \
| tar -zxO ./etc/default/smartmontools
# Defaults for smartmontools initscript (/etc/init.d/smartmontools)
# This is a POSIX shell fragment
# List of devices you want to explicitly enable S.M.A.R.T. for
# Not needed (and not recommended) if the device is monitored by smartd
#enable_smart="/dev/hda /dev/hdb"
# uncomment to start smartd on system startup
#start_smartd=yes
# uncomment to pass additional options to smartd on startup
#smartd_opts="--interval=1800"
$
(Note the commented out `start_smartd=yes' option.)
--
FSF associate member #7257
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
