crocket posted on Sat, 13 Jun 2015 22:48:35 +0900 as excerpted: > I can check the result of 'btrfs scrub' later, but I don't want to take > time to actually check it. > Does anyone know how to make 'btrfs scrub' report errors via email? > It seems google doesn't know.
You'd throw together a script to do it, or, if you're running it as a cronjob, cron normally already has the ability to mail output elsewhere. Similarly, systemd timer jobs normally start service units, which will normally log to journald and possibly from journald to a more conventional syslog daemon (I'm running syslog-ng here), and those logs can be mailed, often after being sorted. Traditionally there was a sendmail executable (originally part of sendmail, but many alternatives supplied a call-compatible binary) as well, which could be called with an address to send to, along with the message body, and sometimes other parameters as well. This standardized things, and was generally what various daemons that mailed logs used to send them. A script could call it as easy as cron and other daemons did, so it was pretty easy to setup output/log mailings. These days many people don't use a full mail system on the machine, instead using a mail client or webmail, and all these daemons that can be configured to send their output elsewhere very often aren't even setup for it. But it's generally still possible, either using the traditional sendmail executable, or by scripting a call to whatever mail client you normally run, having it handle the message. Meanwhile, it's likely someone here (not me) already has such a thing setup and can post the script. Of course you'd have to adjust it to use your own mail client, if different. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
