Article View: vmsnet.sysmgt
Article #112Re: Lost LAT sessions
From: John Lloyd
Date: Thu, 28 Jan 1993 06:26
Date: Thu, 28 Jan 1993 06:26
9 lines
708 bytes
708 bytes
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
Technical Details
Message-ID:
<3988@mdavcr.mda.ca>Path:
arc1-ca.pugleaf.net!sparky!uunet!destroyer!cs.ubc.ca!van-bc!mdavcr!jalReferences:
<L28ZXB1w165w@jeslacs.wimsey.bc.ca>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!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