The login command establishes your AccuRev user identity. In the "User Name" field, you must enter the name of a registered AccuRev user. If your organization has more than one AccuRev repository (each managed by a separate AccuRev server process), you can choose the server to which you want to connect.
Note: Active and inactive users. A user name can be Inactive (
Remove User command) or Active (when first created; or when the
Reactivate User command is used for an Inactive user). When you log in, the username must be currently
Active.
Choose Tools > Login from the GUI main menu. This command is invoked automatically:
Tip: The
ACCUREV_SERVER environment variable influences which AccuRev Server the AccuRev GUI interacts with at startup time. See
ENV_VARS on page 268 of the
AccuRev CLI User’s Guide for more information.
Whether or not the session is canceled when you exit the AccuRev GUI is controlled by the Keep Session Active user preference. This preference is on by default -- your session remains active even after you exit the AccuRev GUI. See
AccuRev Preferences (Tools > Preferences Command) for more information on setting preferences.
A successful login command creates an encrypted file in the
.accurev subdirectory of your home directory. This file records your AccuRev username and password, along with the IP address of your client machine. Most AccuRev client commands can be executed only by an authorized user. Such commands send the information in your session file to the AccuRev Server process, so that you don't need to repeatedly "remind" the AccuRev Server who (and where) you are.
Tip: You can specify whether you want AccuRev to cancel the user session when you exit the AccuRev GUI. See
Keep Session Active for more information.
The name of the session file includes the hostname and port number of the AccuRev Server. If you Login to different AccuRev Server processes, you'll have multiple session files, one for each Server. Example:
These session files indicate that your are logged in to an AccuRev Server on host venus, listening on port 5050, and are also logged into two different AccuRev Server processes on host
mars.
What if you want to be testuser john in one GUI window, but testuser
mary in another -- both using the same AccuRev Server? You can't have two session files with the same name (for example,
session_VENUS_5050) in your
.accurev subdirectory. But you can have two or more session files with the same name in different
.accurev subdirectories. The AccuRev GUI uses the value of environment variable
ACCUREV_HOME as the location of the
.accurev subdirectory (and will create this subdirectory, if necessary). It also uses
ACCUREV_HOME whenever it checking for the existence of a session file in order to authenticate you.