100 
 101 
 102        The prototype of the write access function for volatile property is:
 103 
 104          int write(ptree_warg_t *warg, const void *buf);
 105 
 106 
 107 
 108        The write function returns PICL_SUCCESS to indicate successful
 109        completion.
 110 
 111 
 112        For all volatile properties, the 'size' of the property must be
 113        specified to be the maximum possible size of the value. The maximum
 114        size of the value cannot exceed PICL_PROPSIZE_MAX. This allows a client
 115        to allocate a sufficiently large buffer before retrieving a volatile
 116        property's value
 117 
 118    Plug-in Modules
 119        Plug-in modules are shared objects that are located in well-known
 120        directories for the daemon to locate and load them. Plug-in module's
 121        are located in the one of the following plug-in directories depending
 122        on the plaform-specific nature of the data they collect and publish.
 123 
 124          /usr/platform/picl/plugins/`uname -i`/
 125          /usr/platform/picl/plugins/`uname -m`/
 126          /usr/lib/picl/plugins/
 127 
 128 
 129 
 130        A plug-in module may specify its dependency on another plug-in module
 131        using the -l linker option. The plug-ins are loaded by the PICL daemon
 132        using dlopen(3C) according to the specified dependencies. Each plug-in
 133        module must define a .init section, which is executed when the plug-in
 134        module is loaded, to register themselves with the daemon. See
 135        picld_plugin_register(3PICLTREE) for more information on plug-in
 136        registration.
 137 
 138 
 139        The plug-in modules may use the picld_log(3PICLTREE) function to log
 140        their messages to the system log file.
 141 
 142 ATTRIBUTES
 143        See attributes(5) for descriptions of the following attributes:
 144 
 145 
 146 
 147 
 148        +---------------+-----------------+
 149        |ATTRIBUTE TYPE | ATTRIBUTE VALUE |
 150        +---------------+-----------------+
 151        |MT-Level       | MT-Safe         |
 152        +---------------+-----------------+
 153 
 154 SEE ALSO
 155        libpicl(3PICL), libpicltree(3LIB), picld_log(3PICLTREE),
 156        picld_plugin_register(3PICLTREE), attributes(5)
 157 
 158 
 159 
 160                                  March 1, 2004          LIBPICLTREE(3PICLTREE)

 100 
 101 
 102        The prototype of the write access function for volatile property is:
 103 
 104          int write(ptree_warg_t *warg, const void *buf);
 105 
 106 
 107 
 108        The write function returns PICL_SUCCESS to indicate successful
 109        completion.
 110 
 111 
 112        For all volatile properties, the 'size' of the property must be
 113        specified to be the maximum possible size of the value. The maximum
 114        size of the value cannot exceed PICL_PROPSIZE_MAX. This allows a client
 115        to allocate a sufficiently large buffer before retrieving a volatile
 116        property's value
 117 
 118    Plug-in Modules
 119        Plug-in modules are shared objects that are located in well-known
 120        directories for the daemon to locate and load them. Plug-in modules are
 121        located in the one of the following plug-in directories depending on
 122        the platform-specific nature of the data they collect and publish.
 123 
 124          /usr/platform/picl/plugins/`uname -i`/
 125          /usr/platform/picl/plugins/`uname -m`/
 126          /usr/lib/picl/plugins/
 127 
 128 
 129 
 130        A plug-in module may specify its dependency on another plug-in module
 131        using the -l linker option. The plug-ins are loaded by the PICL daemon
 132        using dlopen(3C) according to the specified dependencies. Each plug-in
 133        module must define a .init section, which is executed when the plug-in
 134        module is loaded, to register themselves with the daemon. See
 135        picld_plugin_register(3PICLTREE) for more information on plug-in
 136        registration.
 137 
 138 
 139        The plug-in modules may use the picld_log(3PICLTREE) function to log
 140        their messages to the system log file.
 141 
 142 ATTRIBUTES
 143        See attributes(5) for descriptions of the following attributes:
 144 
 145 
 146 
 147 
 148        +---------------+-----------------+
 149        |ATTRIBUTE TYPE | ATTRIBUTE VALUE |
 150        +---------------+-----------------+
 151        |MT-Level       | MT-Safe         |
 152        +---------------+-----------------+
 153 
 154 SEE ALSO
 155        libpicl(3PICL), libpicltree(3LIB), picld_log(3PICLTREE),
 156        picld_plugin_register(3PICLTREE), attributes(5)
 157 
 158 
 159 
 160                                  May 16, 2020           LIBPICLTREE(3PICLTREE)