Path: utzoo!attcan!uunet!lll-winken!sun-barr!decwrl!henry.jpl.nasa.gov!elroy.jpl.nasa.gov!hacgate!lori
From: lori@hacgate.scg.hac.com (Lori Barfield)
Newsgroups: comp.sys.apollo
Subject: Re: Shutdown question
Message-ID: <6536@hacgate.scg.hac.com>
Date: 21 Dec 89 18:14:22 GMT
References: <15111@boulder.Colorado.EDU>
Reply-To: lori@hacgate.hac.com (Lori Barfield)
Organization: Hughes Aircraft Co., El Segundo, CA
Lines: 26

In article <15111@boulder.Colorado.EDU> frederit@boulder.Colorado.EDU (FREDERICKS THOMAS M) writes:
>        [...]                  the machines can be shut down by anyone
>        at the console.  Is there a way to prevent this.  [...]

If it's that important, you might write your own DM script to mimic the
standard DM input window.  You would put user input into a buffer, then:

		sc -off
		s/ shut /msg 'Ask your local guru to shut me down'
		  ^    ^
		  |    |
You'd need to wildcard carefully around the 'shut' string or a DM command
'cv shutterbug.file' would get discombooberated.  You'd also need to KD
the dark keys on the keyboard.

If your problem is that people are shutting down or turning off a disked
node off which diskless nodes are booted, then you can put a pad or
alarm window on the disked node when the diskless ones come up.  This way,
the user on the disked node knows better than to shut down or switch off.
Another option (something I've done extensively when logged in via an SIO
line) is to pop up an alarm window when a user on the diskless node (or SIO
line) first logs in, then pop a second when s/he logs out.  Remember, you
might have to crp and start the alarm_server first if you use that method.


...lori