Administration Directory (op_admin)
The administration directory (<HOME>/op_admin) contains configuration information and files specific to an individual user, such as:
- program configurations
- model directory paths
- logical key definitions
- model backups
Because the installation directory serves as a centralized resource for all users at a site, it is not an appropriate place to store files that are specific to a particular user. Such files are best stored in the home directory of each user, where they can be easily found and are protected by the user’s directory permissions. For this reason, Modeler supports individual administration directories in which users store their files.
The administration directory must be named op_admin so that programs can access it via the shell variable-based path name <HOME>/op_admin. This requirement stems from the overall file system organization. Because the installation directory and model directories can be placed anywhere in the file system, Modeler must have a fixed location from which to obtain the locations of these directories. The administration directory serves as a fixed site for this configuration information relative to the current user’s home directory.
The initial organization of op_admin is established at installation, as follows:
Table 5: Initial Contents of the op_admin Directory
| Subdirectory | Contents |
|---|---|
| bk | The backup directory stores user model backups, which are automatically created by the modeler program at user-specified intervals. |
| tmp | The temporary file directory stores any temporary files created by Modeler programs. |
opnet-<release>.prefs(for example: opnet-18-0.prefs) |
The preferences (environment database) file specifies user configuration data and preferences for Modeler programs (including the above-mentioned directory location information). |
Backup Directory (bk)
Modeler creates two types of backup files:
- time-based backup files preserve all model files being edited at the time the backup occurs. You can specify the backup interval (by default set at 60 minutes) with the “backup_interval” preference. Note— The backup operation is not performed if Modeler is performing another operation (such as a simulation) when it is time to perform a backup.
- version-based backup files are created each time you modify and save an existing model file. You can specify the number of versions saved with the “backup_max_count” preference.
Both types of backups are stored in the backup directory (<HOME>/op_admin/bk) with file names based on the name of the corresponding model.
Automatic backup behavior is specified by the following preferences:
- “project_backup_disable” – Specifies whether to suppress automatic backups of open projects.
- “project_backup_query_dialog_disable” – Specifies whether to suppress the Project Backup Prompt dialog box before performing automatic backups.
Version-based backups are named using the syntax:
<model_name>_bk.<n><file_type_suffix>
where n is a consecutive number, with a maximum value set by the backup_max_count preference.
Time-based backup files are named using the syntax:
<model_name>_bk.<file_type_suffix>
If a name has not been assigned to a model when a time-based backup occurs, it has the default name unnamed. This file overwrites any older unnamed model backups of that type.
The file suffix identifies the type of file. See File Naming Conventions for a list of these suffixes.
You can make a model backup a regular model file by moving or copying it into a model directory, using one of the following commands:
-
sample Linux command-line:
% mv net1_bk.nt.m net1.nt.m -
sample Windows command-line:
C:\> move net1_bk.nt.m net1.nt.m
The backup model then appears in the relevant model menus.
Temporary File Directory
The temporary file directory (<HOME>/op_admin/tmp) contains temporary files generated by Modeler in the course of execution, such as the graphics capture files and report files generated by printing operations.
Most of the files stored in tmp have value for a limited time only, after which they can be removed. Typically, the only files worth keeping are captured graphics or PostScript files that must be reprinted periodically. You should move such files from tmp and store them elsewhere to avoid accidental removal.
During periods when a great deal of printing is being performed, the temporary directory tends to fill up with files. It is a good idea to periodically clear out tmp using the op_clrtmp utility described in “op_clrtmp” on page 146.