Information Technology Reference
In-Depth Information
An alternative way is to specify both commands on the same line and sepa-
rate the commands with a semicolon, as shown in the following:
LPDEST=HPLaser; export LPDEST
A similar syntax can be used for a user account that uses the Korn shell as a
login shell. ksh also supports the following variation:
export LPDEST=HPLaser
Although defining variables for csh user accounts is not a certification
requirement, the syntax for two csh methods of defining variables is shown
in the following listing:
set LPDEST=HPlaser
setenv LPDEST HPlaser
Changes made to the user's login initialization file do not take effect until the user logs
in again, or until the .profile is executed by preceding it with a dot separated by a
space. This executes the .profile and makes it part of the current environment.
Sourcing .profile
For user accounts that use the Solaris Common Desktop Environment
(CDE), the
/usr/dt/bin/Xsession
command that starts the desktop can be
configured to read and process the .login (csh) or .profile (sh and ksh) login
initialization file in the user's home directory as part of the startup process.
The first user-specific file that Xsession calls is the .dtprofile file, located in
the user's home directory. The last line of the default .dtprofile file is as fol-
lows:
DTSOURCEPROFILE=true
This will cause the .login or .profile file to be executed (or sourced) auto-
matically. To change this default behavior and prevent the login initialization
file from being sourced, change
true
to
false
.
Summary
User accounts are created using
admintool
or the
useradd
commands.
Account information is stored in the
/etc/passwd
file. The
/etc/shadow
file
is used to store user account passwords.
Groups are created using
admintool
or the
groupadd
commands. Group
information and passwords are stored in the
/etc/group
file.
