Path: utzoo!attcan!uunet!know!zaphod.mps.ohio-state.edu!sdd.hp.com!hp-pcd!hpcvlx!pam
From: pam@hpcvlx.cv.hp.com (Pam Raby)
Newsgroups: comp.sys.hp
Subject: Re: Instant Ignition problems
Message-ID: <101950147@hpcvlx.cv.hp.com>
Date: 14 Sep 90 01:36:48 GMT
References: <1568@sdrc.UUCP>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 81


Following is an overview of the HP-VUE startup process and a brief description
of where various environment sorts of things might be most appropriate.
Sorry for the length, it's fairly condensed.  I hope this overview helps
clarify when/where to set environment variables, start clients, etc.

Pam Raby
pam@cv.hp.com

============================= CUT HERE ==============================

First, note that until you have actually logged in, errors are appended to
/usr/lib/X11/vue/Vuelogin/Xerrors.  Once you have logged in and your session
is initiated, errors are appended to $HOME/.vue/errorlog.

1.  init spawns the parent vuelogin process which reads
    /usr/lib/X11/vue/Vuelogin/Xconfig, starts the X server, and spawns a
    child vuelogin for each display on the system.  Whenever you modify the
    Xconfig file, you should restart the server manually i.e. select restart
    from the login screen.  xrdb is used to load resources.

2.  The child vuelogin sets the following environment variables:
	DISPLAY is set to the first field in the Xservers file
	HOME as specified in /etc/passwd
	LANG is set to the display's NLS language (if any)
	PATH is set to the Vuelogin userPath resource
	     default is /usr/bin/X11:/bin:/usr/bin:/usr/contrib/bin
	USER is set to the user name
	SHELL as specified in /etc/passwd
	TZ set to Vuelogin.timeZone resource in Xconfig; default MST7MDT
	XAUTHORITY set to an authority file
    Note that no shell processing is available at this point (as was already
    mentioned).  Environment variables affecting the X server and/or all
    users on a display are set in Xconfig.

    The child vuelogin runs vuegreet to display the login screen as specified
    in /usr/lib/X11/vue/Vuelogin/Xresources, and validate the user and
    password.  The Xstartup script is then run.  Xstartup is run "as root"
    on behalf of the user to perform system-level functions, e.g. mounting
    home directories from file servers, displaying the message of the day,
    etc.  Last, the session is started via Xsession.

3.  Xsession is a ksh script which sets these environment variables:
	LOGNAME is set to the user name
	TERM is set to hpterm
	MAIL is set to /usr/mail/$USER
    Environment variables you want to affect all users on a display which
    require shell processing or are dependent on the value of other
    environment variables should be set in the Xsession script.

    Xsession displays the copyright notice by running vuehello.  Xsession
    then execs the appropriate shell, passing it $HOME/.vueprofile if it
    exists.  Xsession then starts your session as follows:
	if VUE is present, vuesession is run.
	if XDM is present, .xsession is run.
	otherwise, $HOME/.x11start is run.

    Environment variables for individual users are set in $HOME/.vueprofile.
    The .vueprofile file should not perform terminal I/O nor prompt for user
    input, which causes startup problems.  .profile (or .login) is still used,
    i.e. hpterm -ls, rlogin, telnet.

4.  vuesession starts all the VUE daemons, merges vue.resources into the
    resource database, sets server settings as specified in vue.settings,
    starts the window manager vuewm, runs vue.session (your saved session),
    and runs the sessionetc script if it exists.  vue.resources, vue.settings
    and vue.session are all found in $HOME/.vue/host:display/home
    (or current).  sessionetc is found in $HOME/.vue/host:display.  Start
    clients not automatically saved by VUE in sessionetc.

5.  Session termination.  Assuming you resume your current session, the
    contents of the resource database are saved in vue.resources, server
    settings are saved in vue.settings, and clients' command lines as set
    via the WM_COMMAND property are saved in vue.session.

    The Xreset script, counterpart to Xstartup, is run, again "as root" on
    behalf of the user.  This is your opportunity to "undo" what was done
    in Xstartup if needed.

    Now, you're back to vuelogin and, by default, the server has been
    restarted (not just reset).