Stupid networking question
Aaron J Reichow
reic0024 at d.umn.edu
Tue Apr 30 20:57:30 UTC 2002
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!
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
> 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
> GPG key ID: BEEA7EFE
More information about the Squeak-dev