cue(1)

cue(1)

(Series 800 Only)

NAME

cue - HP Character-Terminal User Environment (CUE)

SYNOPSIS

/usr/bin/cue

DESCRIPTION

CUE provides an easy-to-use, attractive, customizable environment that allows users on Series 800 HP-UXsystems to easily identify themselves to the system and begin a work session. See DEPENDENCIES for supported terminal types.

A menubar is available for changing the native language of the session, changing the type of session to start upon a successful login, or getting on-line help. To obtain context-sensitive help at any time, press the function key labeled HELP ( f 1 ).

A pulldown menu and function keys ( f 1- f 8) are displayed, allowing the user to modify various options or to get help. Before the login is initiated, the user has the option of interactively changing the native language of the session and the type of session to start upon a successful login.

The default native language is C, but the language is easily modi®able by entering the Language Menu which is accessible by selecting the Con®guration item in the menu bar. The native language can also be speci®ed as a parameter to cuegetty (see cuegetty(1M)).

The default session type is the POSIX shell, sh, but the session type can be easily changed to tsm, keysh, or csh by entering the Session Type Menu which is accessible by selecting the Con®guration item in the menu bar.

The following standard login features are available:

∙password aging

∙logging invalid login attempts in /var/adm/btmp

∙list of valid ttys for super-user login

CUE displays a visual screen that prompts for the username and corresponding password. If your user- name does not have a password, press the <carriage return> key to skip this ®eld. Terminal echo is turned off (where possible) during typing of the password so that it will not appear on any written record of the session. After three unsuccessful login attempts, a hangup signal is issued.

If password aging has been invoked by the super-user on your behalf, your password may have expired. In this case, you will be diverted into passwd to change it, after which you can attempt to login again. See passwd(1).

If login is not successfully completed within a certain period of time (e.g., ®ve minutes), the terminal may be silently disconnected.

After a successful login, the accounting ®les are updated, initializing the user and group ids, group access list, and working directory. If the session type chosen is tsm, the SHELL to start in each tsm session is determined from corresponding user entries in the /etc/passwd ®le. cue then forks the appropriate shell by using the last component of the shell pathname preceded by a - (for example, -shor -ksh). When the session type is invoked with its name preceded by a minus in this manner, the shell performs its own initialization, including execution of pro®le, login, or other initialization scripts.

For example, if the user login shell is sh(1) or ksh(1) the shell executes the pro®le ®les /etc/profile and $HOME/.profile if they exist (and possibly others as well). Depending on the contents of the pro®le ®les, messages regarding mail in your mail ®le or any messages you may have received since your last login may be displayed. At this point, cuesession is started to perform accounting procedures, display messages, and start your session.

If /var/adm/btmp is present, all unsuccessful login attempts are logged to this ®le. This feature is disabled if the ®le is not present. A summary of bad login attempts can be viewed by users with appropriate privileges by using lastb, see last(1M).

If /etc/securetty is present, login security is in effect, meaning that only users with appropriate privileges are allowed to login successfully on the ttys listed in this ®le. Restricted ttys are listed by device name, one per line. Valid tty names are dependent on installation. Some examples could be console, tty01, ttya1, etc. Note that this feature does not inhibit a normal user from using su.

c

HP-UX Release 11i: December 2000

− 1 −

Section 1−157