<br><br><div class="gmail_quote">2009/12/6 Wolfgang S. Rupprecht <span dir="ltr"><<a href="mailto:wolfgang.rupprecht@gmail.com">wolfgang.rupprecht@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
Roberto Ragusa <<a href="mailto:mail@robertoragusa.it">mail@robertoragusa.it</a>> writes:<br>
> Joachim Backes wrote:<br>
>> On 12/05/2009 01:32 PM, Hiisi wrote:<br>
>>> 2009/12/5 Wolfgang S. Rupprecht<<a href="mailto:wolfgang.rupprecht@gmail.com">wolfgang.rupprecht@gmail.com</a>>:<br>
>>>><br>
>>>> As of a day or so ago "su" has started hanging for 30 seconds. So has<br>
>>>> the lock screen. Jiggling the mouse unblanks the monitor and shows me<br>
>>>> the backdrop picture but the password entry box doesn't appear for 30<br>
>>>> seconds. I don't believe I mucked with anything PAM related, but there<br>
>>>> were a few yum updates in the last few days. Is anyone else seeing<br>
>>>> this?<br>
</div><div class="im">>>> I have the same problem for a couple of month (don't remember exactly<br>
>>> how long it is) on my F11 (32 bit). I've asked it already on this list<br>
>>> but had no response.<br>
>> I had similar problems in the past (with sudo / not su), and the reason<br>
>> was an error in the network controls (I tried to change the hostname by<br>
>> editing /etc/sysconfig/network, but forgot all other places to edit).<br>
> This kind of delays are often DNS timeouts.<br>
> If the network configuration is wrong, trivial things like printing<br>
> "last unsuccessfull login on 02-12-2009 from <a href="http://abcd.example.com" target="_blank">abcd.example.com</a>"<br>
> take 15-30-60 seconds.<br>
<br>
</div>Hmm. No 6 hours after posting this, the problem cleared up. I'm temped<br>
to finger the selinux-targeted-policy that I installed from<br>
updates-testing for clearing things up. That was the only change in the<br>
intervening time.<br></blockquote><div><br></div><div>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.</div><div><br></div>
<div><br></div><div>Steven</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
As to the DNS issue. Bingo. /etc/resolv.conf to be exact still had an<br>
old IPv6 address in it. Oops. I thought that the resolver should<br>
failover and stay locked to the best dns server fast than 30 seconds. I<br>
see I'm going to have to figure out why it took so long. Thanks for<br>
reminding me to double check.<br>
<br>
search <a href="http://wsrcc.com" target="_blank">wsrcc.com</a><br>
nameserver 2001:5a8:4:7d0::1<br>
nameserver 192.83.197.1<br>
nameserver ::1<br>
nameserver 127.0.0.1<br>
<div class="im"><br>
-wolfgang<br>
--<br>
Wolfgang S. Rupprecht<br>
If the airwaves belong to the public why does the public only get 3<br>
non-overlapping WIFI channels?<br>
<br>
</div><div><div></div><div class="h5">--<br>
fedora-list mailing list<br>
<a href="mailto:fedora-list@redhat.com">fedora-list@redhat.com</a><br>
To unsubscribe: <a href="https://www.redhat.com/mailman/listinfo/fedora-list" target="_blank">https://www.redhat.com/mailman/listinfo/fedora-list</a><br>
Guidelines: <a href="http://fedoraproject.org/wiki/Communicate/MailingListGuidelines" target="_blank">http://fedoraproject.org/wiki/Communicate/MailingListGuidelines</a><br>
</div></div></blockquote></div><br>