Perhaps I missed some of this but... a.) Why do you need to have multiple processes logging to the same file anyhow? b.) If you have this unusual and non-standard configuration, then why is making a service on the machine that much more difficult?
As far as making it part of log4net, this seems rather unusual, so I doubt it'd make it into the main distribution, but I'm sure that if you were willing to do all the development, the log4net project guys might be interested in integrating it, or at least making it part of a secondary contrib. project. Though we all know Nicko has copious amounts of free time, I doubt he would be willing to do a one-off situation like this for someone, but who knows. -Chad -----Original Message----- From: Alexey N. Solofnenko [mailto:[EMAIL PROTECTED] Sent: Monday, May 24, 2004 12:23 PM To: Log4NET User Subject: Re: Bug? Log4Net 1.1 does not allow several processes to log into the same files. If it is simple, why not put it into standard log4net? Otherwise deploying extra components onto every client computer is an issue. - Alexey. Chad Myers wrote: >>From what I've read, Remoting and SOAP are non-preferred. > >Could you just make a simple log sink Win32 service for all your >processes? > >-Chad > > >
