/* ---------------------------------------------------------------------------*/
 (C) Copyright IBM Corp. 2009
 
  All rights reserved. This program and the accompanying materials
  are made available under the terms of the Eclipse Public License v1.0
  which accompanies this distribution, and is available at
  http://www.eclipse.org/legal/epl-v10.html

Author:       Sachin Sant <sachinp@in.ibm.com>

/* ---------------------------------------------------------------------------*/


SBLIM CMPI Crash Dump Providers README
--------------------------------------

The Crash dump Providers allows managing and receiving notifications of Linux
Kernel Crash Dumps.

The provider defined  classes are

- Linux_OSCrash
- Linux_OSCrashDumpCapture


Package Contents
----------------

./README                This file
./INSTALL		Installation instructions
./*.h                   Header Files
./*.c                   Provider Code
./mof/                  Schema file(s)


Build Instructions
..................

Prerequisites
.............
- CIMOM installed
- CMPI enabled CIMOM
- SBLIM package indication_helper installed
- sblim-cmpi-devel package installed
- sblim-cmpi-base package installed

Building cmpi-crashdump
.......................

This package is now GNU autotool enabled, refer to the file named INSTALL for
generic instructions.

The generated configure script tries to determine where the CMPI header files
are located. For this purpose it searches a set of well-known locations.
The "canonical" location is /usr/include/cmpi or /usr/local/include/cmpi,
depending on how configure is invoked.

Further, configure "determines" where providers are to be installed. Actually,
there's no detection logic. The provider directory will always be
/usr/lib/cmpi or /usr/local/lib/cmpi. If a CIM server requires a particular
directory this can be selected by specifying the PROVIDERDIR variable.

And finally, configure tries to find out which CIM server type is being used.
This is necessary in order to select the appropriate schema and provider
registration technique. If the CIM server is not or incorrectly identified,
it is possible to specify it via the CIMSERVER variable.
Supported values are pegasus, sfcb, openwbem and sniacimom.

Here is a quick start

1) ./autoconfiscate.sh
2) ./configure
3) make
4) make install

Load Schema into CIMOM's repository
...................................

with Pegasus/sfcb :
.................
The loading and registering of the classes and their provider is done during
the "make postinstall".

One could also use the provider-register.sh script from the package.

provider-register.sh -r Linux_CrashDump.registration -m Linux_CrashDump.mof


Class specific Libraries
........................

class Linux_OSCrash
...........................
- Linux_OSCrashProvider.c
- Linux_OSCrashDumpCapture.c/.h
- Linux_OSCrash.c/.h

