This section describes how to run the cscapture and pkg_app scripts.
On Solaris platforms, run ./cscapture.
The CS Capture script, cscapture, gathers information about your Calendar Server environment to help debug crashes, hangs, performance issues, and database problems.
The gathered data is compressed into a tar file ready to be uploaded to Sun. CS Capture also incorporates the pkg_app script, described in the following procedure, and gathers pkg_app data. Currently, the CS Capture script is only available on Solaris platforms and replaces the capture_environment script. For details about running cscapture, see Using Calendar Server Capture (cscapture) to Collect Debug Data for Sun Java System Calendar Server.
This script packages an executable and all of its shared libraries into one compressed tar file given the PID of the application and optionally the name of the core file to be opened. The files are stripped of their directory paths and are stored under a relative directory named app/ with their name only, allowing them to be unpacked in one directory.
On Solaris 9 OS or greater, the list of files is derived from the core file rather than the process image if it is specified. You still must provide the PID of the running application to assist in path resolution.
Two scripts are created to facilitate opening the core file when the tar file is unpacked:
opencore. This is the script to be executed once unpacked. It sets the name of the core file and the linker path to use the app/ subdirectory and then invokes dbx with the dbxrc file as the argument.
dbxrc. This script contains the dbx initialization commands to open the core file.
Copy the script to a temporary directory on the system where Calendar Server is installed.
Execute the pkg_app script in one of the following three ways:
./pkg_app pid-of-running-application corefile
./pkg_app pid-of-the-running-application(The pkg_app scripts prompts for the corefile name.)
./pkg_app core file