From: Phillip Susi <phill@thesusis.net>
To: Roman Mamedov <rm@romanrm.net>
Cc: "Kengo.M" <kengo@kyoto-arc.or.jp>, linux-btrfs@vger.kernel.org
Subject: Re: scrub results by email
Date: Tue, 13 Sep 2022 15:39:06 -0400 [thread overview]
Message-ID: <87o7vjyse8.fsf@vps.thesusis.net> (raw)
In-Reply-To: <20220913223009.11e1e549@nvm>
Roman Mamedov <rm@romanrm.net> writes:
> If you want to run a scheduled scrub from crontab, cron can be made to mail
> all output of all cron-issued commands to a designated E-Mail address. Add:
>
> MAILTO=admin@example.com
And it defaults to sending it to $USER@localhost, so you only need to
bother with MAILTO= if you want it to go to a different mailbox.
next prev parent reply other threads:[~2022-09-13 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 0:00 scrub results by email Kengo.M
2022-09-13 0:10 ` Christoph Anton Mitterer
2022-09-13 0:43 ` Kengo.M
2022-09-13 17:30 ` Roman Mamedov
2022-09-13 19:39 ` Phillip Susi [this message]
2022-09-14 3:00 ` Kengo.M
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=87o7vjyse8.fsf@vps.thesusis.net \
--to=phill@thesusis.net \
--cc=kengo@kyoto-arc.or.jp \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.net \
/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