krsd(1m) [hpux man page]

krsd(1M)																  krsd(1M)

NAME

       krsd - kernel registry services daemon

SYNOPSIS

       seconds]

DESCRIPTION

       saves  data, flagged as persistent in the core kernel KRS tree, to files on disk.  These files are read when the system is booted, in order
       to restore the aforementioned persistent data.

       When running in daemon mode, sleeps, waking periodically to check if any persistent data have changed since the last save.   If	persistent
       data have changed, the new state of the data is saved to disk.  Otherwise, sleeps for another period of time and then repeats the process.

       When running in one time (non-daemon) mode, unconditionally saves persistent data to disk and then exits.

       Normally, is executed in daemon mode by init(1M).  The entry for will cause to be respawned automatically if it is terminated.

       uses the message logging facility to log all activity.

       Persistent KRS data are maintained in files based on the class of the data in question.	Currently, the following classes are recognized:

	      Data that apply to the system in general,
		   regardless of what configuration is booted.	This data is saved in the file

	      Data specific to a given bootable configuration.
		   This data is saved in the file

       only saves the class; the class is managed by the kernel configuration tools (see kconfig(5)).

   Options
       recognizes the following options:

       One time     mode, unconditionally save persistent data to disk, then exit.

       Run from     parent does not spawn a child nor exit.  Required if from inittab is to work properly.

       Set the delay time to
		    seconds seconds.  This is the time interval between attempted saves of persistent data.  The default interval is 300 seconds.

AUTHOR

       was developed by Hewlett-Packard Company.

SEE ALSO

       krs_flush(1M), kconfig(5), krs(5).

																	  krsd(1M)

livedump(5)							File Formats Manual						       livedump(5)

NAME

       livedump - a feature that saves operating system state to the file system for debugging purposes.

DESCRIPTION

       is  a  feature by which a running operating system's state can be saved to the filesystem without stopping/rebooting the system.  The saved
       dump can be used for debugging purposes.

       saves the information in a existing dump format readable by the system crash dump access library, See libcrash(5).

       saves the images and related files in the directory The trailing n in the directory name is a number that increases by one  every  time	is
       run  with  the  same This number is stored in the file If the file does not exist in the configured path then it is created and the default
       value of 2 is stored in it.

       supports both blocking and non-blocking invocation.  In a blocking invocation, the control will be returned to the invoker only after  com-
       pletes.

       In case of a non-blocking invocation, the control will be returned to the callee and the user can query the status of by using the command.

       For  blocking  mode  invocation, messages will be printed on the user console, and for non-blocking mode invocation, messages are stored in
       the syslog file

       supports selective dump using page classification similar to crash dump.  uses filesystem space to save the operating  system  state.   The
       amount  of  filesystem  space  to  be left free can be configured by the user.  The operating system state saved by is in the form of image
       files.  The maximum size of each image is also configurable by the user.  The location on the filesystem where saves the system	state  can
       be set by the user.

       configuration can be queried/changed using the utility.	See livedump(1M) for more details.

       The  dump  saved by is not a snapshot of system memory.	Instead it is the state over a period of time.	As the system state keeps changing
       continuously (when is in progress), the dump taken would be a transient one.  Due to this transientness some data structures may be  broken
       in the dump.

   Definitions
       minfree	      Amount  of  space  to be left free upon completion of If detects that the free disk space has fallen below minfree value, it
		      stops saving the dump.  The saved dump, in this case, may not be debuggable.

       chunksize      Size of a single physical memory image file.  See livedump(1M) for details.

       pageclass      System memory classes.  See crashconf(2) for details on defined system memory classes.  does not support saving of the  buf-
		      fer cache and unused pages.

       sid	      The  session  id	associated  with  every  session.   generates  this  id for each invocation in order to identify a session
		      uniquely.  The user can use this id to specify the session to be aborted.

       path	      Directory to save the If this option is not specified, then is used as the default directory to save the dump.

AUTHOR

       The feature described here was developed by Hewlett-Packard.

FILES

       messages saved by

SEE ALSO

       livedump(1M), crashconf(2), libcrash(5).

																       livedump(5)