<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Makes perfect sense, thanks.
<div><br>
<div>
<div>On May 6, 2013, at 16:33 , David Langenberg wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">If
you're centralizing your logs via UNIX syslog, then you shouldn't have anything to worry about. Syslog is a send and forget protocol which works over UDP. If the log message doesn't make it to the syslog server, the node really doesn't care. So, I'd recommend
using (in addition to the syslog appender) rolling-file-appenders with sensible rotation policies on the nodes themselves to ensure disk doesn't fill up. If the central log server dies, you'll still have copies of the logs locally.</span></blockquote>
</div>
<br>
</div>
</body>
</html>