 |
» |
|
|
|
This section covers: How (the order in which) Login Manager accomplishes its functionality.
The default Login Manager configuration | |
Login Manager configuration files are set up to run HP VUE on these
configurations: System with a single bitmap display that is also the system console.
Networked systems, each with a single bitmap display that is the system console.
See Also.
Login Manager Files | |
Executables. Login Manager's user authentication and session startup functions are provided by three executable clients and a number of shell scripts. The three HP VUE executable clients are in /usr/vue/bin. - Client
Description - vuelogin
Performs configuration tasks and spawns another vuelogin process for each display in the system. There
will be n+1 vuelogin clients running, where n is the number of displays managed by the system. - vuegreet
Provides the functionality of the login screen. - vuehello
Provides a transition effect between successful login and the beginning of the HP VUE session. By default, this is a welcome message and copyright notice.
System-wide configuration files. These files are located in /etc/vue/config. - File Name
Description - Xconfig
Contains the resources for the behavior of vuelogin. It can also define new locations for the other vuelogin configuration files. - Xservers
Contains a list of servers to be run by vuelogin. - Xresources
Contains resources for the appearance of the login screen. - Xstartup
Program (usually a shell script) that is run as root after the user login and password is validated. - Xsession
Shell script that sets up the user environment variables, runs user and system customization scripts,
runs vuehello, and invokes the session manager. - Xreset
Program (usually a shell script) that is run as root upon termination of an HP VUE session. It can be used to return the system to its pre-Xstartup configuration. - Xaccess
Contains a list of host names which are allowed or denied access to this machine. Used if remote login is attempted. This file also allows users to bypass the Login Screen. - Xfailsafe
Contains commands to start a simple session consisting of a window manager and terminal emulator. This session allows access to Vue configuration files in case your regular Vue session becomes dysfunctional.
- Xsession.d
Directory containing additional system-wide startup customization scripts. Scripts must be executable and are run in alphabetical order.
User-specific configuration files. These files are located in the user's home directory. - File Name
.Description - .Xauthority
Contains authorization information needed by clients that require an authorization mechanism to connect to the server. - .vueprofile
Contains environment variables, definitions, and pre-session commands.
See Also.
How Login Manager starts an HP VUE session | |
Parent vuelogin.
The Login Manager executable (vuelogin) is started by /sbin/init.d/vuerc during the system boot sequence.
vuelogin reads /etc/vue/config/Xconfig. Xconfig contains resources for various login manager actions. vuelogin reads the following files in /etc/vue/config:
Xservers, or the file identified by the resource Vuelogin.servers in the Xconfig file. Xresources, or the file identified by the Vuelogin*resources resource in the Xconfig file.
vuelogin starts an X server for each local display. (If an X server is already running on a local display, vuelogin ignores that display until the controlling server goes away.) vuelogin starts a child vuelogin process for each managed display.
Child vuelogin. The following steps happen for each child vuelogin started by the parent vuelogin: If configured to do so, vuelogin modifies the X server font path of each local display (for example, to access a remote font server). vuelogin invokes vuegreet, which displays the login screen and handles the user's interaction with the login screen.
The following steps happen for each child vuelogin after the user's login name and password have been validated: If configured to do so, vuelogin reapplies up-to-date modifications to the X server font path for each local display. vuelogin runs (as root)
/etc/vue/config/Xstartup if it is present.
vuelogin sets certain environment variables to default values. vuelogin then runs (as the user) /etc/vue/config/Xsession, a ksh script which performs a number of functions before starting the actual session: It initializes several additional environment variables, including TERM, EDITOR, MAIL, SESSION_SVR, and VUETERM. If the user is using a restricted shell, Xsession now concludes by invoking mwm and a single terminal window. If possible, it runs the /etc/profile script, which may alter environment variables such as PATH, MANPATH, and SHLIB.PATH. It runs the user's $HOME/.vueprofile script which may define the new environment variables, overriding existing variables, or starts background processes. .vueprofile should be either a sh or ksh script. It runs all executable scripts in the /etc/vue/config/Xsession.d/ directory in alphabetical order. It runs vuehello, which displays the message of the day or some other transition effect. If requested to do so, it runs the user's login profile script ($HOME/.profile or $HOME/.login, depending on the user's login shell). The profile script syntax should be appropriate for the user's login shell.
It starts the session manager, vuesession.
After the session terminates: vuelogin runs (as root)
/etc/vue/config/Xreset, if it is present.
Starting a Pre-Session Background Process | |
It is sometimes necessary that certain applications
be up and running in the background before the
session manager starts. If you want to start such an application or
daemon before the session starts, you can start it in: /etc/vue/config/Xstartup.
an /etc/vue/config/Xsession.d script.
Use Xstartup if you want the application to be started for all
sessions system-wide, you want it to be run by root, and you want the
user to have
no control over its startup. Often it may be desirable to let the user have the first opportunity to
start a background application (in .vueprofile), and invoke a
system default only if necessary (in an Xsession.d script). An
environment variable can be used to indicate what has been done or
needs to be done. For example, to start an Input Method Server,
/etc/vue/config/Xsession.d/0020.vueims might contain:
#/bin/ksh
#
# If an IMS has not already been started, start
# one now, and set VUE_IMS_PID to its process id.
#
if [ ! "${VUE_IMS_PID:-}" ]; then
echo >>$VUE_START_LOG "0020.vueims: starting IMS"
vueims &;
VUE_IMS_PID=$!
fi
|
The user could start an IMS and prevent the default from running
by including the following in $HOME/.vueprofile: See Also.
|
Printable version
