The command had not been added into the sudocmd database.
member sudo command: /usr/bin/yum --disableexcludes=all localinstall
example*: no such entry
I think this error should point to someone checking to make sure the sudo
command had been created, something along the lines of no sudocmd
rashard.ke...@sita.aero wrote:
The command had not been added into the sudocmd database.
member sudo command: /usr/bin/yum --disableexcludes=all localinstall
example*: no such entry
I think this error should point to someone checking to make sure the
sudo command had been created,
I would be happy to open a ticket, where do I go to do that?
Thank You,
Rashard Kelly
From: Rob Crittenden rcrit...@redhat.com
To: rashard.ke...@sita.aero, freeipa-users@redhat.com
Date: 03/13/2014 09:52 AM
Subject:Re: [Freeipa-users] Sudo Rule Command Line Option
Arguments
rcrit...@redhat.com
To: rashard.ke...@sita.aero, freeipa-users@redhat.com
Date: 03/13/2014 09:52 AM
Subject:Re: [Freeipa-users] Sudo Rule Command Line Option
Arguments (Solved)
rashard.ke...@sita.aero wrote:
The command had not been added into the sudocmd database.
member
What is the correct way to add a flag inside a sudo command that will be
added to a command group? When adding commands with no flags I have no
issue such as /usr/bin/yum info example* but when I try to add options
to the command like this /usr/bin/yum --disableexcludes=all localinstall
