| 2010-03-09 23:54:50 |
ceg |
bug |
|
|
added bug |
| 2010-03-09 23:56:58 |
ceg |
summary |
mdadm monitor feature is disabled, not depending on local MTA/MDA or wall/notify-send |
mdadm monitor feature broken, not depending on local MTA/MDA or using wall/notify-send |
|
| 2010-03-09 23:59:24 |
ceg |
description |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enogh abbout redundacy to want being notified if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As notifying a human is a serious data protection topic mdadm should depend on a package providing at least local mail services or use wall/notify-send to get the message out. |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use wall/notify-send to get the message out.
|
|
| 2010-03-10 04:15:08 |
Jeremy Foshee |
tags |
|
kernel-series-unknown |
|
| 2010-03-10 06:11:54 |
Jeremy Foshee |
tags |
kernel-series-unknown |
|
|
| 2010-03-24 18:36:46 |
ceg |
mdadm (Ubuntu): status |
New |
Confirmed |
|
| 2010-03-29 13:52:23 |
ceg |
description |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use wall/notify-send to get the message out.
|
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If none of the large MTAs is installed, yes mdadm should pull in a replacement like esmtp + procmail but no postfix on desktops.
|
|
| 2010-03-29 14:01:00 |
ceg |
description |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If none of the large MTAs is installed, yes mdadm should pull in a replacement like esmtp + procmail but no postfix on desktops.
|
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If none of the large MTAs is installed, yes mdadm should pull in (require) a replacement like esmtp + procmail but no postfix on desktops.
|
|
| 2010-04-14 14:45:22 |
ceg |
summary |
mdadm monitor feature broken, not depending on local MTA/MDA or using wall/notify-send |
mdadm monitor feature broken, not depending on local MTA/MDA nor using beep/wall/notify-send |
|
| 2010-04-14 14:46:40 |
ceg |
description |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If none of the large MTAs is installed, yes mdadm should pull in (require) a replacement like esmtp + procmail but no postfix on desktops.
|
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If none of the large MTAs is installed, yes mdadm should pull in (require) a replacement like esmtp + procmail but no postfix on desktops.
|
|
| 2010-04-26 06:44:49 |
ceg |
summary |
mdadm monitor feature broken, not depending on local MTA/MDA nor using beep/wall/notify-send |
mdadm monitor feature broken, email notification not set up, nor using beep/wall/notify-send |
|
| 2010-04-26 06:46:47 |
ceg |
description |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If none of the large MTAs is installed, yes mdadm should pull in (require) a replacement like esmtp + procmail but no postfix on desktops.
|
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one, maybe a replacement like esmtp + procmail (if they are supported) but not postfix on desktops.
|
|
| 2010-08-06 17:59:13 |
Paul Chaplin |
bug |
|
|
added subscriber Paul Chaplin |
| 2011-10-17 21:13:23 |
alfonso |
bug |
|
|
added subscriber alfonso |
| 2012-01-13 17:20:16 |
madbiologist |
bug |
|
|
added subscriber madbiologist |
| 2012-11-28 09:36:00 |
ceg |
description |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one, maybe a replacement like esmtp + procmail (if they are supported) but not postfix on desktops.
|
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one, maybe a replacement like esmtp + procmail (if they are supported) but not postfix on desktops.
---
Workaround to set up local delivery for email send to "root" (to a user mailbox in /var/mail):
#apt-get install esmtp-run procmail
#echo mda=\'/usr/bin/formail -a \"Date: \`date -R\`\" \| /usr/bin/procmail -d %T\' >> /etc/esmtprc
#echo "root: <your-user-name>" >> /etc/alias
#newaliases |
|
| 2012-11-28 09:36:51 |
ceg |
description |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one, maybe a replacement like esmtp + procmail (if they are supported) but not postfix on desktops.
---
Workaround to set up local delivery for email send to "root" (to a user mailbox in /var/mail):
#apt-get install esmtp-run procmail
#echo mda=\'/usr/bin/formail -a \"Date: \`date -R\`\" \| /usr/bin/procmail -d %T\' >> /etc/esmtprc
#echo "root: <your-user-name>" >> /etc/alias
#newaliases |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one, maybe a replacement like esmtp + procmail (if they are supported) but not postfix on desktops.
---
Workaround to set up local delivery for email send to "root" (to a user mailbox in /var/mail):
#apt-get install esmtp-run procmail
#echo mda=\'/usr/bin/formail -a \"Date: \`date -R\`\" \| /usr/bin/procmail -d %T\' >> /etc/esmtprc
#echo "root: <YOUR-USER-NAME-HERE>" >> /etc/alias
#newaliases |
|
| 2012-11-28 09:44:51 |
ceg |
description |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one, maybe a replacement like esmtp + procmail (if they are supported) but not postfix on desktops.
---
Workaround to set up local delivery for email send to "root" (to a user mailbox in /var/mail):
#apt-get install esmtp-run procmail
#echo mda=\'/usr/bin/formail -a \"Date: \`date -R\`\" \| /usr/bin/procmail -d %T\' >> /etc/esmtprc
#echo "root: <YOUR-USER-NAME-HERE>" >> /etc/alias
#newaliases |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one, maybe a replacement like esmtp + procmail (if they are supported) but not postfix on desktops.
---
Workaround to set up local delivery for email send to "root" (to a user mailbox in /var/mail):
#apt-get install esmtp-run procmail
#echo mda=\'/usr/bin/formail -a \"Date: \`date -R\`\" \| /usr/bin/procmail -d %T\' >> /etc/esmtprc
#echo "root: <YOUR-USER-NAME-HERE>" >> /etc/aliases
#newaliases |
|
| 2012-11-28 10:48:43 |
ceg |
description |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one, maybe a replacement like esmtp + procmail (if they are supported) but not postfix on desktops.
---
Workaround to set up local delivery for email send to "root" (to a user mailbox in /var/mail):
#apt-get install esmtp-run procmail
#echo mda=\'/usr/bin/formail -a \"Date: \`date -R\`\" \| /usr/bin/procmail -d %T\' >> /etc/esmtprc
#echo "root: <YOUR-USER-NAME-HERE>" >> /etc/aliases
#newaliases |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one. However, maybe a small replacement like esmtp + procmail (if they are supported) instead of postfix on desktops.
---
Workaround to manually set up local delivery for email send to "root":
#apt-get install postfix procmail
# (choose to configure for local use only)
#echo "root: <YOUR-USER-NAME-HERE>" >> /etc/aliases
#newaliases
#mdadm --monitor /dev/md0 --test
#^C
Then set up an mail program or to check for email in your local mailbox (/var/mail/<YOUR-USER-NAME-HERE>). |
|
| 2012-11-28 10:49:21 |
ceg |
description |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one. However, maybe a small replacement like esmtp + procmail (if they are supported) instead of postfix on desktops.
---
Workaround to manually set up local delivery for email send to "root":
#apt-get install postfix procmail
# (choose to configure for local use only)
#echo "root: <YOUR-USER-NAME-HERE>" >> /etc/aliases
#newaliases
#mdadm --monitor /dev/md0 --test
#^C
Then set up an mail program or to check for email in your local mailbox (/var/mail/<YOUR-USER-NAME-HERE>). |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one. However, maybe a small replacement like esmtp + procmail (if they are supported) instead of postfix on desktops.
---
Workaround to manually set up local delivery for email send to "root":
#apt-get install postfix procmail
# (choose to configure for local use only)
#echo "root: <YOUR-USER-NAME-HERE>" >> /etc/aliases
#newaliases
#mdadm --monitor /dev/md0 --test
#^C
Then set up an mail program to check for email in your local mailbox (/var/mail/<YOUR-USER-NAME-HERE>). |
|
| 2012-11-28 10:57:23 |
ceg |
description |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu system support no local mail and mdadm package was patched to suppress the debconf email question, without setting up mdadm --monitor to use wall or notify-send as an alternative.
As informing a human is a serious data protection topic mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one. However, maybe a small replacement like esmtp + procmail (if they are supported) instead of postfix on desktops.
---
Workaround to manually set up local delivery for email send to "root":
#apt-get install postfix procmail
# (choose to configure for local use only)
#echo "root: <YOUR-USER-NAME-HERE>" >> /etc/aliases
#newaliases
#mdadm --monitor /dev/md0 --test
#^C
Then set up an mail program to check for email in your local mailbox (/var/mail/<YOUR-USER-NAME-HERE>). |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu systems do not support local mail, and the mdadm package was patched to suppress the installation of an MTA/MDA (only if installed during the initial installation Bug #379882 ), without adapting mdadm --monitor to use "wall" or "notify-send" as a replacement.
As informing a human is a serious data protection topic, mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one, maybe a replacement like esmtp + procmail (if they are supported) but not postfix on desktops. |
|
| 2012-11-28 11:04:20 |
ceg |
description |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu systems do not support local mail, and the mdadm package was patched to suppress the installation of an MTA/MDA (only if installed during the initial installation Bug #379882 ), without adapting mdadm --monitor to use "wall" or "notify-send" as a replacement.
As informing a human is a serious data protection topic, mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one, maybe a replacement like esmtp + procmail (if they are supported) but not postfix on desktops. |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu systems do not support local mail, and the mdadm package was patched to suppress the installation of an MTA/MDA (only if installed during the initial installation Bug #379882 ), without adapting mdadm --monitor to use "wall" or "notify-send" as a replacement.
As informing a human is a serious data protection topic, mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one.
However, maybe a small replacement like esmtp + procmail (if they are
supported) instead of postfix on desktops.
---
Workaround to manually set up local delivery for email send to "root":
#apt-get install postfix procmail
# (choose to configure for local use only)
#echo "root: <YOUR-USER-NAME-HERE>" >> /etc/aliases
#newaliases
#mdadm --monitor /dev/md0 --test
#^C
Then set up an mail program or to check for email in your local mailbox
(/var/mail/<YOUR-USER-NAME-HERE>). |
|
| 2012-12-11 12:57:36 |
ceg |
description |
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu systems do not support local mail, and the mdadm package was patched to suppress the installation of an MTA/MDA (only if installed during the initial installation Bug #379882 ), without adapting mdadm --monitor to use "wall" or "notify-send" as a replacement.
As informing a human is a serious data protection topic, mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one.
However, maybe a small replacement like esmtp + procmail (if they are
supported) instead of postfix on desktops.
---
Workaround to manually set up local delivery for email send to "root":
#apt-get install postfix procmail
# (choose to configure for local use only)
#echo "root: <YOUR-USER-NAME-HERE>" >> /etc/aliases
#newaliases
#mdadm --monitor /dev/md0 --test
#^C
Then set up an mail program or to check for email in your local mailbox
(/var/mail/<YOUR-USER-NAME-HERE>). |
Binary package hint: mdadm
Anybody who cares enough about redundancy to use mdadm probably cares enough to want getting informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu systems do not support local mail, and the mdadm package was patched to suppress the installation of an MTA/MDA (only if installed during the initial installation Bug #379882 ), without adapting mdadm --monitor to use "wall" or "notify-send" as a replacement.
As informing a human is a serious data protection topic, mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one.
However, maybe a small replacement like esmtp + procmail (if they are
supported) instead of postfix on desktops.
---
Workaround to manually set up local delivery for email send to "root":
#apt-get install postfix procmail
# (choose to configure for local use only)
#echo "root: <YOUR-USER-NAME-HERE>" >> /etc/aliases
#newaliases
#mdadm --monitor /dev/md0 --test
#^C
Then set up an mail program or to check for email in your local mailbox
(/var/mail/<YOUR-USER-NAME-HERE>). |
|
| 2012-12-11 13:00:14 |
ceg |
description |
Binary package hint: mdadm
Anybody who cares enough about redundancy to use mdadm probably cares enough to want getting informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu systems do not support local mail, and the mdadm package was patched to suppress the installation of an MTA/MDA (only if installed during the initial installation Bug #379882 ), without adapting mdadm --monitor to use "wall" or "notify-send" as a replacement.
As informing a human is a serious data protection topic, mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one.
However, maybe a small replacement like esmtp + procmail (if they are
supported) instead of postfix on desktops.
---
Workaround to manually set up local delivery for email send to "root":
#apt-get install postfix procmail
# (choose to configure for local use only)
#echo "root: <YOUR-USER-NAME-HERE>" >> /etc/aliases
#newaliases
#mdadm --monitor /dev/md0 --test
#^C
Then set up an mail program or to check for email in your local mailbox
(/var/mail/<YOUR-USER-NAME-HERE>). |
Binary package hint: mdadm
Anybody who cares enough about redundancy to use mdadm probably cares enough to want getting informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm asks for a mail address to notify during mdadm install.
By default ubuntu systems do not support local mail, and the mdadm package was patched to suppress the installation of an MTA/MDA (only if installed during the initial installation Bug #379882 ), without adapting mdadm --monitor to use "wall" or "notify-send" as a replacement.
As informing a human is a serious data protection topic, mdadm should depend on a package providing at least local mail services and/or use beep/wall/notify-send to get the message out.
---
The monitoring facility of mdadm is very important to get notice if somthing goes wrong with your raid.
So you can replace disks etc. ahead of a total failure.
To send out notifications mdadm needs a sendmail command (MTA mail transport agent ).
To deliver mail localy you need a mail delivery agent (MDA)
Things like exim, postfix open network ports and are large and not easy to configure, but of course provide the sendmail command and delivery.
If no MTA/MDA is installed, yes mdadm should pull in (require) one.
However, maybe a small replacement like esmtp + procmail (if they are
supported) instead of postfix on desktops.
---
Workaround to manually set up local delivery for email send to "root":
#apt-get install postfix procmail
# (choose to configure for local use only)
#echo "root: <YOUR-USER-NAME-HERE>" >> /etc/aliases
#newaliases
#mdadm --monitor /dev/md0 --test
#^C
Then set up an mail program to check for email in your local mailbox
(/var/mail/<YOUR-USER-NAME-HERE>). |
|
| 2013-01-06 00:03:22 |
Hans Deragon |
bug |
|
|
added subscriber Hans Deragon |
| 2016-01-05 19:34:55 |
Till Ulen |
removed subscriber Alexander Konovalenko |
|
|
|
