Details
-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Professional Edition
-
None
Description
Over the years, files in my rrd directory have inconsistent group ownership (observium or www-data) and inconsistent file permissions (mostly group write issues.)
Command line accidents (like running poller.php as root) can also mess things up
Incorrect cron issues aside...
ASK:
Would it worth making scripts that create files in the rrd directory enforce the owner/group/permissions for the files?
My argument here is that a whole class of user confusion can be avoided by enforcing ownership/permissions when possible, and visibly noting a permissions error in the web interface when not.
I was surprised that poller.php -h foo didn't complain when the rrd/foo directory was owned by root, and that the web interface was silent on the matter.
Attachments
Activity
The Web UI and Poller don't always have direct access to these files, often they're accessed via rrdcached.
It would likely be fairly slow and wasteful for most users to do permissions checks on every rrd file during polling.
What would probably be a good idea would be to get the poller to switch to the observium user when configured so in config.php. This would solve this on new installs via the install script as we could automate it.