[Tcl-bugs] [ tcl-Bugs-533301 ] fconfigure -peername very slow

[SourceForge.net <no...@so...>]

Bugs item #533301, was opened at 2002-03-21 21:01
Message generated for change (Comment added) made by cdclercq
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=533301&group_id=10894

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: 24. Channel Commands
Group: obsolete: 8.3.4
Status: Open
Resolution: None
Priority: 5
Submitted By: robert karen (rkaren)
Assigned to: Andreas Kupries (andreas_kupries)
Summary: fconfigure -peername very slow

Initial Comment:
set socket [socket $host $port]
fconfigure -peername ;# or fconfigure
# long delay, network specific- 5 seconds on mine much longer (minutes) on others.

I also tried this with ver.8.0.

----------------------------------------------------------------------

Comment By: Christophe De Clercq (cdclercq)
Date: 2005-09-19 07:45

Message:
Logged In: YES 
user_id=617750

When using ActiveTcl ftp package I have exactly the same thing.
But only on Solaris (not on Windows).

I takes sometimes more than a minut (sometimes a timeout) to
do a set peer [fconfigure $ftp(CtrlSock) -peername].
* We only have this when starting on Solaris connecting
to Windows via a Fortigate 200 Antivirus Appl. and a
firewall.





----------------------------------------------------------------------

Comment By: Donal K. Fellows (dkf)
Date: 2002-04-08 09:22

Message:
Logged In: YES 
user_id=79902

There's no parameter for timeout on standard getXbyY calls
(nor any guarantee on what underlying lookup mechanism will
be used; I know of systems that use host files, DNS and
NIS+, and could well believe it if others used LDAP or
something equally horrific) and they are all synchronous.

This sucks, but it is not our fault. :^(

Suggested fix: helper processes/threads, perhaps with a
clever cache (with timed expiry) as well.  There are a
number of interesting issues with how you bind this into Tcl
though, particularly in relation to async socket handling
and whether people should be penalized for information they
don't look at...

----------------------------------------------------------------------

Comment By: David Gravereaux (davygrvy)
Date: 2002-04-07 04:50

Message:
Logged In: YES 
user_id=7549

That might be a global setting on the machine regarding the 
sockets implimentation for getXbyY().  Off-hand, I don't 
know of a localized way to set a getXbyY timeout.  Then 
again, it's been ages since I've done any sockets 
programming.

----------------------------------------------------------------------

Comment By: robert karen (rkaren)
Date: 2002-03-31 01:31

Message:
Logged In: YES 
user_id=489489

Yes, I figured that, but it would be nice if it timed out.
I sent code to someone that slowed a 30 second process
down to 20 minutes because of some diagnostic messages
that were printing [fconfigure $sock] results.

RK

----------------------------------------------------------------------

Comment By: David Gravereaux (davygrvy)
Date: 2002-03-26 09:53

Message:
Logged In: YES 
user_id=7549

It's related to DNS reverse lookup, I think.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=533301&group_id=10894