my-swatch News
Brought to you by:
branc0
Menu
▾
▴
Posted by
2003-03-26
Posted by
2003-03-17
Posted by
2003-03-05
Posted by
2003-02-25
Posted by
2003-02-25
Posted by
2003-02-22
Posted by
2003-02-20
my-swatch / News: Recent posts
my-swatch 0.6 - Bugfixes
Sometimes my-swatch would reopen the file containing the logs and would parse it all over again. This could cause the re-sending of e-mail alerts and all other associated triggers leading to disinformation and pain for system administrators.
2003-03-26
my-swatch 0.5 Released
A new version of my-swatch has been released and i think we have a current user base good enough to declare my-swatch stable in the absence of bugs.
The release is just maintenance and code cleanup. The web interface is now shipped by default and there was a little anoying problem with the "blink" keyword when printing out to the screen that is solved by now.
2003-03-17
Bugs Found and Fixed
my-swatch 0.4 comes to fix some bugs in MySQL and PostgreSQL modules that were handling syslog dates incorrectly. In some cases my-swatch would crash.
No need to worry anymore.
2003-03-05
my-swatch-web
my-swatch-web is a new package that goes hand by hand with my-swatch.
It pretends to be a web browser for those of you who are using MySQL logging. In the future it should also have support for the PostgreSQL people.
It's not been fully tested. So, as always, feedback is welcome.
2003-02-25
my-swatch-0.3 Released
The new version of my-swatch has been launched and it includes some major improvements. Here are the changes:
- You can now log your triggers to a remote (or local) database
- Added support for MySQL.
- Added support for PostgreSQL
- Added support for "blink" keyword when choosing color to print
- Better documentation
2003-02-25
my-swatch 0.2 Released
my-swatch 0.2 has been released today now with support to execute the commands you want when the triggers on syslogd are awaken.
2003-02-22
my-swatch 0.1 released
This is the first release of my-swatch. It doesn't do anything special. It's just like a trial version
so that users can see what are the potentials in the program.
Configuration should be pretty strait forward. Just edit conf.pl and run the script as root (or make your syslog file readeble by the user you will use - i haven't tested it this way).
The only avaiable caracteristics is to highlight the message, to ignore the message and to send you an e-mail warning you with the message and a costum subject.
2003-02-20
