Parent document is top of "comp.sys.hp.hpux FAQ"
Previous document is "6.6 How come my HP X/Motif clients take a LONG time to display on a Sun?"
Next document is "6.8 How can I get console messages to go to an hpterm?"

6.7 How can I get my login stuff to work under HP-VUE?

Suggestion 1) The HP-VUE User's Guide suggests that people make a copy
              of /usr/vue/config/sys.vueprofile to ~/.vueprofile. This file
              contains a detailed set of comments about setting it up so
              that their .login/.profile will be sourced correctly (including
              details on making sure that tset(1)-like programs are only run
              when *NOT* in HP-VUE).

Suggestion 2) When you login via VUE, VUE sources ~/.vueprofile *INSTEAD
              OF* your .login (csh), .profile (sh/ksh), and other startup
              files.  Whatever actions are taken in  ~/.vueprofile are
              persistent across any children started by VUE. Meaning that
              if you symbolic link  ~/.vueprofile to your ~/.profile, then
              VUE will source your ~/.profile before starting the window
              system, and all children (hpterms/xterms and their interactive
              shells) will inherit this environment (prompt variables et al).

              Documentation indicates your ~/.vueprofile should contain
              either csh, or sh/ksh syntax, depending upon what your login
              shell is.

              When csh is my login shell, I set my  ~/.vueprofile  to contain
              only two lines:

                 if ( -f /etc/csh.login ) source /etc/csh.login
                 if ( -f ~/.cshrc ) source ~/.cshrc

              When sh/ksh is my login shell, I set my ~/.vueprofile to
              contain only two lines:

                 test -f /etc/profile && . /etc/profile
                 test -f ${HOME}/.profile && . ${HOME}/.profile

              So, before  starting the window  manager and any clients, VUE
              makes sure that all my shell startup files are sourced and all
              the variables I want in my shell environment are already there
              and waiting for me.

(Thanks to David Masterson <davidm@prism.kla.com>, and
           Steve Jumonville, 3com)
Parent document is top of "comp.sys.hp.hpux FAQ"
Previous document is "6.6 How come my HP X/Motif clients take a LONG time to display on a Sun?"
Next document is "6.8 How can I get console messages to go to an hpterm?"