This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig67F18C3C05E1CB872D771EC5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 11/14/2012 05:58 AM, Mike Burns wrote:
On Wed, 2012-11-14 at 08:45 -0500, Doron Fediuck wrote:
Thanks Mike! I suggest to have a cron alerting for no-space issues. =20 We run logwatch which is supposed to highlight these issues, but I suspect that no one is actually reading the logwatch report. A separat= e cron job or monitoring service is also a possibility.
Logwatch comes to this list (it should, if you all aren't receiving it, let me know). I read it semi-regularly. The trouble is, we've been running >90% full for so long that we fill that last 5% quickly at times.= I can adjust the backup scripts to keep one fewer day of backup, down to the last five. Is that acceptable for now? - Karsten --=20 Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 --------------enig67F18C3C05E1CB872D771EC5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iD8DBQFQo7bO2ZIOBq0ODEERAi8tAJ9WiRfgy6ohzoep99vMpZ4QhPJSvACfRuxL ALPWYU9y5kfMpGYgj1S4YUg= =y2T/ -----END PGP SIGNATURE----- --------------enig67F18C3C05E1CB872D771EC5--