<html><head></head><body>Err... You might want to wait until we solve a little problem with awstats... :-)<br><br><div class="gmail_quote">On February 26, 2016 9:34:35 PM PST, Sebastian Silva <sebastian@fuentelibre.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Tell you what I'll subscribe to system-logs then :-)<br /><br />I'll try to help.<br /><br />Regards,<br />Sebastian<br /><br />On 26/02/16 21:36, Bernie Innocenti wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> While I was cleaning up our cron mail, I noticed that lightwave was not<br /> being backup due to a silly config error. FOR MONTHS.<br /><br /> I fixed it, but I think this highlights a serious issue: nobody (me<br /> included) is reading email from cron. There are way too many errors, and<br /> important stuff like this gets lost in the noise.T<br /><br /> So let's make an effort to cleanup systems-logs@ so we receive email<br /> only when something goes wrong. If we can't find a clean way to make a<br /> script shut up, let's redirect it to /dev/null in the cron line...<br /><br /> But from now on, let's all try to keep an eye at cron errors in our inbox.</blockquote><br
/></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>