:
#
# .rkshrc	-- Commands executed by each Restricted Korn shell at startup
#
#	@(#) rkshrc 1.1 90/03/13 
#
# Copyright (c) 1990, The Santa Cruz Operation, Inc.
# All rights reserved.
#
# This Module contains Proprietary Information of the Santa Cruz
# Operation, Inc., and should be treated as Confidential. 
#
#	The Restricted Korn Shell is identical to the Standard
#	Korn Shell except that the user may _not_:
#	  (1)  cd,
#	  (2)  Set PATH, SHELL, or ENV,
#	  (3)  Use command names containing slashs ("/"), and
#	  (4)  Re-direct output with ">", ">|", "<>", or ">>".
#	Any shell script, however, is run by the unrestricted Korn
#	Shell -- which means that the user should not have both write
#	and execute permission for any directory listed in PATH.
#
#		NOTE TO THE SYSTEM ADMINISTRATOR
#		--------------------------------
# Each Restricted Korn Shell user should have a customized version
# of this script.  This is the script named by the ENV environment
# variable, which should be initialized in the user's ".profile".
# Normally, this script is installed in the user's home directory
# as ".rkshrc", and so ENV would be set as:
#	ENV=$HOME/.rkshrc
# Note that since the Korn shell does parameter substitution on the
# definition of ENV before reading the so-named file, the value of
# ENV should not contain any unescaped "$"s.
#
# The required customizations depend on the what the user is allowed
# to do (or should be prevented from doing).  Typically, the user's
# private $HOME/bin should contain only the commands the user is
# allowed to execute, and the PATH environment variable should be
# set to _only_ search the user's $HOME/bin directory.  Futhermore,
# the user's current working directory should be not be the same
# as their home, and the user should not have both write and execute
# permissions in that directory.
#
#	Please examine, edit, and test each user's customized
#	copy of this script before allowing that user to log
#	onto the system.
#
# CAUTION - When this script is executed (each time a Korn shell,
#	restricted or not, starts up), the restrictions are not
#	yet in effect.  The restrictions start to apply as soon
#	as this script is done executing.  (If the user tries
#	to interrupt either script while it is executing, 
#	the Restricted Korn Shell exits.)
#
#

# If there is no VISUAL or EDITOR to deduce the desired edit
#  mode from, assume vi(C)-style command line editting.
if [ -z "$VISUAL" -a -z "$EDITOR" ]; then
	set -o vi
fi
