| As far as setup for users is concerned, you perform setup in a vPars environment just as you would in a non-vPars environment. The prompt, for instance, might include the hostname of your system. On a system where the hostname and vPar name are different, you still probably want your prompt to include the hostname. You can, however; also include the vPar name at the prompt if you wish. The following is the section of /.profile that includes some minor customization for the user root: # Added for prompt, history etc. HISTFILE=~/.sh_history; export HISTFILE EDITOR=vi; export EDITOR PS1="`whoami`@`hostname`"'[${PWD}] > '; export PS1 This is the information I typically add for root to provide history file information and the prompt. I included the hostname here which would result in a prompt that includes the user's name, hostname, and present working directory, as shown below: root@actappd1[/.root] > If your users need to see the vPar name, this can be added to or substituted for the hostname in .profile. This is another example of the advantage to having your hostname and vPar name identical. It may be; however, that your hostname is very confusing, and substituting a simple vPar name in the prompt may be advantageous to users. In either case, your user setup does not change with vPars, since vPars are the same as separate systems from a user perspective. |
