Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!sri-unix!sri-spam!ames!ucbcad!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU.UUCP
Newsgroups: mod.computers.vax
Subject: Re: RE:TDUGGAN@WASH-VAX.BBN.COM
Message-ID: <870212125545.05f@CitHex.Caltech.Edu>
Date: Thu, 12-Feb-87 15:55:45 EST
Article-I.D.: CitHex.870212125545.05f
Posted: Thu Feb 12 15:55:45 1987
Date-Received: Fri, 13-Feb-87 23:10:01 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 24
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?

Using the logical name SYS$SYLOGIN:  forces all  logins  to  use  the  command
procedure  so  defined,  regardless  of the /COM= and /NOCOM qualifiers to the
username, whereas either of these qualifiers  may  be  used  to  override  the
default LGICMD specified in SYSUAF (unless appropriate flags are set).