su hangs for 30 seconds

[steven bellens]

2009/12/6 Wolfgang S. Rupprecht <wolfgang.rupprecht at gmail.com>

>
> Roberto Ragusa <mail at robertoragusa.it> writes:
> > Joachim Backes wrote:
> >> On 12/05/2009 01:32 PM, Hiisi wrote:
> >>> 2009/12/5 Wolfgang S. Rupprecht<wolfgang.rupprecht at gmail.com>:
> >>>>
> >>>> As of a day or so ago "su" has started hanging for 30 seconds.  So has
> >>>> the lock screen.  Jiggling the mouse unblanks the monitor and shows me
> >>>> the backdrop picture but the password entry box doesn't appear for 30
> >>>> seconds.  I don't believe I mucked with anything PAM related, but
> there
> >>>> were a few yum updates in the last few days.  Is anyone else seeing
> >>>> this?
> >>> I have the same problem for a couple of month (don't remember exactly
> >>> how long it is) on my F11 (32 bit). I've asked it already on this list
> >>> but had no response.
> >> I had similar problems in the past (with sudo / not su), and the reason
> >> was an error in the network controls (I tried to change the hostname by
> >> editing /etc/sysconfig/network, but forgot all other places to edit).
> > This kind of delays are often DNS timeouts.
> > If the network configuration is wrong, trivial things like printing
> > "last unsuccessfull login on 02-12-2009 from abcd.example.com"
> > take 15-30-60 seconds.
>
> Hmm.  No 6 hours after posting this, the problem cleared up.  I'm temped
> to finger the selinux-targeted-policy that I installed from
> updates-testing for clearing things up.  That was the only change in the
> intervening time.
>

I had the same problem with sudo hanging and I can confirm that updating the
selinux-policy-targeted using the test repositories solves the problem.


Steven


>
> As to the DNS issue.  Bingo.  /etc/resolv.conf to be exact still had an
> old IPv6 address in it.  Oops.  I thought that the resolver should
> failover and stay locked to the best dns server fast than 30 seconds.  I
> see I'm going to have to figure out why it took so long.  Thanks for
> reminding me to double check.
>
>     search wsrcc.com
>     nameserver 2001:5a8:4:7d0::1
>     nameserver 192.83.197.1
>     nameserver ::1
>     nameserver 127.0.0.1
>
> -wolfgang
> --
> Wolfgang S. Rupprecht
> If the airwaves belong to the public why does the public only get 3
> non-overlapping WIFI channels?
>
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines:
> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20091207/9b1b3031/attachment-0001.htm>