{ "content": [ { "type": "text", "text": "# dbus-monitor (man)\n\n## NAME\n\ndbus-monitor - debug probe to print message bus messages\n\n## SYNOPSIS\n\ndbus-monitor [--system | --session | --address ADDRESS] [--profile | --monitor | --pcap |\n--binary] [watch expressions]\n\n## DESCRIPTION\n\nThe dbus-monitor command is used to monitor messages going through a D-Bus message bus. See\n\u001b[34mhttp://www.freedesktop.org/software/dbus/ for more information about the big picture.\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **OPTIONS** (5 subsections)\n- **EXAMPLE**\n- **AUTHOR**\n- **BUGS**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "dbus-monitor", "section": "", "mode": "man", "summary": "dbus-monitor - debug probe to print message bus messages", "synopsis": "dbus-monitor [--system | --session | --address ADDRESS] [--profile | --monitor | --pcap |\n--binary] [watch expressions]", "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [ { "flag": "", "long": "--system", "arg": null, "description": "Monitor the system message bus." }, { "flag": "", "long": "--session", "arg": null, "description": "Monitor the session message bus. (This is the default.)" }, { "flag": "", "long": "--address", "arg": "ADDRESS", "description": "Monitor an arbitrary message bus given at ADDRESS." }, { "flag": "", "long": "--profile", "arg": null, "description": "Use the profiling output format." }, { "flag": "", "long": "--monitor", "arg": null, "description": "Use the monitoring output format. (This is the default.)" } ], "examples": [ "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'\"" ], "see_also": [], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 4, "subsections": [] }, { "name": "DESCRIPTION", "lines": 28, "subsections": [] }, { "name": "OPTIONS", "lines": 1, "subsections": [ { "name": "--system", "lines": 2, "long": "--system" }, { "name": "--session", "lines": 2, "long": "--session" }, { "name": "--address ADDRESS", "lines": 2, "long": "--address", "arg": "ADDRESS" }, { "name": "--profile", "lines": 2, "long": "--profile" }, { "name": "--monitor", "lines": 2, "long": "--monitor" } ] }, { "name": "EXAMPLE", "lines": 6, "subsections": [] }, { "name": "AUTHOR", "lines": 3, "subsections": [] }, { "name": "BUGS", "lines": 4, "subsections": [] } ], "sections": { "NAME": { "content": "dbus-monitor - debug probe to print message bus messages\n", "subsections": [] }, "SYNOPSIS": { "content": "dbus-monitor [--system | --session | --address ADDRESS] [--profile | --monitor | --pcap |\n--binary] [watch expressions]\n\n", "subsections": [] }, "DESCRIPTION": { "content": "The dbus-monitor command is used to monitor messages going through a D-Bus message bus. See\n\u001b[34mhttp://www.freedesktop.org/software/dbus/ for more information about the big picture.\n\nThere are two well-known message buses: the systemwide message bus (installed on many systems\nas the \"messagebus\" service) and the per-user-login-session message bus (started each time a\nuser logs in). The --system and --session options direct dbus-monitor to monitor the system\nor session buses respectively. If neither is specified, dbus-monitor monitors the session\nbus.\n\ndbus-monitor has two different text output modes: the 'classic'-style monitoring mode, and\nprofiling mode. The profiling format is a compact format with a single line per message and\nmicrosecond-resolution timing information. The --profile and --monitor options select the\nprofiling and monitoring output format respectively.\n\ndbus-monitor also has two binary output modes. The binary mode, selected by --binary, outputs\nthe entire binary message stream (without the initial authentication handshake). The PCAP\nmode, selected by --pcap, adds a PCAP file header to the beginning of the output, and\nprepends a PCAP message header to each message; this produces a binary file that can be read\nby, for instance, Wireshark.\n\nIf no mode is specified, dbus-monitor uses the monitoring output format.\n\nIn order to get dbus-monitor to see the messages you are interested in, you should specify a\nset of watch expressions as you would expect to be passed to the dbusbusaddmatch function.\n\nThe message bus configuration may keep dbus-monitor from seeing all messages, especially if\nyou run the monitor as a non-root user.\n", "subsections": [] }, "OPTIONS": { "content": "", "subsections": [ { "name": "--system", "content": "Monitor the system message bus.\n", "long": "--system" }, { "name": "--session", "content": "Monitor the session message bus. (This is the default.)\n", "long": "--session" }, { "name": "--address ADDRESS", "content": "Monitor an arbitrary message bus given at ADDRESS.\n", "long": "--address", "arg": "ADDRESS" }, { "name": "--profile", "content": "Use the profiling output format.\n", "long": "--profile" }, { "name": "--monitor", "content": "Use the monitoring output format. (This is the default.)\n", "long": "--monitor" } ] }, "EXAMPLE": { "content": "Here is an example of using dbus-monitor to watch for the gnome typing monitor to say things\n\n\ndbus-monitor \"type='signal',sender='org.gnome.TypingMonitor',interface='org.gnome.TypingMonitor'\"\n\n", "subsections": [] }, "AUTHOR": { "content": "dbus-monitor was written by Philip Blundell. The profiling output mode was added by Olli\nSalli.\n", "subsections": [] }, "BUGS": { "content": "Please send bug reports to the D-Bus mailing list or bug tracker, see\n\u001b[34mhttp://www.freedesktop.org/software/dbus/\n\nD-Bus 1.14.10 DBUS-MONITOR(1)", "subsections": [] } } } }