Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

cr_info(3) [hpux man page]

cr_info(3)						     Library Functions Manual							cr_info(3)

cr_info - retrieve crash dump information SYNOPSIS
The function returns a pointer to a structure with information about an open crash dump. cr_info_t The structure contains the following fields. Note that there is no necessary correlation between the placement in this list and the order in the structure, and the structure may contain other, reserved fields. In the future, this structure may change in size and should not be copied to avoid compatibility problems with various releases. char *cri_hostname Name of system dumped char *cri_model Model string from system char *cri_panic Panic message char *cri_release Release string from system char *cri_dumptime Time of the crash dump char *cri_savetime Time crash dump saved uint64_t cri_chunksize Size of uncompressed image files. uint64_t cri_memsize Physical size of memory (bytes) uint64_t cri_num_err Number of error messages char **cri_errmsg Error messages from INDEX file uint64_t cri_num_warn Number of warning messages char **cri_warnmsg Warning messages from INDEX file uint64_t cri_num_mod Number of module structures cri_modinfo_t *cri_modinfo Array of module structures uint32_t cri_num_nodes Number of nodes uint32_t cri_monarch_node Physical monarch node number The fields cri_hostname, cri_model, cri_panic, cri_release, cri_dumptime, and cri_savetime are all null-terminated strings; respectively, representing the name and model of the system that dumped, the panic message, the release version string of the kernel, and the times that the system dumped and the dump was saved. The amount, in bytes, of physical memory on the system is in cri_memsize. The target size, in bytes, of individual uncompressed image files is in cri_chunksize. cri_errmsg and cri_warnmsg are arrays of null-terminated strings with the list of saved messages. cri_num_err and cri_num_warn are the number of strings in each list. cri_modinfo is an array of structures defining the loaded kernel modules; there are cri_num_mod elements in the array. cri_num_nodes is the number of nodes contained on the machine and cri_monarch_node is the physical node number of the monarch. cri_modinfo_t The structure contains information specific to kernel modules loaded into memory at the time of the system crash. The specific fields are: char *mdi_loadpath File path when loaded into memory char *mdi_savepath File path when saved in crash directory uint64_t mdi_size Size in bytes uint64_t mdi_checksum Checksum of the file from cksum(1) Again, the order of these fields within the structure is not specified, and other reserved fields may be present in the structure. The caller must not modify any information in any of the structures returned by RETURN VALUE
returns a pointer to the structure described above. If is not a valid descriptor of a crash dump opened with the return value is unde- fined. EXAMPLES
Assuming a process opened a crash dump, the following call to cr_info(3) retrieves the information about the open crash dump. AUTHOR
was developed by HP. SEE ALSO
cr_open(3), libcrash(5). cr_info(3)

Check Out this Related Man Page

savecore(1M)						  System Administration Commands					      savecore(1M)

savecore - save a crash dump of the operating system SYNOPSIS
/usr/bin/savecore [-Lvd] [-f dumpfile] [directory] DESCRIPTION
The savecore utility saves a crash dump of the kernel (assuming that one was made) and writes a reboot message in the shutdown log. It is invoked by the dumpadm service each time the system boots. savecore saves the crash dump data in the file directory/vmcore.n and the kernel's namelist in directory/unix.n. The trailing .n in the pathnames is replaced by a number which grows every time savecore is run in that directory. Before writing out a crash dump, savecore reads a number from the file directory/minfree. This is the minimum number of kilobytes that must remain free on the file system containing directory. If after saving the crash dump the file system containing directory would have less free space the number of kilobytes specified in minfree, the crash dump is not saved. if the minfree file does not exist, savecore assumes a minfree value of 1 megabyte. The savecore utility also logs a reboot message using facility LOG_AUTH (see syslog(3C)). If the system crashed as a result of a panic, savecore logs the panic string too. OPTIONS
The following options are supported: -d Disregard dump header valid flag. Force savecore to attempt to save a crash dump even if the header information stored on the dump device indicates the dump has already been saved. -f dumpfile Attempt to save a crash dump from the specified file instead of from the system's current dump device. This option may be useful if the information stored on the dump device has been copied to an on-disk file by means of the dd(1M) command. -L Save a crash dump of the live running Solaris system, without actually rebooting or altering the system in any way. This option forces savecore to save a live snapshot of the system to the dump device, and then immediately to retrieve the data and to write it out to a new set of crash dump files in the specified directory. Live system crash dumps can only be per- formed if you have configured your system to have a dedicated dump device using dumpadm(1M). savecore -L does not suspend the system, so the contents of memory continue to change while the dump is saved. This means that live crash dumps are not fully self-consistent. -v Verbose. Enables verbose error messages from savecore. OPERANDS
The following operands are supported: directory Save the crash dump files to the specified directory. If directory is not specified, savecore saves the crash dump files to the default savecore directory, configured by dumpadm(1M). FILES
directory/vmcore.n directory/unix.n directory/bounds directory/minfree /var/crash/'uname -n' default crash dump directory ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
adb(1), mdb(1), svcs(1), dd(1M), dumpadm(1M), svcadm(1M), syslog(3C), attributes(5), smf(5) NOTES
The system crash dump service is managed by the service management facility, smf(5), under the service identifier: svc:/system/dumpadm:default Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. If the dump device is also being used as a swap device, you must run savecore very soon after booting, before the swap space containing the crash dump is overwritten by programs currently running. SunOS 5.10 25 Sep 2004 savecore(1M)
Man Page

Featured Tech Videos