Reload/refresh of events is already supported: - Open the receiver panel - Clear the events on the tab in order to prevent duplicates (ctrl-backspace) - Select your receiver - Right click on your selected receiver and select 'restart' (or use the button on the receiver panel's toolbar).
Scott -----Original Message----- From: OOMS DIRK [mailto:[EMAIL PROTECTED] Sent: Thu 3/3/2005 6:23 AM To: 'Log4J Users List' Cc: Subject: RE: Chainsaw LogFilePatternReceiver: ftp/http tailing Scott, Thanks for your extensive reply. This solution has quite some dependencies on other projects. A workaround (that would suit me :-)) is that there would be a 'reload/refresh' option for ftp/http file access. Any estimate on the effort that would take? cheers, dirk > -----Original Message----- > From: Scott Deboy [mailto:[EMAIL PROTECTED] > Sent: donderdag 24 februari 2005 15:43 > To: Log4J Users List > Subject: RE: Chainsaw LogFilePatternReceiver: ftp/http tailing > > > Hi Dirk, > > I discussed this with Mario on the VFS team. He's explained > how I can more fully support 'tail' using VFS. > > 'Tail' will be available for these file systems: > > LocalFile > Ftp > Http > Smb > > He also asked the developers of JSch if they would make some > minor changes to also support this, and they said they would > make the change. > > When JSch makes this change, and VFS makes their needed > change, we will then also have the ability to tail over SSH > (I wasn't told when to expect this capability). > > I'll try and implement this change soon. > > LogFilePatternReceiver (the non-VFS version) will probably > not support tailing over ftp/http. > > Hope that helps, > Scott > > -----Original Message----- > From: OOMS DIRK [mailto:[EMAIL PROTECTED] > Sent: Thu 2/24/2005 1:49 AM > To: 'Log4J Users List' > Cc: > Subject: Chainsaw LogFilePatternReceiver: ftp/http tailing > The tailing of a file with the LogFilePatternReceiver works > fine when the > file is on the file system, but when the file is specified > with ftp or http, > the tailing does not seem to work. Is this the expected behavior? > > dirk > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
