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 ®le. 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 con®guration ®le.

Multiple cue logins may run simultaneously on separate terminals attached to the same local host. cuegetty can be con®gured in the /etc/inittab ®le 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 con®guration ®le.

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 ®le $HOME/.profile for sh and ksh users or .cshrc for csh users.

Note that alias and function de®nitions need to be included in the ®le speci®ed by ENV for ksh, as this ®le will be sourced for each invocation of the shell. For csh users, the .cshrc ®le should be structured such that it cannot generate any output on standard output or standard error, including occasions when it is invoked without an af®liated terminal. The rcp command sources the .cshrc ®le and any output generated by this ®le, even to standard error, causes problems. Commands such as stty should be placed in the .login ®le, not in .cshrc, so that their output cannot affect rcp.

For users with appropriate privileges, PATH is augmented to include /etc.

Section 1−158

− 2 −

HP-UX Release 11i: December 2000