home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky vmsnet.sysmgt:452 vmsnet.networks.misc:151 comp.os.vms:22094
- Path: sparky!uunet!destroyer!cs.ubc.ca!van-bc!mdavcr!jal
- From: jal@mdavcr.mda.ca (John Lloyd)
- Newsgroups: vmsnet.sysmgt,vmsnet.networks.misc,comp.os.vms
- Subject: Re: Lost LAT sessions
- Message-ID: <3988@mdavcr.mda.ca>
- Date: 28 Jan 93 06:26:53 GMT
- References: <L28ZXB1w165w@jeslacs.wimsey.bc.ca>
- Followup-To: vmsnet.sysmgt
- Organization: MacDonald Dettwiler, 13800 Commerce Parkway, Richmond, BC, Canada V6V 2J3
- Lines: 9
-
- We can attest to Lotus for VMS having (almost) the same symptoms.
- However, in our situation finding the LTA device (and the process) is
- easy.
-
- One simple fix: set a cpu-time limit on the users; that might kill the
- process even in it's LAT-bound state.
-
-
- John nnn
-