[Info-vax] prevent user login during and after startup

[VAXman- at SendSpamHere.ORG]

In article <71208044-004c-4a80-a2b6-b9a3a11e1a5b at googlegroups.com>, Bob Gezelter <gezelter at rlgsc.com> writes:
>Vaxman,
>
>I was not suggesting "manually" starting telnet.
>
>What I would do in that situation is to add an invocation of the specific telnet startup file in the last stage of the layered products STARTUP database (using SYSMAN for the actual operation).
>
>The goal is to start telnet at a later point in the startup than when TCP/IP is started.
>
>- Bob Gezelter, http://www.rlgsc.com

I don't believe I was suggesting that you would "manually" start telnet.  I
wouldn't even suggest starting telnet at all on VMS. ;)  Use ssh.

The OP, IMHO, needs to address his system's startup procedures.  Why doesn't
everything startup or get configured during the system's startup?  Why does
he need to perform these manual "system" tasks after VMS is ready to allow 
interactive user logins? 

I only suggested the SYSUAF solution because I don't like the idea of some
SYLOGIN.COM DCL code determining who can or can not login after they *HAVE*
logged in!  LOGINOUT.EXE along with SYSUAF would have that sussed out long
before DCL ever gets mapped into the process.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.