Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 57321 - mdadm --monitor mode is not used
Summary: mdadm --monitor mode is not used
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal enhancement (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
: 78451 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-07-16 12:53 UTC by Remy Blank
Modified: 2005-03-01 15:33 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Init script to start mdadm in monitor mode (mdadm,847 bytes, text/plain)
2004-07-16 12:55 UTC, Remy Blank
Details
Init file to start mdadm in monitor mode (mdadm,825 bytes, text/plain)
2004-07-16 17:06 UTC, Remy Blank
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Remy Blank 2004-07-16 12:53:57 UTC
I use mdadm for raid administration. On my previous RH8 install, I had a service that was started on boot to monitor the md devices through /proc/mdstat, and that sent an e-mail when something was wrong.

I couldn't find a boot script in the mdadm ebuild, so I quickly wrote one. It works on my machine, with 5 raid1 devices. It probably needs some cleaning by somebody who has written more than one Gentoo rc-script in his life, some testing, and could then be added to mdadm.
Comment 1 Remy Blank 2004-07-16 12:55:47 UTC
Created attachment 35593 [details]
Init script to start mdadm in monitor mode

Needs reviewing and testing.
Comment 2 Remy Blank 2004-07-16 17:06:33 UTC
Created attachment 35602 [details]
Init file to start mdadm in monitor mode

Oops, was a bit too quick. Changing the uid to nobody prevented sending events
as e-mail. Staying as root makes it work.
Comment 3 SpanKY gentoo-dev 2004-12-05 12:20:56 UTC
added to 1.8.1, thanks :)
Comment 4 SpanKY gentoo-dev 2005-03-01 15:33:48 UTC
*** Bug 78451 has been marked as a duplicate of this bug. ***