I believe "mdadm --detail" is better than "mdadm --examine"

Hello,

Since some time back, I get messages like these in the mdadm section
of my nightly logwatch mail.

    mdadm: cannot open /dev/md/1: No such file or directory
    /dev/md/1 : 

Now I've got around to investigate what actually is wrong.  And I
believe it is the use of the "mdadm" command in the services/mdadm
script.  In the absence of any /etc/mdadm.conf file, it uses the
command "mdadm --examine --scan" to find all devices.

The rules for naming of devices etc. in "mdadm" is not very obvious,
and not clearly explained in the manual pages as far as I can find.
So it took me a bit of googling.  But if I understand things
correctly, the "--examine" flag investigates partitions that are used
to make up a raid device, and makes a guess at what they will be
named.  In my case, this guess is wrong for one of my two RAID arrays.

I believe we rather would want to use the flag "--detail".  With that
flag, "mdadm" will report the names the arrays really got when
created.  See for example this comment in a Red Hat Bugzilla which
seems to be about a very similar case to ours:
https://bugzilla.redhat.com/show_bug.cgi?id=827240#c2

So I would suggest to change the command in the script in this way.
Does this make sense?

------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk