dbus-monitor(1) [linux man page]

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

NAME

       dbus-monitor - debug probe to print message bus messages

SYNOPSIS

       dbus-monitor [--system | --session | --address ADDRESS] [--profile | --monitor] [watch expressions]

DESCRIPTION

       The  dbus-monitor command is used to monitor messages going through a D-Bus message bus.  See http://www.freedesktop.org/software/dbus/ 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-monitor to monitor
       the system or session buses respectively.  If neither is specified, dbus-monitor monitors the session bus.

       dbus-monitor has two different output modes, the 'classic'-style monitoring mode and profiling mode. The profiling format is a compact for-
       mat  with a single line per message and microsecond-resolution timing information. The --profile and --monitor options select the profiling
       and monitoring output format respectively. If neither is specified, dbus-monitor uses the monitoring output format.

       In order to get dbus-monitor to see the messages you are interested in, you should specify a set of watch expressions as you  would  expect
       to be passed to the dbus_bus_add_match function.

       The message bus configuration may keep dbus-monitor from seeing all messages, especially if you run the monitor as a non-root user.

OPTIONS

       --system
	      Monitor the system message bus.

       --session
	      Monitor the session message bus.	(This is the default.)

       --address ADDRESS
	      Monitor an arbitrary message bus given at ADDRESS.

       --profile
	      Use the profiling output format.

       --monitor
	      Use the monitoring output format.  (This is the default.)

EXAMPLE

       Here is an example of using dbus-monitor to watch for the gnome typing monitor to say things

	 dbus-monitor "type='signal',sender='org.gnome.TypingMonitor',interface='org.gnome.TypingMonitor'"

AUTHOR

       dbus-monitor was written by Philip Blundell.  The profiling output mode was added by Olli Salli.

BUGS

       Please send bug reports to the D-Bus mailing list or bug tracker, see http://www.freedesktop.org/software/dbus/

																   dbus-monitor(1)

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

NAME

       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 http://www.freedesktop.org/software/dbus/ 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 http://www.freedesktop.org/software/dbus/

																      dbus-send(1)