NIO CommKit Host Interface Installation and System Administration Manual

DK(1C) DK(1C)
E-7 CommKit Host Interface, Release 4.0
A sample which illustrates the proper setup of the .profile follows:
HOME=‘pwd‘
umask 022
PATH=$PATH:/opt/dk/bin:/bin:$HOME/bin:/usr/bin:/usr/ucb
DKEXPORT=TERM
export PATH CDPATH HOME MAIL PS1 TERM DKEXPORT
MAIL=/usr/mail/$LOGNAME
EDITOR=vi ED=vi MAILER=mail
export EDITOR ED MAILER MAIL
PS1="HELLO> "
case $0
in
–Dsh)
# remote login
echo "you are on ‘uname‘"
trap ’echo logged off ‘uname‘’ 0
mesg n
;;
–Xsh)
# remote execution
#
# NEVER prompt for anything or ’exec’ another
# program from this case. If you perform an
# ’exec ksh’ when $0 == ’–Xsh’, remote execution
# will not work.
;;
–sh | –ksh)
# regular login
if [ "‘tty‘" != "/dev/console" -o x${TERM} = "xansi" ]
then
echo "TERM=\c"
read TERM
fi
mesg n
stty tabs erase ’^h’ kill ’^o’ echoe cr0
tabs
date
;;
esac
FILES
/opt/dk/bin directory in which this command resides
/etc/opt/dk/dkhosts host control file for destination mapping
/etc/opt/dk/dkuidtab default user ID mapping file
/dev/dkx/intf.chan remote device names
/etc/profile
SEE ALSO
dkcu(1C), authorize(1M), dkserver(1M), dkdial(3X), dkhosts(4), dkuidtab(4)
cat(1), login(1), passwd(1), who(1) in the UNIX System V User’s Reference Manual
WARNINGS
The protocol used by remote login and remote execution has a large overhead and users may notice that things
appear to be much slower than a login session from a ’DESTINATION:’ prompt or one initiated from a
dkcu(1C) command. Single character output, in particular, is very inefficient, and for programs that don’t
buffer their terminal output, piping the results through cat(1) will often speed up output.
The user’s profiles must not read nor write anything to the standard output when invoked for remote execution
(where $0 == ’–Xsh’), or services based dk.