It seems that viewglob executable needs executables to be in /usr/lib64/viewglob (instead they are in directly in /usr/libexec), yet needs some getoptex, about which I could find only this as most relevant: https://gist.github.com/MisterDA/7284755 https://stackoverflow.com/questions/25371503/iterate-twice-on-bash-scripts-arguments-using-getoptex The fact that it requires gtk2 makes me to think it's now orphaned if not be removed. I get following errors from viewglob script: $ viewglob /usr/bin/viewglob: line 153: /usr/lib64/viewglob/getopt.sh: No such file or directory /usr/bin/viewglob: line 156: getoptex: command not found /usr/bin/viewglob: line 253: /usr/lib64/viewglob/vgping: No such file or directory Next time it appears that vgd is active, slightly more errors happen: (last error with cgd and vgping repeats infinitely). $ viewglob /usr/bin/viewglob: line 153: /usr/lib64/viewglob/getopt.sh: No such file or directory /usr/bin/viewglob: line 156: getoptex: command not found /usr/bin/viewglob: line 235: /usr/lib64/viewglob/vgping: No such file or directory /usr/bin/viewglob: line 253: /usr/lib64/viewglob/vgping: No such file or directory This repeats infinitely: vgd: CRITICAL: Could not setup a listening socket. The last error was: Address already in use /usr/bin/viewglob: line 253: /usr/lib64/viewglob/vgping: No such file or directory
Change to VG_LIB_DIR in viewglob is enough... To make it run without errors (but not more =).