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
Status | Original: In Review [ 10101 ] | New: Pending Response [ 10000 ] |
Status | Original: Pending Response [ 10000 ] | New: In Review [ 10101 ] |
Comment |
[ _*General questions and device support can be discussed in [our Discord channel, click here to join|https://discord.gg/GjpNXKWm8W].*_ ---- Please make and attach additional information about the device: * full snmp dump from device: {noformat} snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk {noformat} _If device not support SNMP version 2c, replace -v2c with -v1._ * If you have problems with discovery or poller processes, please do and attach these debugs: {noformat} ./discovery.php -d -h <device> ./poller.php -d -h <device> {noformat} * additionally attach device and/or vendor specific MIB files ---- {color:#505F79}_This comment is added automatically._{color} ] |
Status | Original: Open [ 1 ] | New: Pending Response [ 10000 ] |