[smokeping-users] using sudo in an alert
rb14060 at gmail.com
Wed Jul 25 18:23:52 CEST 2012
Try using the absolute path to the script in the sudoers file. Also, the
/etc/sudoers file should NOT be edited directly, you should be using the
visudo command as root.
On Wed, Jul 25, 2012 at 4:41 AM, Andrew Pattison <andrum99 at gmail.com> wrote:
> I've got something similar in in /etc/sudoers already.
> On 24 July 2012 23:15, Ryan Becker <rb14060 at gmail.com> wrote:
>> Make sure that the user is allowed to execute the script without a
>> password. Here's an example that you can modify to suit your
>> needs: techbnc ALL = NOPASSWD: /usr/sbin/csf
>> In this example the user techbnc is allowed to call /usr/sbin/csf without
>> needing a password. What's happening is that normally when sudo is called,
>> it asks for the password and Smokeping has no way to provide that password.
>> By adding the user to the file with NOPASSWD, they are allowed to execute
>> the script without being password prompted and therefore Smokeping will be
>> able to complete the action.
>> On Tue, Jul 24, 2012 at 5:35 PM, Andrew Pattison <andrum99 at gmail.com>wrote:
>>> I am trying to set up smokeping with an alert script. The alert script
>>> is called like this entry in /etc/smokeping/config.d/Alerts:
>>> to = |sudo script.py
>>> When called as simply |script.py this works fine, but with sudo the
>>> script does not get called. How can I get this working?
>>> smokeping-users mailing list
>>> smokeping-users at lists.oetiker.ch
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the smokeping-users