All of lore.kernel.org
 help / color / mirror / Atom feed
From: Farkas Levente <lfarkas@bnap.hu>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm never notify, grub cause fault
Date: Mon, 19 May 2003 08:06:19 +0200	[thread overview]
Message-ID: <3EC8745B.9010106@bnap.hu> (raw)
In-Reply-To: <16072.17850.938484.250446@notabene.cse.unsw.edu.au>

Neil Brown wrote:
> On Friday May 16, Paul.Clements@SteelEye.com wrote:
> 
>>Juri Haberland wrote:
>> 
>>
>>>I also ran into this problem. I found the reason when I started mdadm
>>>without '--daemonize': It tries to use '/usr/lib/sendmail' whereas most
>>>recent distributions have sendmail (or it's replacement) in /usr/sbin.
>>>So just create a link from /usr/sbin/sendmail to /usr/lib/sendmail and it
>>>should work.
>>
>>I was wondering myself how mdadm sent e-mail...sounds like there might
>>be a need for a new "MAILPROG" entry in mdadm.conf...
>>
> 
> 
> There is a compile-time option which I have just made more explicit in
> the Makefile.  
> If you add:
>    -DSendmail=\""/usr/sbin/sendmail -t"\"
> to the CFLAGS line in the makefile you will change how mail is sent by
> default.
> 
> If you want runtime configuration, I would rather just leave the
> PROGRAM entry and you and write a script to do whatever you like.
> 
> I'm thinking of causing the "NewArray" alert to 
>  - be generate for all arrays at start time
>  - contain an indication of whether the array is degraded
>  - cause email to be sent if the array is degraded.
> 
> Thus you will get an alert of a failed drive when the mdadm --monitor
> is started.

the above are generated every every time when --monitor started? that 
would be nice!

-- 
   Levente                               "Si vis pacem para bellum!"



  reply	other threads:[~2003-05-19  6:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16  9:21 mdadm never notify, grub cause fault Farkas Levente
2003-05-16 17:45 ` Juri Haberland
2003-05-16 17:57   ` Paul Clements
2003-05-19  2:47     ` Neil Brown
2003-05-19  6:06       ` Farkas Levente [this message]
2003-05-21  1:38         ` Neil Brown
2003-05-21  9:05           ` Farkas Levente
2003-05-22  0:36             ` Neil Brown
     [not found]       ` <3EC8B398.8090702@koschikode.com>
2003-05-19 11:25         ` Neil Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3EC8745B.9010106@bnap.hu \
    --to=lfarkas@bnap.hu \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.