cr_verify(3) Library Functions Manual cr_verify(3)NAME
cr_verify - verify integrity of crash dump
SYNOPSIS DESCRIPTION
uncompresses and verifies the sizes and checksums of every file in the crash dump identified by crash_cb.
flags is a bitmask of zero or more of the following flag values:
will not attempt to verify checksums of files in the crash
dump if this flag is set. Only sizes will be verified.
will write messages to stderr during time-consuming operations
(decompressions and checksums) if this flag is set.
will write messages to stderr describing any validation problems
that are encountered. If this flag is set, should not be called when returns; repeated error messages would result.
RETURN VALUE
Returns zero for success. Other possible return values are described in libcrash(5).
EXAMPLES
The following call to cr_verify(3) verifies the integrity of the dump.
WARNINGS
Because it uncompresses and checksums all files in a dump, can be very time-consuming. If was not specified, the calling application
should notify its user before calling that there may be a significant delay.
AUTHOR
was developed by HP.
SEE ALSO cr_open(3), cr_perror(3), libcrash(5).
cr_verify(3)
Check Out this Related Man Page
cr_uncompress(3) Library Functions Manual cr_uncompress(3)NAME
cr_uncompress - uncompress a file in a crash dump
SYNOPSIS DESCRIPTION
The ensures that a file, part of a crash dump described by crash_cb, is uncompressed and matches its expected size and checksum (as com-
puted by cksum(1)). This call is most often used to ensure the integrity of module files that are a part of the crash dump; see
cr_info(3).
pathname is the name of the file to uncompress. Supported compression methods include gzip(1), which appends a to the filename, and com-
press(1), which appends Respectively, size and checksum are the expected size and checksum of the uncompressed file. Either validity check
can be disabled by specifying zero for the corresponding parameter.
RETURN VALUE
Returns zero for success. Other possible return values are described in libcrash(5).
EXAMPLE
The following call to cr_uncompress(3) ensures that the kernel file is uncompressed and validated.
AUTHOR
was developed by HP.
SEE ALSO gunzip(1), uncompress(1), cr_info(3), cr_open(3), libcrash(5).
cr_uncompress(3)
Hi!
Letīs say I want copy dump-files to a location.
These dump-files vary between 80 and 280MB and will be produced in about 1min or less.
I have a cronjob which (not only) copies those.
So how can I find out whether a file is currently produced or not?
Because if my script works with these... (2 Replies)
Hi
i want to know if many users are logging in system then how would i know that how much space in system i am consuming..
Thanks
Vijay sahu (4 Replies)
Hi gurus,
I will be glad if anyone can help me with this:
How do you copy a crash dump file to send to your support provider?
Thanks lots guys. (1 Reply)
Hello
There are options / commands to check which process is consuming maximum memory
However is there any command/mechanism which will tell us which process was consuming maximum memory in specific time interval in the past?
I heard nmon report can help in this regard.
is there any... (5 Replies)
hey I am dumping two database results into two text files and doing checksums on them.
Anyone know how to do this.
I originally was doing line by line comparison and diff but I need something faster for larger gb size files. anyone got tips? (5 Replies)