The dupatch utility captures patching activities in the following log files:
Every time you run dupatch it creates a session log that captures dupatch activities. The session.log files from the previous 25 sessions are saved. The order is first in, first out, with session.log.25 as the oldest file.
When you run dupatch from the newly untarred kit or from the mounted Tru64 UNIX Patch CD–ROM, dupatch determines if the patch distribution contains new patch tools, and loads them if necessary.
This log file has a name similar to this: Dupatch_load_2000Jul1:15:43:35.log
When you run the system baselining feature, dupatch creates a baseline log. The session.log files from the previous 25 sessions are saved. The order is first in, first out, with baseline.log.25 as the oldest file.
When patches are installed or removed, an event log captures that information. Only one copy of the file is updated each time patches are installed or removed. The information in the patch event log is not available through the dupatch user interface, but the log is a text file that you can view with a command such as more. The following list describes the types of information an event log provides, although the format and content are subject to change. Example A-1 “ Sample Event Log” shows a typical event log.
The revision of dupatch being used
The type of action that was taken; either install or remove
The name entered by the user through a dupatch query
The name of the user performing the action
Notes that were entered by the user through a dupatch query
The directory from which the patch kit was installed
The name of the patch kit that was installed
The choice made on whether or not the patch installation is reversible
A pointer to the directory that contains the original files before they were patched
A plain directory; not a mount point or a symbolic link