🚀 go-pugleaf

In article <1992Jul23.100315.13912@aston.ac.uk> stopsdj@uhura.aston.ac.uk (David Stops) writes:
>Is there a simple way of preventing people logging on to a DYNIX/ptx system.
>In DYNIX this can be achieved by creating /etc/nologin, if this file exists
>when a user attempts to log in, login prints its contents and exits.  Is there
>an equivalent in DYNIX/ptx ?

Unfortunately, there is no equivalent in PTX.

We're going to use a different approach, and create a "quiescent" mode on
our PTX systems whereby everything is up and running, but only
administrators can log in.  Start by adding code to /etc/profile...
-- 

Pete Gregory       |  Internet: pete@wvus.org
UNIX SA            |  Bangpath: ames!elroy!wvus!pete
World Vision U.S.  |  Slowpath: 919 W. Huntington Dr., Monrovia, CA 91016

stopsdj@uhura.aston.ac.uk (David Stops) writes:
: Is there a simple way of preventing people logging on to a DYNIX/ptx system.
: In DYNIX this can be achieved by creating /etc/nologin, if this file exists
: when a user attempts to log in, login prints its contents and exits.  Is there
: an equivalent in DYNIX/ptx ?

No, there is no equivalent version of the /etc/nologin functionality in 
Dynix/PTX  (this is not a Sequent thing, more a SysV/POSIX thing if memory
serves me right).

It can be simulated but you need to "hack" /etc/profile with something like:

if [ $LOGNAME != "root" ]; then
    echo "Logins refused at this time"
    exec tput clear
fi

This is from memory so you might need to explicitly state where tput is
(that's the trouble using two o/s Dynix[bsd] and Dynix/PTX[att]).

This will probably fail though for people who just "su" [$LOGNAME doesn't get
altered!]


Cheers,

Jayce.

--

"Nudists only have one button on their suits!"

Internet: aangel@sequent.co.uk			Sequent Computer Systems
	  cs89jmb@brunel.ac.uk			UK Customer Support
						Chertsey, Surrey KT16 9HB