This sounds like a good idea for another linux appliance. A centralized logging and log-analysis server could be a nice drop-in appliance for a fledgling penguin network. One spot to accumulate logs, rotate logs, analyze logs and archive logs. Sounds much better than having to configure each server for its own log storage, rotation, anaysis and archival.
/Tom Kern /301-903-2211 >From: David Boyes <[EMAIL PROTECTED]> >Subject: Re: Small Mail Transport Agent > > Which is why I use a central logging host, and do all the logging > produced by clients to that remote host. If a client tanks, I don't want > to have to dig through the remains; I want the diagnostics somewhere > central and easily located, and better yet, preparsed and ready to go, > suitably edited and processed for analysis.=20 > > I don't log anything on clients locally. If the client is so horked that > it can't send syslog output, it's not going to give me anything useful > to help fix it anyway, and I've done the up-front network engineering to > ensure that UDP packets don't get dropped (I wish syslog-ng would > stabilize...TCP would be good...). Crash logs on the console get > recorded where I have easy facilities to do so (yay, VM spooling > system!), but everything else goes to the logging host.=20 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
