Another option you may find useful: use a file appender instead of a UDP appender, and configure Chainsaw to use a LogFilePatternReceiver (which will parse and tail the log file).
There are two versions of LogFilePatternReceiver - the 'regular' version (which can process files using file: and http: URLs) and the VFS receiver, which extends this ability to include support for files accessible via the Apache Jakarta Commons VFS library (for example, log files stored on an ssh-accessible server or a remote windows share). You can find example LogFilePatternReceiver configurations from Chainsaw's Welcome tab. The documentation for receivers is available from Chainsaw's help/receiver javadoc menu. Here's the link to the VFS supported file systems: http://commons.apache.org/vfs/filesystems.html Scott On Thu, Feb 4, 2010 at 12:55 AM, Ulrich Proeller < [email protected]> wrote: > > Hello Josef, > > this is a known problem with log4net 1.2.10 and Windows Vista/7. > Caused by the additional support of the IPv6 protocoll, the UDP appender in > log4net 1.2.10.0 doesn't work, if the parameter "RemoteAddress" is set to > the "normal" Value 127.0.0.1. A workaround is to set the localhost address > to 127.0.0.2 instead. > > Of course, you can also use Log4View instead of Chainsaw and utilize more > reliable the TCP appender which comes with Log4View (www.log4view.com) ;-) > -- > View this message in context: > http://old.nabble.com/Log4net-UDP-Appender-and-Chainsaw-on-Windows-7-tp27439707p27449484.html > Sent from the Log4net - Dev mailing list archive at Nabble.com. > >
