NetNameResolver on Linux always returns #(0 0 0 0)
Dino
deanmao at cc.gatech.edu
Tue Feb 8 06:12:28 UTC 2000
John Clonts wrote:
>
> Bijan Parsia wrote:
> >
> > At 11:44 PM -0500 2/7/00, John Clonts wrote:
> >
> > >On Squeak 2.7. I don't have any other name-resolving problems on this
> > >machine....
> > >
> > >Any Ideas?
> > >
> >
> > Did you do ye old "Socket initializeNetwork."? If not, then the
> > NetNameResovler won't work properly. I notice on my (Mac) machine that
> > calling #initializeNetwork *after* trying to resolve something tends to
> > leave the resovler scrambled (i.e., I have to restart the image). (Well, I
> > don't know that I *have* to, but it seems to be the simplest thing to do,
> > and it works :))
> >
> > Cheers,
> > Bijan.
>
> Mmm, and that sounded so promising, too...
>
> No, I did that on a clean image, same thing
> Socket initializeNetwork.
> NetNameResolver addressForName: 'mastnet.net' ==> #(0 0 0 0).
Hmm... interesting. I just had lots of NetNameResolver problems myself
since I have multiple network cards in my computer. But for me,
NetNameResolver addressForName: 'mastnet.net' ==> #(206 65 193 1)
Seems like it worked for me... very odd though.
Dino
More information about the Squeak-dev
mailing list
|