Hello all-
Somewhere last night, my Squeak's networking stopped working. Socket initializeNetwork doesn't remedy things. I've narrowed it down to the name resolution- connecting to IPs works fine.
If I eval: NetNameResolver nameForAddress: 'www.squeak.org' timeout: 10
It just sits there, hung, not timing out after 10 seconds. When I Cmd-. it, the topmost method called is Semaphore>>#critical:IfError: called by NetNameResolver class>>#nameForAddress:timeout:.
I'm running 3.2g-4827 on Mac OS X w/ the 3.2.6B8 Carbon VM. Nothing has changed in my OS X network settings, no problem resoving names in 'native' OS X apps.
Any ideas?
Regards, Aaron
Aaron Reichow :: UMD ACM Pres :: http://www.d.umn.edu/~reic0024/ "the only difference it makes if some dust on the clay" :: atmosphere
Aaron J Reichow wrote:
It just sits there, hung, not timing out after 10 seconds. When I Cmd-. it, the topmost method called is Semaphore>>#critical:IfError: called by NetNameResolver class>>#nameForAddress:timeout:.
It sounds like the Semaphore is still locked. Did you abort a name lookup earlier and the unwind didn't reset the Semaphore? Just an idea...
Michael
Not that I know of, but perhaps I did so accidentally. How could I remedy this?
Regards, Aaron
Aaron Reichow :: UMD ACM Pres :: http://www.d.umn.edu/~reic0024/ "life, probably the biggest word i've ever said, that says a lot, because there's a whole lot of words inside my head.." :: atmosphere
On Tue, 30 Apr 2002, Michael Rueger wrote:
Aaron J Reichow wrote:
It just sits there, hung, not timing out after 10 seconds. When I Cmd-. it, the topmost method called is Semaphore>>#critical:IfError: called by NetNameResolver class>>#nameForAddress:timeout:.
It sounds like the Semaphore is still locked. Did you abort a name lookup earlier and the unwind didn't reset the Semaphore? Just an idea...
Michael
On Tuesday 30 April 2002 01:25 pm, Aaron J Reichow wrote:
Not that I know of, but perhaps I did so accidentally. How could I remedy this?
I assume you mean to use addressForName: if you're looking up www.squeak.org.
Anyway, you can do this:
[ NetNameResolver addressForName: 'www.squeak.org' timeout: 10 ] forkAt: Processor userBackgroundPriority.
and then fire up a Process browser, select the stuck process, and signal its semaphore from the context menu.
I don't know that that will be a remedy, but you can unstick semaphores easily that way.
Most curious, that worked. There were no hung Semaphores in the Process browser before, I had checked that, to signal. But creating a new one, then signaling it worked like a charm. Thanks guys!
Regards, Aaron
Aaron Reichow :: UMD ACM Pres :: http://www.d.umn.edu/~reic0024/ "the only difference it makes if some dust on the clay" :: atmosphere
On Tue, 30 Apr 2002, Ned Konz wrote:
On Tuesday 30 April 2002 01:25 pm, Aaron J Reichow wrote:
Not that I know of, but perhaps I did so accidentally. How could I remedy this?
I assume you mean to use addressForName: if you're looking up www.squeak.org.
Anyway, you can do this:
[ NetNameResolver addressForName: 'www.squeak.org' timeout: 10 ] forkAt: Processor userBackgroundPriority.
and then fire up a Process browser, select the stuck process, and signal its semaphore from the context menu.
I don't know that that will be a remedy, but you can unstick semaphores easily that way.
-- Ned Konz http://bike-nomad.com GPG key ID: BEEA7EFE
squeak-dev@lists.squeakfoundation.org