1picld(1M) System Administration Commands picld(1M)
2
6 picld - PICL daemon
7
9 /usr/lib/picl/picld
10
13 The Platform Information and Control Library (PICL) provides a mecha‐
14 nism to publish platform-specific information for clients to access in
15 a platform-independent way. picld maintains and controls access to the
16 PICL information from clients and plug-in modules. The daemon is
17 started in both single-user and multi-user boot mode.
18 Upon startup, the PICL daemon loads and initializes the plug-in mod‐
21 ules. These modules use the libpicltree(3PICLTREE) interface to create
22 nodes and properties in the PICL tree to publish platform configuration
23 information. After the plug-in modules are initialized, the daemon
24 opens the PICL daemon door to service client requests to access infor‐
25 mation in the PICL tree.
26 PICL Tree
28 The PICL tree is the repository of all the nodes and properties created
29 by the plug-in modules to represent the platform configuration. Every
30 node in the PICL tree is an instance of a well-defined PICL class. The
31 name of the base PICL class is picl, which defines a basic set of prop‐
32 erties that all nodes in the tree must possess. Two of those properties
33 are name and _class, where name contains the name of the node, and the
34 _class contains the PICL class name of the node. Certain nodes in the
35 PICL tree have well-known names. For example, the name of the root node
36 of the PICL tree is / and the name of the root node of the sub-tree
37 containing platform device nodes is platform.
38 PICL plug-in Modules
40 The PICL plug-in modules are shared objects that publish platform-spe‐
41 cific data in the PICL tree. They are located in well-known directories
42 so that the daemon can locate and load them.
43 Plug-in modules are located in one of the following plug-in directories
46 depending on the plaform-specific nature of the data that they collect
47 and publish:
48 /usr/platform/`uname -i`/lib/picl/plugins
50 /usr/platform/`uname -m`/lib/picl/plugins
51 A plug-in module can specify its dependency on another plug-in module
56 using the -l or -R linker option. The plug-ins are loaded by the daemon
57 using dlopen(3C) according to the specified dependencies. Each plug-in
58 module must define a .init section, which is executed when the plug-in
59 module is loaded, to register themselves with the daemon. See
60 picld_plugin_register(3PICLTREE) for additional information on plug-in
61 registration.
62 The plug-in modules use the libpicltree(3PICLTREE) interface to publish
65 nodes and properties in the PICL tree so that clients can access them.
66 When the PICL daemon invokes the initialization routine of the plug-in
69 module, the plug-in collects the platform information and creates nodes
70 and/or properties to represent the configuration in the PICL tree. A
71 plug-in can create additional threads to monitor the platform configu‐
72 ration and update the PICL tree with any changes. This enables a PICL
73 plug-in to operate as a daemon within the PICL framework.
74 An environmental monitor is an example of a plug-in module that uses a
77 thread to monitor the temperatures and fan speeds of the platform, then
78 publishes the environmental information in the PICL tree so clients can
79 access them.
80 Clients use the libpicl(3PICL) interface to send requests to picld for
83 accessing the PICL tree.
84
86 picld does not return an exit status.
87
89 /var/run/picld_door PICL daemon door
90 /usr/lib/picl/picld PICL daemon
93
96 See attributes(5) for descriptions of the following attributes:
97 ┌─────────────────────────────┬─────────────────────────────┐
102 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
103 ├─────────────────────────────┼─────────────────────────────┤
104 │Availability │SUNWpiclu │
105 └─────────────────────────────┴─────────────────────────────┘
106
108 svcs(1), svcadm(1M), dlopen(3C), libpicl(3PICL), libpi‐
109 cltree(3PICLTREE), picld_log(3PICLTREE), picld_plugin_regis‐
110 ter(3PICLTREE), attributes(5), smf(5)
111
113 The picld service is managed by the service management facility,
114 smf(5), under the service identifier:
115 svc:/system/picl
117 Administrative actions on this service, such as enabling, disabling, or
122 requesting restart, can be performed using svcadm(1M). The service's
123 status can be queried using the svcs(1) command.
124SunOS 5.11 10 Aug 2004 picld(1M)