Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!cbatt!ucbvax!nuhub.acs.northeastern.edu!JOHNSON From: JOHNSON@nuhub.acs.northeastern.edu.UUCP Newsgroups: mod.computers.vax Subject: vms batch crash and spying. Message-ID: <8612101326.AA07941@ucbvax.Berkeley.EDU> Date: Fri, 5-Dec-86 17:13:00 EST Article-I.D.: ucbvax.8612101326.AA07941 Posted: Fri Dec 5 17:13:00 1986 Date-Received: Sun, 14-Dec-86 00:53:34 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 37 Approved: info-vax@sri-kl.arpa >Hello vax world, do any one have any idea how to: >1. save the context of batch job so it can be > saved before system shutdown and rerun when > system is up again. Please note that we want to > run a long (and large) program that take days > to complete and so restart points in the > command procedure are no good for us. Unless DEC came up with it and didn't tell anyone, no there isn't. Many users have been screaming for checkpointing for years. The closest behavior is RESTARTing a batch job from a known point. This is totally useless for a single long program. Of course, you can always write your program so it checkpoints itself ... (more work) >2. Is there any way to monitor any particular user > that we suspect him for naughty behavior. We would > love to have a record of his session without his > knowledge. (set host 0 is no good he is to smart) There are products out that do this. We have one from Clyde Software and we have used it for just this purpose. Worked too. We caught the guy and had him flogged, drawn and quarted. US mail: Chris Johnson Academic Computer Services Northeastern University 39RI 360 Huntington Ave. Boston, MA. U.S.A. 02115 AT&T: (617) 437-2335 CSNET: johnson@nuhub.acs.northeastern.edu ARPANET: johnson%nuhub.acs.northeastern.edu@relay.cs.net "What's reality anyway? Nothin' but a collective hunch." Lily Tomlin