Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!ames!ucbcad!ucbvax!WAKS.RUTGERS.EDU!hamm
From: hamm@WAKS.RUTGERS.EDU.UUCP
Newsgroups: mod.computers.vax
Subject: Login command files
Message-ID: <8702121745.AA00811@ucbvax.Berkeley.EDU>
Date: Wed, 11-Feb-87 21:11:00 EST
Article-I.D.: ucbvax.8702121745.AA00811
Posted: Wed Feb 11 21:11:00 1987
Date-Received: Fri, 13-Feb-87 21:48:10 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: "Greg Hamm" <hamm@waks.rutgers.edu>
Organization: The ARPA Internet
Lines: 26
Approved: info-vax@sri-kl.arpa

I've come across two ways of handling login command files, and wonder whether
anyone knows a reason to prefer (or abhor) one or the other:

    1. SYS$SYLOGIN is defined to point to a system-wide login command
    procedure, which is thus invoked for all processes.  LGICMD (in the
    UAF) for each user is defined to point to the file LOGIN.COM in
    that user's home directory.

    2. SYS$SYLOGIN is undefined, but LGICMD for *all* users points to
    the system-wide login command procedure.  A line late in this command
    procedure checks to see if a user LOGIN.COM exists, and, if so,
    executes it.

As far as I can tell, these two methods are superficially equivalent.  Each
results in both levels of command procedure being executed in the proper
order, and neither chokes if no user LOGIN.COM is present.

Comments?

Greg Hamm
Rutgers Molecular Biology Computing Lab

hamm@biovax.bitnet
hamm@waks.rutgers.edu

------