WILLIAM J LUTTER wrote:
> Following a Feb 06 update of the sudo package to sudo.i386 1.6.9p17-3.el5_3.1 I find that its behavior has changed for my simple usage.  The linux box runs SL5.1 (earliest SL5 as I remember).  
> 
> As a separate question, how do I easily deduce which SL version I am running? 
> 
> Back to sudo issue:
> I usually specify a user alias via these lines using visudo:
> User_Alias      STAFF=user1,user2
> 
> # User privilege specification
> root    ALL=(ALL) ALL
> STAFF   ALL=(ALL) ALL
> 
> Not very sophisticated, but it works for our small work group.  We also turn off selinux.
> 
> After the sudo update, usage of sudo yields an error message following entry of a password:
> sudo: symbol lookup error: sudo: undefined symbol: audit_log_user_command
> 
> I tried following the suggestion in the visudo text:
> ## User Aliases
> ## These aren't often necessary, as you can use regular groups
> ## (ie, from files, LDAP, NIS, etc) in this file - just use %groupname
> ## rather than USERALIAS
> # User_Alias ADMINS = jsmith, mikem
> 
>  Say groupname for user1 and user2 is group12, then
>  %group12  ALL=(ALL) ALL
> 
> This also yields same error message.  Not being an IT person, I'm a bit at a loss.  I either need to go back to an earlier package such as sudo-1.6.7p5-30.1.3.i386 where this behavior did not occur or get clued in on what the proper visudo configuration is...
> 
> Is this an obvious config file issue?  If not, is it an error in the new sudo?  If not, what is the simplest way to use yum to access earlier versions of sudo, or should I just remove current one and find the rpm package for sudo-1.6.7p5-30.1.3.i386 and install that via rpm commands?
> 
> Bill Lutter

Looking into this.
Troy
-- 
__________________________________________________
Troy Dawson  [log in to unmask]  (630)840-6468
Fermilab  ComputingDivision/LCSI/CSI DSS Group
__________________________________________________