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
<!— NVPAIR XML format specification Copyright 2001, 2012, Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Intended Use: An nvpair element is meant to be used in an SC_EVENT or SC_CALLBACK_REG element. —> <!— NVPAIR definition The NVPAIR is a name/value pair to represent arbitrary name/value combinations. It is intended to be a direct, generic, translation of the Oracle Solaris nvpair_t structure used by the sysevent framework. However, there is no type information associated with the name or the value (they are both arbitrary text) in this xml element. The NVPAIR consists simply of one NAME element and one or more VALUE elements. One VALUE element represents a scalar value, while multiple represent an array VALUE. ATTRIBUTES: CONTENTS: SUBELEMENTS: NAME(1), VALUE(1 or more) —> <!ELEMENT NVPAIR (NAME,VALUE+)> <!— NAME definition The NAME is simply an arbitrary length string. ATTRIBUTES: CONTENTS: Arbitrary text data. Should be wrapped with <![CDATA[...]]> to prevent XML parsing inside. —> <!ELEMENT NAME (#PCDATA)> <!— VALUE definition The VALUE is simply an arbitrary length string. ATTRIBUTES: CONTENTS: Arbitrary text data. Should be wrapped with <![CDATA[...]]> to prevent XML parsing inside. —> <!ELEMENT VALUE (#PCDATA)>