On Tue, 2 May 2006 09:18 am, James Gray wrote: > Hi All, > > Seems my shiny new RHEL4 (update 3)[1] wont allow any of my configured > "sudoers" to actually use sudo. What I have is everyone in the "wheel" > group configured to complete access to sudo with their user password. > However, when any of us actually run sudo, the following sequence allways > occurs: 1. we are prompted for our user password > 2. enter the password > 3. sudo goes to 100% CPU and never returns. > 4. Switch to another terminal, log in as root and "killall -TERM sudo". > 5. Terminal with the attempted sudo now says that sudo was killed. > > Anyone else seen this? There's nothing in the logs (well, I haven't found > anything, put it that way), so I'm flying blind. Ideas??
For the record, RHEL4 stores the sudo logs in /var/log/secure. The solution - my user account wasn't a member of the "wheel" group which is the only group (currently) with sudo privs. Once I added myself to the group, logged out and back in again, sudo is working as advertised :) Yay. Thanks to David Gillies, and J amie Wilkinson for the help just the same. Cheers, James -- "Are [Linux users] lemmings collectively jumping off of the cliff of reliable, well-engineered commercial software?" (By Matt Welsh)
pgp06KLEL3dWT.pgp
Description: PGP signature
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
