HP3000-L Archives

April 1996, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Steve Dirickson b894 WestWin <[log in to unmask]>
Reply To:
Steve Dirickson b894 WestWin <[log in to unmask]>
Date:
Wed, 3 Apr 1996 17:04:00 P
Content-Type:
text/plain
Parts/Attachments:
text/plain (17 lines)
<<The fix was ugly, we set the NETIPC timer to infinite in the FTP/iX
client and server.  SR 5003233213.  This addressed the internet timeout
problem, but left us with servers which did not go away if the network
dropped until the Connection Assurance timer expired...>>
 
Always "did not go away"? Or only under specific conditions? I'd think
you'd get errors like 64 (remote abort), 67 (connection failure) or 68
(graceful release) most of the time.
 
Of course, when it does happen, it's not pleasant. A "better" solution
might to keep the 60-second timeout, but run it in a loop controlled by a
user-settable (via QUOTE, or something else, or both) counter that
defaults to something comparable to the CA timeout.
 
Steve Dirickson         WestWin Consulting
(360) 598-6111  [log in to unmask]

ATOM RSS1 RSS2