| socket issue [message #52605] |
Thu, 22 February 2007 01:30  |
Bringfried Stecklum
Messages: 75
Registered: January 1996
|
Member |
|
|
One of my programs retrieves data over the web using the socket
procedure. It also runs on the laptop which has different network
settings depending on where I am. Usually the IDL session is kept
running when hibernating/resuming the system. In this case I noticed
that socket does not become aware of the change in the network settings
and fails
% SOCKET: Unable to lookup host. Unit: 1, File: remotehost
Of course remotehost can be reached. So it seems that the network
configuration is fixed upon IDL startup, and not dynamically updated.
regards,
Bringfried Stecklum
|
|
|
|
| Re: socket issue [message #52716 is a reply to message #52605] |
Mon, 26 February 2007 05:07  |
Bringfried Stecklum
Messages: 75
Registered: January 1996
|
Member |
|
|
Dear Nigel,
I am aware of the cause for the error. I also wrote that remotehost can
be resolved and reached ouside of IDL. My point was that IDL could be a
bit more flexible by checking whether the DNS configuration found at
startup is still valid when socket is being called. People move around
with laptops these days and DNS service can change quickly.
regards,
Bringfried
Nigel Wade wrote:
> Bringfried Stecklum wrote:
>
>> One of my programs retrieves data over the web using the socket
>> procedure. It also runs on the laptop which has different network
>> settings depending on where I am. Usually the IDL session is kept
>> running when hibernating/resuming the system. In this case I noticed
>> that socket does not become aware of the change in the network settings
>> and fails
>>
>> % SOCKET: Unable to lookup host. Unit: 1, File: remotehost
>>
>> Of course remotehost can be reached. So it seems that the network
>> configuration is fixed upon IDL startup, and not dynamically updated.
>>
>> regards,
>>
>> Bringfried Stecklum
>
> "Unable to lookup host." looks like a failure in DNS hostname resolution. What
> host is it trying to connect to, and can you resolve that hostname outside of
> IDL?
>
|
|
|
|
| Re: socket issue [message #52739 is a reply to message #52605] |
Fri, 23 February 2007 02:36 |
Nigel Wade
Messages: 286
Registered: March 1998
|
Senior Member |
|
|
Bringfried Stecklum wrote:
> One of my programs retrieves data over the web using the socket
> procedure. It also runs on the laptop which has different network
> settings depending on where I am. Usually the IDL session is kept
> running when hibernating/resuming the system. In this case I noticed
> that socket does not become aware of the change in the network settings
> and fails
>
> % SOCKET: Unable to lookup host. Unit: 1, File: remotehost
>
> Of course remotehost can be reached. So it seems that the network
> configuration is fixed upon IDL startup, and not dynamically updated.
>
> regards,
>
> Bringfried Stecklum
"Unable to lookup host." looks like a failure in DNS hostname resolution. What
host is it trying to connect to, and can you resolve that hostname outside of
IDL?
--
Nigel Wade, System Administrator, Space Plasma Physics Group,
University of Leicester, Leicester, LE1 7RH, UK
E-mail : nmw@ion.le.ac.uk
Phone : +44 (0)116 2523548, Fax : +44 (0)116 2523555
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
