Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!ames!ucbcad!ucbvax!HUCSC.HARVARD.EDU!stew%lhasa
From: stew%lhasa@HUCSC.HARVARD.EDU.UUCP
Newsgroups: mod.computers.vax
Subject: Re: Login command files
Message-ID: <8702122140.AA05269@ucbvax.Berkeley.EDU>
Date: Thu, 12-Feb-87 11:17:46 EST
Article-I.D.: ucbvax.8702122140.AA05269
Posted: Thu Feb 12 11:17:46 1987
Date-Received: Fri, 13-Feb-87 22:14:54 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 12
Approved: info-vax@sri-kl.arpa

Regarding SYS$SYLOGIN and login command procedures:

SYS$SYLOGIN should be used for things you want to require that all users
execute every time they log in.  LGICMD should be used for things which
you supply for the user's convenience.  The former should be as short
as possible, so that a user that wants to get in to do something quick
can do so by logging in with USERNAME/NOCOM.  In this case, SYS$SYLOGIN
is executed, but the LGICMD isn't.  That's the major difference.

On our system, SYS$SYLOGIN is defined, and LGICMD points to another
file in SYS$MANAGER: which sets up symbols and terminal types and
so forth, and then executes SYS$LOGIN:LOGIN.COM (if it exists).