CS Capture gathers the following set of information:
Machine environment information:
Machine statistics (vmstat, iostat, prstat, mpstat, and netstat)
Disk space usage (df)
Details of running processes (ps)
Hardware configuration (prtconf)
Swap information (swap -l)
Patches (showrev -p)
Calendar Server information:
Configuration (contents of SUNWics5/config)
timezones.ics file
Calendar Server production database (optional)
Calendar Server log files
Calendar Server running process information (optional):
3 gcores on each running process every 5 seconds
Uses pkg_app (supplied) to collect debugger environment for gcore analysis
Runs pstack and pmap against all gcores.
Core dump information from crashed processes:
Searches and collects Calendar Server process cores
Uses pkg_app (supplied) to collect debugger environment for core analysis
Runs pstack and pmap against core files
Packages data:
Uses tar and compress to package the data
Figure 1–1 shows a directory-layout diagram illustrating how the captured data is structured and archived:
The data gathered may vary, depending on the Calendar Server's configuration and the way cscapture is executed. (See 1.7 Running CS Capture for further information on different ways to run cscapture.) Also, certain directories will only exist if cores files are found.