Package Details: stackdriver-collectd 6.1.3-1

Git Clone URL: https://aur.archlinux.org/stackdriver-collectd.git (read-only, click to copy)
Package Base: stackdriver-collectd
Description: Stackdriver's monitoring agent based on collectd
Upstream URL: https://github.com/Stackdriver/collectd
Licenses: MIT
Conflicts: collectd
Provides: stackdriver-collectd
Submitter: shulhan
Maintainer: shulhan
Last Packager: shulhan
Votes: 0
Popularity: 0.000000
First Submitted: 2020-12-01 12:12
Last Updated: 2021-07-20 15:27

Latest Comments

shulhan commented on 2021-07-20 15:34

Strange that it would read from /etc and not /opt/collectd. Perhaps this can be changed either by a make option i.e. it seems like there's an overall prefix of /opt/collectd

I just check and rebuild the package by setting the prefix to /usr. When the collectd run its failed to load the plugins. Seems like the code use static paths fixed to /opt/collectd,

$ collectd -h

...

Builtin defaults:
  Config file       /opt/collectd/etc/collectd.conf
  PID file          /opt/collectd/var/run/collectd.pid
  Plugin directory  /opt/collectd/lib/collectd
  Data directory    /opt/collectd/var/lib/collectd

BTW, I have updated the version and systemd service and fix some installation issues.

JP-Ellis commented on 2021-07-13 09:47

Strange that it would read from /etc and not /opt/collectd. Perhaps this can be changed either by a make option i.e. it seems like there's an overall prefix of /opt/collectd, so removing it might adjust the config path automatically. Alternatively, it could also be possible to just tell collectd where to look for the configuration file in the systemd service (though I agree it would be better if it automatically found it).

shulhan commented on 2021-07-13 09:09

Is there any reason this is installed in /opt/collectd?

My memory kinda blur, last time I remembered, it will not read the configuration in /etc but from /opt/collectd.

Lastly, I'm not really sure the service should be forking. You can add the -f flag to prevent forking which I believe systemd prefers.

I didn't know that flag exists. Let me check again later ... or do you have patch?

Will update the version later.

JP-Ellis commented on 2021-07-13 08:10

Is there any reason this is installed in /opt/collectd? It appears to me that the directory structure within /opt/collectd is compatible with having it installed within /usr.

It would also make more sense to have the configuration files in /etc (instead of /opt/etc) and the PID file in /run, etc.

Lastly, I'm not really sure the service should be forking. You can add the -f flag to prevent forking which I believe systemd prefers.