Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris Cluster Data Services Developer's Guide Oracle Solaris Cluster 4.1 |
1. Overview of Resource Management
3. Resource Management API Reference
6. Data Service Development Library
8. Sample DSDL Resource Type Implementation
9. Oracle Solaris Cluster Agent Builder
12. Cluster Reconfiguration Notification Protocol
13. Security for Data Services
A. Sample Data Service Code Listings
B. DSDL Sample Resource Type Code Listings
C. Requirements for Non-Cluster-Aware Applications
D. Document Type Definitions for the CRNP
Note - The NVPAIR data structure that is used by both SC_CALLBACK_REG and SC_EVENT is defined only once.
<!— SC_EVENT XML format specification Copyright 2001, 2012, Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. The root element of the XML document is intended to be a direct, generic, translation of the Oracle Solaris syseventd message format. It has attributes to represent the class, subclass, vendor, and publisher, and contains any number of NVPAIR elements. ATTRIBUTES: VERSION: The CRNP protocol version of the message. CLASS: The sysevent class of the event SUBCLASS: The subclass of the event VENDOR: The vendor associated with the event PUBLISHER: The publisher of the event CONTENTS: SUBELEMENTS: NVPAIR (0 or more) —> <!ELEMENT SC_EVENT (NVPAIR*)> <!ATTLIST SC_EVENT VERSION NMTOKEN #FIXED "1.0" CLASS CDATA #REQUIRED SUBCLASS CDATA #REQUIRED VENDOR CDATA #REQUIRED PUBLISHER CDATA #REQUIRED >