chudremotectrl(1) [osx man page]

CHUDREMOTECTRL(1)					      General Commands Manual						 CHUDREMOTECTRL(1)

NAME

       chudRemoteCtrl - start or stop the collection of performance monitor data in a performance monitor remote server application.

SYNOPSIS

       chudRemoteCtrl [ -m ] [ executable [args... ] ]

       chudRemoteCtrl -s label

       chudRemoteCtrl -e

       chudRemoteCtrl -k PID

DESCRIPTION

       chudRemoteCtrl is a command line tool that allows for the collection of performance data by any active performance monitor remote server
       application. There are currently two CHUD Tools that can be put in remote performance monitor server mode: MONster, and Shark (as well as
       their command line counterparts). Typically, chudRemoteCtrl is invoked on the command line or in a shell script, followed by the path to an
       executable to be measured and its arguments.  chudRemoteCtrl issues a chudStartRemotePerfMonitor message immediately after launching the
       specified target program. When the launched program terminates, chudRemoteCtrl issues a chudStopRemotePerfMonitor message, and then exits.
       When the '-s', '-e' or '-k PID' options are used, no program is launched.

OPTIONS

       -r     seconds: If the 'chudStartRemotePerfMonitor' message fails to either acquire or start the remote monitoring service, then keep try-
	      ing to start again, until the specified number of seconds has elapsed.  The same thing is true of the '-e' option. If there is a '-r
	      <seconds>' argument on the command line, and a failure occurs trying to stop the remote profiling program, the stop message will be
	      sent again until the retry time limit is reached.

       -s     label: Issue a chudStartRemotePerfMonitor message with the specified label and exit. A 'label' is a string of up to 32 characters.

       -e     Issue a chudStopRemotePerfMonitor message and exit.

       -q     silence some of the non-essential warning and error output.

       -kPID  Send a UNIX signal (SIGUSR1 to start profiling, SIGUSR2 to stop profiling) to the specified process-id. For example, if a command-
	      line profiling tool, is running as PID 4267, using '-k 4267' along with a '-s' will send a SIGUSR1 to the command-line profiling
	      tool and it will start sampling, while '-k 4267' along with a '-e' will send a SIGUSR2 to the command-line profiling tool and it
	      will stop sampling. A 'start' example: % chudRemoteCtrl -s session_42 -k 4267.  And a 'stop' example: % chudRemoteCtrl -e -k 4267.
	      The command-line CHUD tool 'shark' responds to UNIX signals and toggles performance profiling.  You can repeatedly send '-s <label>
	      -k <PID#>' to shark and it will toggle profiling start or stop.  Sending '-e -k <PID#>' to shark will stop sampling (if it's run-
	      ning) and cause shark to EXIT.

       -m     Set the performance monitor mark bit in the main thread of the launched child process.

DIAGNOSTICS

       chudRemoteCtrl returns a zero (0) upon success and a non-zero value on failure.

BUGS

       Please send your comments, suggestions and bug reports to: perftools-feedback@group.apple.com

SEE ALSO

       monster(1), shark(1)

CHUD
								  6 October 2003						 CHUDREMOTECTRL(1)

Check Out this Related 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)

Linux and UNIX Man Pages

chudremotectrl(1) [osx man page]

Check Out this Related Man Page