[mod.computers.vax] System log in command procedures.

RBrooks@MIT-MULTICS.ARPA.UUCP (02/12/87)

To my knowledge ther e is one fairly big difference between the two
methods.

If you define the logical name SYS$SYLOGIN all logins go through the
command procedure whether they want to or not.  If you define the login
command procedure by defining LGICMD in SYSUAF.DAT then the user can log
in with the /NOCOMMAND switch after his user name and the procedure will
not be executed.

One could of course make the account captive and define LGICMD but to do
it correctly would be a lot of work.

Forcing users to go through the SYS$SYLOGIN command string can also be
very useful for many reasons.  I have used it before to keep track of
DIALUP logins an REMOTE access to VAXen.