--=-LwiUUKVLbSTD9yR1UR5g Content-Type: text/plain Content-Transfer-Encoding: quoted-printable > It is sortof a tradeoff. You either get 250 e-mails, or you have to log = in=20 > and look at 250 log files. (or use a log watcher, when would in turn e-m= ail=20 > you, ending up with the first situation) >=20 > The trick is to just have it be quiet if it doesn't do anything. We only= put=20 > things out where an update would get them about once a month normally (un= less=20 > it's an emergency), so we basically get blasted once a month, and the tri= ck is=20 > to basically look at all your mail, and see which machines *didn't* get u= pdated. then the last message I sent to the list should answer your question/problem. although the default behavior would be - if nothing changed, don't email anything - could you look for a machine NOT sending a message? -sv --=-LwiUUKVLbSTD9yR1UR5g Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA9B7uH1Aj3x2mIbMcRAhyZAJ9gZuRfH66bLT0QQHI3jfN4HuJnwQCfWU2j PG+UCxMyOsq3LLywLHoVArw= =uNPz -----END PGP SIGNATURE----- --=-LwiUUKVLbSTD9yR1UR5g--
