Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

obus-introspect(1) [debian man page]

OBUS-INTROSPECT(1)					      General Commands Manual						OBUS-INTROSPECT(1)

obus-introspect - a D-Bus introspecter SYNOPSIS
obus-intrpsoect [ options ] destination path DESCRIPTION
obus-introspect allow you to introspect a D-Bus service. Given a path it can introspect recursively all its children. By default it prints only all the interfaces it found, but it can also prints all object path with the interfaces they implements. OPTIONS
-rec Introspects recursively all sub-nodes instead of just the one of path path -session The service is on the session bus (the default). -system The service is on the system bus. -objects List objects with interfaces they implements instead of interfaces. -help or --help Display a short usage summary and exit. AUTHOR
Jeremie Dimino <> SEE ALSO
obus-dump(1), obus-binder(1). October 2009 OBUS-INTROSPECT(1)

Check Out this Related Man Page

dbus-send(1)						      General Commands Manual						      dbus-send(1)

dbus-send - Send a message to a message bus SYNOPSIS
dbus-send [--system | --session] [--dest=NAME] [--print-reply] [--type=TYPE] <destination object path> <message name> [contents ...] DESCRIPTION
The dbus-send command is used to send a message to a D-Bus message bus. See for more information about the big picture. There are two well-known message buses: the systemwide message bus (installed on many systems as the "messagebus" service) and the per- user-login-session message bus (started each time a user logs in). The --system and --session options direct dbus-send to send messages to the system or session buses respectively. If neither is specified, dbus-send sends to the session bus. Nearly all uses of dbus-send must provide the --dest argument which is the name of a connection on the bus to send the message to. If --dest is omitted, no destination is set. The object path and the name of the message to send must always be specified. Following arguments, if any, are the message contents (mes- sage arguments). These are given as type-specified values and may include containers (arrays, dicts, and variants) as described below. <contents> ::= <item> | <container> [ <item> | <container>...] <item> ::= <type>:<value> <container> ::= <array> | <dict> | <variant> <array> ::= array:<type>:<value>[,<value>...] <dict> ::= dict:<type>:<type>:<key>,<value>[,<key>,<value>...] <variant> ::= variant:<type>:<value> <type> ::= string | int16 | uint 16 | int32 | uint32 | int64 | uint64 | double | byte | boolean | objpath D-Bus supports more types than these, but dbus-send currently does not. Also, dbus-send does not permit empty containers or nested con- tainers (e.g. arrays of variants). Here is an example invocation: dbus-send --dest=org.freedesktop.ExampleName /org/freedesktop/sample/object/name org.freedesktop.ExampleInterface.ExampleMethod int32:47 string:'hello world' double:65.32 array:string:"1st item","next item","last item" dict:string:int32:"one",1,"two",2,"three",3 variant:int32:-8 objpath:/org/freedesktop/sample/object/name Note that the interface is separated from a method or signal name by a dot, though in the actual protocol the interface and the interface member are separate fields. OPTIONS
The following options are supported: --dest=NAME Specify the name of the connection to receive the message. --print-reply Block for a reply to the message sent, and print any reply received. --system Send to the system message bus. --session Send to the session message bus. (This is the default.) --type=TYPE Specify "method_call" or "signal" (defaults to "signal"). AUTHOR
dbus-send was written by Philip Blundell. BUGS
Please send bug reports to the D-Bus mailing list or bug tracker, see dbus-send(1)
Man Page

Featured Tech Videos