-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 James Gray wrote: > 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??
I haven't come across this before, but if I was trying to figure out what's going on, I'd probably: 1. tail /var/log/messages, /var/log/secure and /var/log/sudo.log during a sudo attempt 2. check that you've installed the latest version of sudo available (there's been plenty of times that stuff is broken in rhel until you do an up2date). 3. Make 100% sure that the syntax in your /etc/sudoers file is correct. 4. Perhaps do a complete removal of sudo and re-install again? - -- dave. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEVsKChPPdWeHRgaoRAm2aAJ9l2Fa2M4t2dpetLzVtvzzWpoKNQQCgzk1g yVbRgwJ9CCfLoKc0aXCQt3U= =uZ91 -----END 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
