Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: How about this for logins?
Message-ID: <8985@ucbvax.ARPA>
Date: Thu, 11-Jul-85 17:12:53 EDT
Article-I.D.: ucbvax.8985
Posted: Thu Jul 11 17:12:53 1985
Date-Received: Sat, 13-Jul-85 09:01:44 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 23

From: Gail Rubin 

If what you actually want is to not have the OUTPUT from the system login
show up in their log files, but you don't mind if the EXECUTION happens,
you could put:

$  oldverify = f$verify(0)

at the beginning of the system login command file which turns off verify
(which is normally off when you start an interactive job and on for a batch
job) and then at the end of your system login command file put:

$  junk = f$verify(oldverify)

to put it back to the state it was in. That's what we do here.

For details on what login command files get executed when see page 5-10 of
the Guide to VAX/VMS System Management and Daily Operations (VMS 4.0; one
of the smaller manuals) - I think you will find that there are plenty of
options. If you don't have that book, let me know and I'll summarize it.

-- Gail Rubin
(grubin@bbn-spca or @bbn-unix)