Return-Path: Delivered-To: apmail-logging-log4net-user-archive@www.apache.org Received: (qmail 19055 invoked from network); 4 Feb 2009 02:52:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Feb 2009 02:52:57 -0000 Received: (qmail 85049 invoked by uid 500); 4 Feb 2009 02:52:56 -0000 Delivered-To: apmail-logging-log4net-user-archive@logging.apache.org Received: (qmail 85021 invoked by uid 500); 4 Feb 2009 02:52:56 -0000 Mailing-List: contact log4net-user-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Log4NET User" List-Id: Delivered-To: mailing list log4net-user@logging.apache.org Received: (qmail 85007 invoked by uid 99); 4 Feb 2009 02:52:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Feb 2009 18:52:55 -0800 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [68.142.200.115] (HELO web30502.mail.mud.yahoo.com) (68.142.200.115) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 04 Feb 2009 02:52:47 +0000 Received: (qmail 75313 invoked by uid 60001); 4 Feb 2009 02:52:25 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=rsmkSnb2z3JbriIfwSnf0enju/Qk99Vs4KVfJ9dXXn2MU5sIP9ilury3H7ezG6Jq4nVSUnJSB8Hhvep8FgqZApB/prT+bazts3wugvVgAQ+CqIK3EEm0U/wFOUI5ZyysEGlFs4dHZpoxc2r4eH+X+k8MkrjAziXR0rZdvZ6r9to=; X-YMail-OSG: KeQd2gEVM1mOF0SuqJRrxYWyGcds_HoZ.Ip62CP2G2ltz0N_Ta6EZdDhAfWrWvEZZdcNZpsok5EnEWsD0jWjcZhrEIQJWxl.W5J4kR03vfMoLOLzI3yjM2aD4Lkd1Wr2wI2cqdLzPXgDj.aSb5b_eqMbMKD8iXDm3bfg27Hw6W7_NPS0TDwep1shRH0_0hQfPvoKk5N2tOxsWORBw30rxNeOllW1 Received: from [173.89.245.218] by web30502.mail.mud.yahoo.com via HTTP; Tue, 03 Feb 2009 18:52:25 PST X-Mailer: YahooMailRC/1155.45 YahooMailWebService/0.7.260.1 References: <21804464.post@talk.nabble.com> Date: Tue, 3 Feb 2009 18:52:25 -0800 (PST) From: Ron Grabowski Subject: Re: Using Log4Net for Distributed Logging To: Log4NET User MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <419424.73347.qm@web30502.mail.mud.yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org 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 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.