I'd start out using the remoting appender. If you want two processes to share the same log file you'll need to change the locking mechanism from the default ExclusiveLock to MinimalLock. Other alternatives include writing to real database server that can handle the concurrency. Someone posted a MutextLock to the list a while ago. I'm in the process of rewriting it to be included in the log4net distribution because the author didn't post any comments on where the code from or if it was ok to ship with log4net.
----- Original Message ---- From: Deep George <dee...@hotmail.com> To: log4net-user@logging.apache.org Sent: Tuesday, February 3, 2009 1:10:05 AM Subject: Using Log4Net for Distributed Logging Hi, I am relatively new to Log4Net. I would like to know whether Log4Net can be used for logging in a distributed environment. I am looking at 2 scenarios- Scenario 1: A 20 server site. One of the server takes care of logging (Logging Server). Every other servers pushes the log information to this centralized logging server. Which appender can i use ? (RemoteAppender?) Scenario 2: Here, there are 2 processes (Process A, Process B) running on the same host, using log4Net for logging. Is it possible for both the processes to share the log? Let say, both the processes use LogFileAppender, will they be able to share the same log file? Also, please suggest a good link/book about distributed logging using Log4Net. Thanks. -- View this message in context: http://www.nabble.com/Using-Log4Net-for-Distributed-Logging-tp21804464p21804464.html Sent from the Log4net - Users mailing list archive at Nabble.com.
