Path: utzoo!attcan!uunet!husc6!bbn!uwmcsd1!ig!agate!ucbvax!CITHEX.CALTECH.EDU!carl From: carl@CITHEX.CALTECH.EDU (Carl J Lydick) Newsgroups: comp.os.vms Subject: Re: Disconnect from SET HOST Message-ID: <880711111305.321f@CitHex.Caltech.Edu> Date: 11 Jul 88 18:16:38 GMT References: <880708102014.8f6@Warbucks.AI.SRI.COM> Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 16 > > A word of warning here: if you create a disconnected > > process this way then log in on the GPX from the console, it will > > offer you the chance to connect to the disconnected process. If you > > accept its offer, the system will crash (or at least it would under > > uVMS v4.4 and [I think] VWS v3.1). > > I'm sure you would find that you get better response to bugs of > this nature if you complained to your vendor instead of INFO-VAX. We > have received no reports of this problem (including from you). Apparently my message wasn't as clear as it should have been. This was a problem with VWS v3.1 running under VMS V4.4, not with the MULTINET software. It doesn't matter how you create a disconnected process, it's the attempt to connect WTAx: to VTAx: that kills the system. The problem no longer exists with VMS v4.7 and VWS v3.2.