The application’s clients and servers generate a number of log files. These logs enable an administrator to evaluate the performance of the system and potentially troubleshoot problems. Each server configuration has its own server log and security log. Each client creates its own log file, which records activity between that client and the server configurations it is connected to.
Users must have the appropriate security access rights in order to view a log file. These access rights can be set using the menu option in the Server Administration tool.
The server log file (Server.locale.Log) records the activity on a server configuration. Each time you start a server configuration, the Server renames the existing log file and creates a new log file for the current server configuration session. The log file from the previous startup is renamed to include the date and time at which it was renamed (Server.locale.date.Log). For example, if you start a server configuration on November 9, 2011 at 5:22 P.M., the old Server.locale.Log file is renamed Server.en-US.2011-11-09-17-22-59.Log and a new Server.locale.Log file is created whose time stamp might be 11/9/2011 17:23:03.
If the locale specified for the operating system on which your server runs is not US English, you will have two server log files: one for US English and one for your locale. For example, you might have both Server.en-US.Log and Server.fr-FR.Log. The first log is for support purposes, and the second log is for your use.
You can view the contents of the server log file at any time, even while the server configuration is running by choosing .
A security log records all security-related events for a server configuration. For each secured event (such as logging on or off), the security log records the date and time it occurred, the user performing the operation, the workstation from which the operation was performed, the item acted upon, and whether the operation failed.
Depending upon the number of users and the amount of activity on a server configuration, the security log may grow rapidly. To keep the log to a reasonable size, you can have the server delete old entries. First, decide how long you want to have security events available, then configure the server configuration to purge entries that are older than this time period. See “Working with the Security Log” topic in Related Information for how to purge security log entries.
If you have access rights to a server configuration, you can view its security log at any time the server is running. The security log is not a typical log file, as its data is stored in the application database. The security log is available by choosing .
The StarTeam.Log file records the operations performed on your client workstation during a session. It helps you troubleshoot and document errors or operations between the server and your workstation that failed during server configuration sessions.
The StarTeam.Log file may contain the following types of information:
Every time you start your client, the system creates a StarTeam.Log file in the folder location specified in your personal options.
On most systems, the default location for the StarTeam.Log file is C:\Program Files\Borland\StarTeam x.x. If there is a StarTeam.Log file already in this folder, the application renames the existing file to include the date and time at which it was renamed. For example, if you create a StarTeam.Log file on November 9, 2011 at 10:35 A.M., the old StarTeam.Log file is renamed StarTeam-09-Nov-11-10-35-18.Log, and a new StarTeam.Log file is created.