Dean,
Thank you for your suggestion. It's a good one, and I have thought about it,
but since L4N is already doing it (running a separate thread with a FSO) I
just wanted to reuse what's already there. If I could just hook in to
ConfigureationResetEvent that would be great.
Should I be asking this q
No need to piggyback on to log4net for this, you can use the
FileSystemWatcher class directly, which is yours free with the .NET
Framework
http://msdn2.microsoft.com/en-us/library/system.io.filesystemwatcher.aspx
Regards,
Dean
_
From: dawebber [mailto:[EMAIL PROTECTED]
Sent
Hello, all!
I would like to make use of (and piggyback on) log4net's ability to watch
the app config file for changes. I have a Windows Service, which I would
like to have the ability to reread configuration on the fly, after I edit
the configuration file.
I use the following to init the logger
Ahh, that does explain something. I'll give it a go and see if it
works.
Thanks
Ian
Ian Dykes
Software Developer
Esendex Ltd
T: +44 (0)115 852 5762
F: +44 (0)115 852 5757
Email: [EMAIL PROTECTED]
Web: www.esendex.com
Blog: http://devproj20.blogspot.com/
Esendex: Connect and Communicate
Are you setting the LocalPort for the RemoteSyslogAppender? You
shouldn't be. In the InitializeClientConnection of the UdpAppender you
should see:
if (this.LocalPort == 0)
{
this.Client = new UdpClient();
}
else
{
this.Client = new Udp
> Is this possible?
The source code it available, so I guess anything is possible. :) But
realistically no, log4net is designed to NOT throw exceptions.
> there is no comparable functionality to the ... context attributes
collection?
I've not played with the MS Block, but would the Contexts of t
Hi,
We're looking to use the RemoteSyslogAppender from a bunch of Windows
services running on the same machine, sending log events to one server
listening to one port. Looking through the source, RemoteSyslogAppender
inherits from UdpAppender, and UdpAppender uses a UdpClient object. If
I try to
Steve,
If I understand correctly, just have multiple loggers. Perhaps the
"per-class" logger for general diagnostics an trace, and then a more
global "audit" logger you use to write your audit information. You could
use different storage for the two or use the same storage. If you're
using the
