On Mon, Aug 16, 2004 at 01:57:00PM -0400, jludwig wrote:
> On Mon, 2004-08-16 at 12:32, François Patte wrote:
> > Selon Mike Klinke <lsomike@xxxxxxxxxx>:
> >
> > > On Monday 16 August 2004 07:00, François Patte wrote:
> > >
> > > > If I use the command
> > > >
> > > > yum update
> > > >
> > > > as a normal user, it works untill I have to be root to perform the
> > > > operation. If do the same as root yum hangs and I have to kill the
> > > > process...
> > > >
> > > > Who cold give me some information?
> > >
> > > How are you getting "root"? Are you using "su"? If so try either
> > > logging in as root at the initial login or use "su -" to be sure you
> > > have set up root's environment and see if that makes a difference.
> >
> > I use "su -", but the problem is the same with "su" only
Can you also tell us what "id" returns?
With SELinux active you can see differences in the context that
SELinux enforces. i.e. It might be more than $PATH,
Thus...
$ su -
# id
uid=0(root) gid=0(root) groups=0(root).... context=mitch12:staff_r:staff_t
# newrole -r sysadm_r
Authenticating mitch12.
Password:
# id
uid=0(root) gid=0(root) groups=0(root).... context=mitch12:sysadm_r:sysadm_t
It may be that your yum.conf has an effective long list of hosts and
is searching them all to resolve package interactions. You can check
this by watching you network traffic with a packet sniffer like
"tehereal" or "ethereal".
--
T o m M i t c h e l l
Just say no to 74LS73 in 2004
