ralph@nastassia.laas.fr (Ralph P. Sobek) (05/18/89)
I am unable to delete a closed stream which is listed by OPENP as #<Closed stream on {MIRO}<RIA>miro.../56,1610. The suggestions of using the INSPECTor or CLOSEF of OPENP don't work, so FILEWATCH (Lyric version) does not want to come up. Any ideas, Ralph P. Sobek Disclaimer: The above ruminations are my own. ralph@laas.laas.fr Addresses are ordered by importance. ralph@laas.uucp, or ...!uunet!mcvax!laas!ralph If all else fails, try: SOBEK@FRMOP11.BITNET sobek@eclair.Berkeley.EDU
welch@CIS.OHIO-STATE.EDU (Arun Welch) (05/19/89)
I've seen this before when debugging TCPFTP, so I'm gonna assume that it's a TCP stream. What's happening is that the stream has gotten munged to the point where the BEFORECLOSE prop, \TCP.READ.UNTIL.EOF, can't execute for some reason or another, so when you try and close it, that function dies, and you're left with this stream hanging around. Setting the prop to NIL should allow you to close it. The function's only in there 'cause some FTP servers don't allow you to abort a read in the middle of a file, and so you have to read to the end before you break the connection. If MIRO's a BSD or TOPS-20 host, you're safe. If you're not sure, telnet to the FTP port and do a HELP, and if it supports ABOR you're safe. ...arun (ex)Envos TCP Support (I took it over from Frank :-).