Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory how can I monitoring the LUNs in HP storage Post 77291 by TioTony on Wednesday 6th of July 2005 08:20:42 PM
Old 07-06-2005
I'm sorry but I don't understand exactly what you are looking for. Are you looking to monitor the luns on an HP VA or EVA? Or are looking to monitor the devices as the OS sees them?
 

2 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Storage Monitoring/Reporting?

Hi. How do you guys, monitor/report your Storage environment? I have people (don't we all? ) that like to have monthly reports on space (raw/assigned/available), ports available/used, switches and the such. Do you use anything special? Or are you like me, a nice big Excel spreadsheet? How... (1 Reply)
Discussion started by: Stephan
1 Replies

2. AIX

Migrating LUNs to new storage array

All, I have a AIX server with multiple volumes and I need to move them from a legacy storage SAN to a new SAN. We are concerned because to use mirrorvg as we would have to run on a single HBA (one on the old SAN and one on the new). Our other option is to use an appliance to do a block... (3 Replies)
Discussion started by: bkchicago
3 Replies
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)
All times are GMT -4. The time now is 11:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy