cam@SATURN.ACC.COM (Chris Markle acc_gnsc) (12/18/89)
Folks, How should FTP server that is receiving data (eg. STOR, STOU) close the data connection in response to a permanent I/O error? Let me outline a scenario... An FTP client initiates a STOR to our server and begins to send 100 megabytes. The data set that is the STOR target is one measly disk track, so we have an "out of space condition". We send the apropriate 4xx response over the control connection, but then what? Our current scheme is issue a non-abortive close of the data connection. The problem with this is that the remote end keeps sending the whole 100 MB which we are now just throwing away. You might say "well just issue an abortive close (ie. TCP RST)" but that seems to cause certain clients to close the control connection as well! (One of these clients is 4.3 BSD ftp which we definitely need to work with). Are clients that close the control connection when the data connection is reset broken? How should this situation be handled between FTP servers and clients? Chris Markle ACC (Advanced Computer Communications) cam@saturn.acc.com (301)290-8100