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: Re: sys vs batch jobs
Message-ID: <9033@ucbvax.ARPA>
Date: Fri, 12-Jul-85 23:06:28 EDT
Article-I.D.: ucbvax.9033
Posted: Fri Jul 12 23:06:28 1985
Date-Received: Sat, 13-Jul-85 16:53:09 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 23

From: Kathy Minnich 


 >  This would mean that ALL batch jobs on your system would not
 >  execute the system login; that might not be what you wanted.

that sounds fine.  i just thought that it would be nice if the system
login setup could be transparent to the user and not muddy up their
log files which are created by "submit"  (something similar to "csh -f"
in UNIX).  i wasn't thinking about any specific programs or batch jobs.

one other thing:  do you know if the login command procedure is read
in by "submit" when it's set in the sysuaf LGICMD field?  i haven't
tried that yet, but i didn't like the idea of not executing the user's
login.com file if there was one (since the login procedure executes 
either the one in LGICMD or the user's login.com).  i know that you
could hack the LGICMD procedure up to look for a user's login.com file,
then execute it if it's there, but .... i just wanted to know if there 
was an easy way around it all.

kathy

PS:  i got your other note, too, but replied to the first one.