From: Wols Lists <antlists@youngman.org.uk>
To: Leslie Rhorer <lesrhorer@att.net>, linux-raid@vger.kernel.org
Subject: Re: checkarray not running or emailing
Date: Wed, 11 Mar 2020 12:17:29 +0000 [thread overview]
Message-ID: <5E68D6D9.5040004@youngman.org.uk> (raw)
In-Reply-To: <0ef54c89-b486-eb0b-8d70-a043ef089c9f@att.net>
On 11/03/20 01:11, Leslie Rhorer wrote:
> Is there seriously no one here who knows how checkarray was launched
> in previous versions?
You need to ask on a Debian list. I for one don't have a damn clue
because I actively avoid apt-based systems.
Sorry, I don't mean to be harsh, but each distro "does its own thing" so
a lot of people (like me) *will* be clueless on that point, even if we
are raid experts.
Cheers,
Wol
>
> On 3/1/2020 3:03 PM, Leslie Rhorer wrote:
>> I have upgraded 2 of my servers to Debian Buster, and now neither
>> one seems to be running checkarray automatically. In addition, when I
>> run checkarray manually, it isn't sending update emails on the status
>> of the job. Actually, I have never been able to figure out how
>> checkarray runs. One my older servers, there doesn't seem to be
>> anything in /etc/crontab, /etc/cron.monthly, /etc/init.d/,
>> /etc/mdadm/mdadm.conf, or /lib/systemd/system/ that would run checkarray.
next prev parent reply other threads:[~2020-03-11 12:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <814aad65-fba3-334c-c4df-6b8f4bfc4193.ref@att.net>
2020-03-01 21:03 ` checkarray not running or emailing Leslie Rhorer
2020-03-11 1:11 ` Leslie Rhorer
2020-03-11 12:17 ` Wols Lists [this message]
2020-03-12 1:17 ` Leslie Rhorer
2020-03-11 12:50 ` Brad Campbell
2020-03-12 1:41 ` Leslie Rhorer
2020-03-12 4:53 ` Ram Ramesh
2020-03-13 0:24 ` Leslie Rhorer
2020-03-12 9:17 ` Brad Campbell
2020-03-13 0:13 ` Leslie Rhorer
2020-03-13 16:53 ` Brad Campbell
2020-03-15 11:11 ` Leslie Rhorer
2020-03-11 13:18 ` Robin Hill
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=5E68D6D9.5040004@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=lesrhorer@att.net \
--cc=linux-raid@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).