-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Please login via the console as root and execute those commands. Also show what "id" shows for the root user. Executing the following as root will probably fix your problem. # semanage login -m -s unconfined_u __default__ On 01/11/2011 07:00 AM, Walt wrote:
Ran those commands as user. Walt
On 01/10/2011 11:05 AM, Daniel J Walsh wrote:
On 01/10/2011 09:35 AM, Walt wrote:
semanage login -l and semanage user -l gives: /usr/sbin/semanage: SELinux policy is not managed or store cannot be accessed. I don't know how this came about either. I think it started after a package update, but I'm not sure. Thanks! Walt
Did you do these commands as root?
On 01/10/2011 09:23 AM, Daniel J Walsh wrote:
On 01/10/2011 09:13 AM, Walt wrote:
id gives: uid=500(walt) gid=500(walt) groups=500(walt) context=user_u:user_r:user_t:s0 Thanks! Walt
user_t is a confined user, it is not allowed to do root activity. Not sure how you got this setup, you probably want to run with unconfined_t.
Please attach the output of # semanage login -l # semanage user -l
If logging in as root gets you a user that is running as user_t, then you might have to boot the machine in permissive mode.
On 01/10/2011 08:30 AM, Daniel J Walsh wrote:
On 01/09/2011 04:39 PM, Walt wrote: > Thank you all for the help. > I can access a shell from ctrl alt F2 and can use it to do the admin > work I need to with this system. > find / -name su > gives me a lot of 'permission denied' for many of the directories. > which su > gives me /usr/bin/which: no su in > (/usr/lib/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/lib/alliance/bin:/usr/libexec/sdcc:/home/walt/bin:/usr/lib/alliance/bin:/usr/libexec/sdcc)
> But the part that bothers me the most is when I want to run yumex or > some other GUI app that requires root privileges, I can't. > Thanks again!! > Walt
These sound like SELinux issues. What does
# id
Show?
> On 01/06/2011 10:18 AM, Tal Cohen wrote: >> Does "which su" find su in your path?
>> If not, try "find / -name su" to find out where it is on your system.
>> ----- Original Message ----- >> From: "Eric J. Martin" <eric.joshua.martin@gmail.com> >> To: "Worcester Linux Users Group" <wlug@mail.wlug.org> >> Sent: Thursday, January 06, 2011 9:04 AM >> Subject: Re: [Wlug] problems with su (WAS: help)
>>> _______________________________________________ >>> Wlug mailing list >>> Wlug@mail.wlug.org >>> http://mail.wlug.org/mailman/listinfo/wlug >>> >> _______________________________________________ >> Wlug mailing list >> Wlug@mail.wlug.org >> http://mail.wlug.org/mailman/listinfo/wlug
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
Please log in as roo -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAk0sXUUACgkQrlYvE4MpobN2nwCeNZ1TJNIIbgPa3I+3sbhsRuEk RVgAnih+oQy2XPwmVO9sMfShJ35zIh+Q =2ksp -----END PGP SIGNATURE-----