Bauduin Raphael wrote:
> Hi,
> 
> I'm happy to announce the second public version of logtails. This 
> version is a big improvements on v0.1 (see below).
> 

No, no, I didn't think everybody put logtails' page on rubyforge as their homepage,
it just got lost in the edition of the announcement....

http://rubyforge.org/projects/logtails

Raph

> Again, big thanks to Richard Dale for his help and feedback on using 
> Korundum!
> 
> Raph
> 
> 
> *Description:
> 
> If you need to watch log files and are tired of opening tens of 
> terminals and ssh to a remote host to run a tail -f, logtails could be 
> for you! I've started this project out of this need and it's starting to 
> fill it. Suggestions are welcome. I'm especially interested in feedback 
> from people using net-ssh not installed as a gem.
> 
> 
> 
> *Improvements:
> 
> -Opening of local file is possible with KDE's "open file" dialog
> -Filter lines: enter regexps that either reject the line (meaning it 
> isn't displayed) or force the line's display (even if there's a regexps 
> that would normally reject it).
> -Tooltips on the text output  show you which patterns are accepted and 
> which are  rejected
> -One files' lines can be displayed in different tabs, each tab applying 
> different filters.
> -A file, local or remote, that is already monitored can be reused 
> without entering any info. No new connection or process is started, 
> internal buffers are used.
> -When requesting a new remote tail, the current user's login is the 
> default value for the ssh login
> -When requesting a new remote tail, an existing remote tail's parameters 
> can be used as the base of this new tail, only changing the file eg.
> -Internally, the code is a bit better structured.
> 
> *Known problems:
> 
> -Tabs can't be closed
> -key based authentication is needed to open an ssh connection
> -The drop down in the dialog to open a local file sometimes gets too 
> much expanded
> -Adding an accepted regexp doesn't make all other lines rejected by 
> default. If the user enters an accepted patterns, it's supposed that 
> (s)he doesn't want lines without that pattern to be displayed.
> 
> * Plans for the future:
> -Correcting know problems ;-)
> -Add configuration items and history
> -Highlighting of text that triggered the display of the line
> -Saving a tab's content to a file
> -Printing a tab's content
> -Enable search
> -Better use of KDE's infrastructure
> -Merge 2 files' output in one tab
> -Add a change indicator in the tab selector
>