crash dumps Post: 302388653

7 More Discussions You Might Find Interesting

1. Solaris

Generating core dumps

I have the following set up on a Sun server running solaris 5.8 for core dump generation coreadm global core file pattern: /var/core init core file pattern: /var/core global core dumps: enabled per-process core dumps: enabled global setid core dumps:...

2. Programming

strcmp core dumps

hi everyone, Right now when I do: strcmp(s1, s2); i get a core dump because at times s1 or s2 can be nothing so that makes strcmp() core dump. What is the solution, if at times I expect one of them (or both) to be NULL? I want to be able to compare that s1 is NULL and s2 is "blah" or...

3. AIX

AIX Dumps

I m studying AIX and going to appear my certification exam!!! Is any one there can give me the name of website which provides dumps for free?? or if any one is having them and can share with me.

4. Solaris

core dumps

i had a situation where a process was defunct. preap would not reap the process and gcore would not work properly (not sure why). therefore, the suggestion was to force a panic and collect the core dump. obviously you could do a savecore -L and capture the dump without bringing down the system....

5. HP-UX

HP UX Dumps

Hi Every one Pls Provide me the letest dumps of HP UX if any one can Thanks And Regards

6. Red Hat

RHCE DUMPS

Hi All, I am planing to take RHCE exam in the month of March 2012. Could anyone provide me with the latest dumps and pattern which can help me in clearing the certification exam. Thanks

7. HP-UX

Machine dumps crash on each reboot.

Hi experts, My HP machine dumps a crash upon each reboot(even if we reboot it manually) and fill the root space. Can anyone please point out what config parameter could be went wrong to happen this? Thanks, Vaishey

LEARN ABOUT OPENSOLARIS

savecore

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

NAME

       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.11							    25 Sep 2004 						      savecore(1M)