HP-UX Reference (11i v1 05/09) - 1 User Commands A-M (vol 1)

c
cue(1) cue(1)
(Series 800 Only)
Starting Cue
There are several methods that can be used to start
cue.
• An entry for
cuegetty can be placed in the
/etc/inittab file. See cuegetty(1M)). This is
the preferred method as the user does not need to do anything further to start
cue.
• Start
cue from the command line by typing:
cue.
• Start
cue by making it the last entry in the user’s
.login configuration file.
Multiple
cue logins may run simultaneously on separate terminals attached to the same local host.
cuegetty can be configured in the
/etc/inittab file for all users.
Remote users to the CUE system must access CUE by entering the
cue command at the command-line
prompt or as the last item in the user’s
.login configuration file.
EXTERNAL INFLUENCES
Environment Variables
cue invokes the user’s session with the following default environment:
CUESESSION is set to the session type selected. Valid values are:
/usr/bin/sh POSIX Shell (DEFAULT)
/usr/bin/tsm manages up to 10 sessions at once
/usr/bin/keysh Easy Context-Sensitive Softkey Shell
/usr/bin/ksh Korn Shell
/usr/bin/csh C Shell
HOME is set to the home directory of the user
LANG is set to the native language selected (C is the default)
LOGNAME is set to the user name
MAIL is set to /var/mail/$LOGNAME
NLSPATH
is set to the path applications search for NLS message catalogs, usually
/usr/lib/nls/%L/%N.cat
PATH
is set to the path to be searched for commands :/usr/bin
SHELL
is set to the user’s default shell (from /etc/passwd )
Several methods are available to modify or add to this list depending on the desired scope of the resulting
environment variable.
Basic environment variables can be set for all
CUE users on a system by setting the values in
/etc/profile and /etc/csh.login. Personal environment variables can be set on a per-user basis
in the script file
$HOME/.profile
for sh and ksh users or .cshrc for csh users.
Note that alias and function definitions need to be included in the file specified by
ENV for ksh, as this file
will be sourced for each invocation of the shell. For csh users, the
.cshrc file should be structured such
that it cannot generate any output on standard output or standard error, including occasions when it is
invoked without an affiliated terminal. The
rcp command sources the .cshrc file and any output gen-
erated by this file, even to standard error, causes problems. Commands such as stty should be placed in
the .login file, not in .cshrc, so that their output cannot affect rcp.
For users with appropriate privileges, PATH is augmented to include /etc.
Section 1−−158 Hewlett-Packard Company − 2 − HP-UX 11i Version 1: September 2005