Syslog Management Tool(SMT) & Security Framework(SecFrame)
Main
Version 2.0 Info
F.A.Q
Installation
Documentation
Downloads
LICENSE
Innovation
Screen Shots
CVS(Subversion)
Mailing Lists
Okay... okay... what will be in SMT? Oh, you want to know when? :)
Changes:
TONS OF BUG FIXES
Some new bugs ;)
Better interface support.
A pre-packaged syslog daemon rather than modular syslog. It will NOT replace syslogd but will act as the primary UDP target.
NO-Archive Immediate Purge Flag - means any host flagged with this will have its logged purged from the TSyslog table once a minute. This is ideal for those hosts where you want logs temporarily but you don't want them clogging the larger archive.
MUCH improved recovery time from a crashed log processor. If a log processor crashed an you had 3,000 hosts assigned to it, SMT would have to scan the archive table 3,000 times to bring it to a sane state. SMT now records where it left off after every host. Thus is need only to remember where it left off, clean up that host, and be on its way.
Processors now log the last time they correctly ran. IOW, you can monitor to check for a log process that hasn't executed in a while.
Created another background monitoring script that keeps an eye on the size of TSyslog. It will 'make noise' in the event TSyslog looks like its size is 'running away'!
Work Windows: Yeah... the ability to say when SMT should be quiet cause you've got work to do. 8)
ERP Systems: We are extending the security framework to include ERP_ID's for both groups and users. This can be important if you need to synchronize your system with another ticket system or an ERP system(yes.... it happens)
Slony: I have been updating SMT to include direct support for interacting with and 'controlling' Slony.
Various interface updates..
For help write to: smt-AT-dangermen.com
Last Modified: 8:30:00pm CST - 5/22/2006