1ohhandler(1)                        OpenHPI                       ohhandler(1)
2
3
4

NAME

6       ohhandler - An openhpi sample application that uses the openhpi
7       additional interfaces to control openhpi configuration. That is plugins
8       can be loaded, plugin instances (handlers) created, unloaded or their
9       configuration displayed.
10

SYNOPSIS

12        ohhandler [-D nn] [-N host[:port]] [-C <cfgfile>] [-X] command <specific arguments>
13        ohhandler [--domain nn] [--host=host[:port]] [--cfgfile=file] [--debug] command <specific arguments>
14
15        ohhandler [-D nn] [-X] list
16        ohhandler [-D nn] [-X] info    <handler-id>
17        ohhandler [-D nn] [-X] destroy <handler-id>
18        ohhandler [-D nn] [-X] getnext <handler-id>
19        ohhandler [-D nn] [-X] find    <resource-id>
20        ohhandler [-D nn] [-X] retry   <handler-id>
21        ohhandler [-D nn] [-X] create  plugin <plugin-name> <configuration-parameters>
22

DESCRIPTION

24       ohhandler list will display a list of all plugin instances (handlers)
25       currently defined in the openhpi daemon for the specified domain. Part
26       of the output is the handler-id that can be used in subsequent
27       commands.
28
29       ohhandler info will display specific info for the handler with the
30       specified id. This information includes all configuration parameters of
31       the handler as specified in the openhpi.conf file or as dynamically
32       defined during a "ohhandler create" call.
33
34       ohhandler destroy will unload the specified handler and delete all its
35       configuration information.
36
37       ohhandler getnext will allows to walk through all hanlers currently
38       defined in the openhpi daemon for the specified domain.
39
40       ohhandler find will find the handler that is managing the specified
41       resource.
42
43       ohhandler retry allows to try again to load and initialize the
44       specified handler.
45
46       ohhandler create allows to dynamically create a new handler with
47       configuration parameters like they are specified in the openhpi.conf
48       file.
49        - The type of plugin is specified with the keyword plugin
50        - Configuration parameters should follow as name value pairs
51        - Complex strings like entity paths must be enclosed with ""
52        Example:
53        ohhandler create plugin libsimulator entity_root "{SYSTEM_CHASSIS,1}"
54       name sim
55
56       If no domain or host is selected, ohhandler uses the default domain as
57       specified in the openhpiclient.conf file.
58

OPTIONS

60   Help Options:
61       -h, --help
62         Show help options
63
64   Application Options:
65       -D nn, --domain=nn
66         Select domain id nn
67
68       -X, --debug
69         Display debug messages
70
71       -N "host[:port]", --host="host[:port]"
72         Open session to the domain served by the daemon at the specified URL
73         (host:port).  This option overrides the OPENHPI_DAEMON_HOST and
74         OPENHPI_DAEMON_PORT environment variables.  If host contains ':' (for
75         example IPv6 address) then enclose it in square brackets.  For
76         example: "[::1]" or "[::1]:4743".
77
78       -C "file", --cfgfile="file"
79         Use passed file as client configuration file.  This option overrides
80         the OPENHPICLIENT_CONF environment variable.
81

SEE ALSO

83                hpi_shell
84
85                hpialarms      hpifan         hpipower       hpithres
86                hpidomain      hpigensimdata  hpireset       hpitop
87                hpiel          hpiiinv        hpisensor      hpitree
88                hpievents      hpionIBMblade  hpisettime     hpiwdt
89                hpixml
90                ohdomainlist   ohparam
91

AUTHORS

93       Authors of this man page:
94
95        Ulrich Kleber (ulikleber@users.sourceforge.net)
96        Anton Pak (avpak@users.sourceforge.net)
97
98
99
1003.8.0                             2017-05-27                      ohhandler(1)