Stas Bekman wrote: > Medi Montaseri wrote: > >> Unfortunately everyone wants to use email for everything.....the >> proper way would >> be to use some facilities that have proven track record, like >> syslogd(1d) on each >> box. > > > syslog(3) is not a very scalable solution because it's slow. > It's also unreliable because it uses UDP to send the data, which doesn't > ensure that the data will reach its destination. This solution is also > unicast. If the master host goes down the logs will get lost.
And a better replacement is mod_log_spread. Based on the group communications toolkit Spread using IP multicast. mod_log_spread provides reliable, scalable centralized logging whith minimal performance impact on the web servers. For more information see http://www.backhand.org/mod_log_spread/. -- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
