$arr_19 ), array( 3, false, $arr_20, $arr_24 ), array( 2, false, "\" />", $arr_25 ) ) ); ?> $arr_27 ), array( 3, false, $arr_28, $arr_30 ), array( 2, false, "\" />\n\n", $arr_31 ) ) ); ?> array( 2, false, false, $arr_9 ), array( 4, $arr_10, "if", $arr_245, $arr_248 ), array( 2, false, "\n", $arr_249 ) ) ); ?> rr_466 ), array( 4, $arr_467, "if", $arr_482, $arr_484 ), array( 2, false, "\n", $arr_485 ) ) ); ?> MILKING MACHINE 2.0 » Linux Magazine
 

The sys admin’s daily grind: phpLogCon

MILKING MACHINE 2.0

Author(s):

Using SQL to sift syslog data out of a database is an admittedly universal, but also fairly convoluted approach. phpLogCon, with its web interface, gives admins an easier option.

In last month’s issue, I talked about RSyslog, a replacement for the syslog daemons. Instead of referencing the standard logfiles in /var/log, RSyslog works with one or multiple databases in which it logs local results or data supplied by remote servers. I always use one database, Maillog, for the mail facility, and a second database, syslog, for all other messages.
A couple of scripts extract statistics on spam filter performance from the Maillog DB.

Read full article as PDF »

069-069_charly.pdf  (262.88 kB)
comments powered by Disqus

Visit Our Shop

Trial Subscription

Digital Subscription

Subscribe

Direct Download

Read full article as PDF »

069-069_charly.pdf  (262.88 kB)

Tag Cloud

Bruce Byfield Gnome KDE Kernel Linux Linux Pro Magazine Open Source Projects Red Hat Ubuntu events foss free software google

News