<br><br>
<div class="gmail_quote">2008/11/25 David Mathog <span dir="ltr"><<a href="mailto:mathog@caltech.edu">mathog@caltech.edu</a>></span><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>I suppose syslog could be used for this, but the trick would be to<br>choose a facility/priority for it such that nothing other than the<br>
desired cluster messages was ever sent. In other words, something<br>like:<br><br>logger -p <a href="http://cluster.info/" target="_blank">cluster.info</a> "this is a cluster message"<br><br>Unfortunately there is no "cluster" facility, and I do not know<br>
which one of the 20 or so defined facilities (auth, authpriv... local7)<br>will never be used by some other part of the client OS.<br><br></blockquote>
<div>Sounds good to me.</div>
<div>Maybe you could just log all those other types of messages to the central syslog server,</div>
<div>and use logwatch, or another log parser,. to filter out the 'noise' and just email you the interesting ones?</div>
<div>Not 100% what you want.</div>
<div> </div>
<div> </div>
<div> </div></div>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.