mike%udel-oitvax.arpa@UDEL.EDU.UUCP (02/13/87)
...
Reply-To: Greg Hamm <hamm%waks.rutgers.edu@UDEL.EDU>
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.
>>> If you do not enter anything, it will default to login.com.
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.
>>> Using this method will allow users to not execute the system login
>>> file if they log in with /NOCOMMAND. Could be a problem if you
>>> have special checks in the system login file.
>>>
>>> I would suggest just not defining the user's login file through
>>> authorize, and defining SYS$SYLOGIN. Then, just have SYS$SYLOGIN
>>> exit and let LOGINOUT deal with the user's login file.
...
Greg Hamm
Rutgers Molecular Biology Computing Lab
hamm@biovax.bitnet
hamm@waks.rutgers.edu
>>> Mike Porter (mike@udel-oitvax.udel.edu)
>>> (mike%udel-oitvax@udel.arpa)
------