Re: Why "mdadm --monitor --program" sometimes only gives 2 command-line arguments to the program?

[Nagilum]

----- Message from [EMAIL PROTECTED] ---------
    Date: Sat, 5 Jan 2008 18:11:38 -0800 (PST)
    From: Hxsrmeng <[EMAIL PROTECTED]>

I hope the mdadm monitor function can pass all three command-line
arguments to my-script, including the name of the event, the name of the
md device and the name of a related device if relevant.

But my-script doesn't get the third one, which should be /dev/sda2. Is
this not "relevant"?

If I really need to know it's /dev/sda2 that fails, what can I do?

Kind regards,
Alex.


========================================================================
#    _  __          _ __     http://www.nagilum.org/ \n icq://69646724 #
#   / |/ /__ ____ _(_) /_ ____ _  [EMAIL PROTECTED] \n +491776461165 #
#  /    / _ `/ _ `/ / / // /  ' \  Amiga (68k/PPC): AOS/NetBSD/Linux   #
# /_/|_/\_,_/\_, /_/_/\_,_/_/_/_/   Mac (PPC): MacOS-X / NetBSD /Linux #
#           /___/     x86: FreeBSD/Linux/Solaris/Win2k  ARM9: EPOC EV6 #
========================================================================


----------------------------------------------------------------
cakebox.homeunix.net - all the machine one needs..

Since you have the array name (e.g. /dev/md1) you could run "mdadm -Q --detail /dev/md1" and parse the output or have a look at /proc/mdstat or /sys/block/md1/* .

pgpBy8N97tUkA.pgp
Description: PGP Digital Signature