From b85a2a653f1b0a9aa1109ee4e606071e06cc7545 Mon Sep 17 00:00:00 2001 From: Daniel Berteaud Date: Tue, 21 May 2019 15:03:46 +0200 Subject: [PATCH] vdo scripts must use sudo --- zabbix_conf/vdo.conf | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/zabbix_conf/vdo.conf b/zabbix_conf/vdo.conf index 8c04c8a..95c1860 100644 --- a/zabbix_conf/vdo.conf +++ b/zabbix_conf/vdo.conf @@ -1,12 +1,12 @@ # Discover VDO volumes # $1 not used for now -UserParameter=vfs.vdo.vol.discovery[*],/var/lib/zabbix/bin/disco_vdo_sudo --what=volumes +UserParameter=vfs.vdo.discovery[*],/var/lib/zabbix/bin/disco_vdo_sudo --what=$1 # Type: Agent or Agent (active) # Key: vfs.vdo.vol[volume,item] where volume is the name of the volume to monitor # item can be one of the valid keys (run manually without --value arg to see available keys) -UserParameter=vfs.vdo.vol[*],/var/lib/zabbix/bin/check_vdo_sudo --volume=$1 --value=$2 +UserParameter=vfs.vdo.vol[*],sudo /var/lib/zabbix/bin/check_vdo_sudo --volume=$1 --value=$2 # Type: Agent or Agent (active) # You can also get all the info about a vdo volume at once, in JSON -UserParameter=vfs.vdo.vol.all[*],/var/lib/zabbix/bin/check_vdo_sudo --volume=$1 +UserParameter=vfs.vdo.vol.all[*],sudo /var/lib/zabbix/bin/check_vdo_sudo --volume=$1