2. Using the AccuRev GUI : The Login Command

The Login Command
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 a particular Server to connect to.
Note: Active and inactive users. A user name can be Inactive (Remove User command) or Active (when first created; Reactivate User command). When you log in, the username must be currently Active.
See also: Security on page 255
Invoking the Login Command
Choose Tools > Login from the GUI main menu. This command is invoked automatically ...
at the beginning of an AccuRev GUI session if there is no valid session file in the .accurev subdirectory of your home directory
Using the Login Dialog
To login
Type in your username -- and if you have one, your password -- then click Ok. Passwords are case-sensitive.
To switch to another server
Open the listbox by clicking the down-arrow, then select another AccuRev Server (hostname/port-number combination).
Then, complete the login by typing your username (and password).
To add an AccuRev Server to the listbox
Click the button to display the Available AccuRev Servers dialog. (See “Using the Available AccuRev Servers Dialog” on page 269.). Click the Add Server button to specify:
The "session" File
A successful Login command creates an encrypted file in subdirectory .accurev 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.
Session Expiration
Session files are automatically deleted by the AccuRev Server after an administrator-configurable interval, which defaults to 240 minutes. This implements a session-expiration feature.
Multiple Session Files for Different Servers
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:
session_VENUS_5050
session_MARS_5050
session_MARS_5999
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.
Multiple Session Files for the Same Server
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.
Example (Windows):
1.
Set ACCUREV_HOME to c:\myusers\john.
2.
Create directory c:\myusers\john.
3.
4.
5.
Set ACCUREV_HOME to c:\myusers\mary.
6.
Create directory c:\myusers\mary.
7.
8.
Login as mary in this second instance.
Hint: Setting up scripts to run the AccuRev GUI makes it easier to ensure that the GUI will be running with the environment variable set correctly.

AccuRev, Inc.
Phone: 781-861-8700
Fax: 781-861-8704
support@accurev.com