How to set LockingModel in Log4cxx (if possible)

AUTO: Chhavi Agarwal is out of the office (returning 04/16/2012)

I am out of the office until 04/16/2012.

On Vacation.
Please contact Imran.kazi <at> in.ibm.com ( Imranuddin W Kazi )l for any project
related queries.
If urgent call me 9740335000

Note: This is an automated response to your message  "How to set
LockingModel in Log4cxx (if possible)" sent on 12/4/12 3:14:20.

This is the only notification you will receive while this person is away.

Re: How to set LockingModel in Log4cxx (if possible)

Guten Tag Millard, Andy,
am Mittwoch, 11. April 2012 um 23:44 schrieben Sie:

> Is LockingModel implemented for log4cxx (0.10.0) as it is for Log4Net ?

No. Why do you think it should be if even the appender name is log4net
specific? 

> If this is not supported in Log4cxx 0.10.0 what are the alternatives?
> E.g. suggested code changes to log4cxx itself?  A later release of
> log4cxx, although I have not found one.

Use another Editor to view the file. If Notepad can open the file, the
problem is not with the file locking, because it's locked by the
logging process to be readable by others, but with the editor which
can't open the file unless it is able to get an exclusive lock.
TextPad for example is able to open logfiles in use, too. I don't
think there's any other solution because locking the file by the
logging process to be the only one which can write to the logfile
seems fine and logical to me.

Mit freundlichen Grüßen,

Thorsten Schöning

--

-- 
Thorsten Schöning       E-Mail:Thorsten.Schoening <at> AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon.............030-2 1001-310
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow

Usage in embedded Systems

Hi,

is log4cxx suitable for usage in embedded systems?

Regards,
Sven Müller.

Re: Usage in embedded Systems

Re: Usage in embedded Systems

Rhosyn wrote:
> As ever, it depends on the nature of your embedded platform and your
> usage of log4cxx :)
> 
> We've used log4cxx successfully for a number of years in a Linux based
> appliance product.
> 
> You might well find it less appropriate for your needs if you're
> targeting an embedded RTOS, for example.
> 
> On 20 April 2012 15:19, Sven Müller <sven.mueller <at> uni-oldenburg.de>
> wrote:
>         Hi,
>         
>         is log4cxx suitable for usage in embedded systems?
>         
>         Regards,
>         Sven Müller. 

In fact, I am targeting an embedded real-time os. Why would there be a
difference to using log4cxx in an embedded "non-real-time" os?

Regards,
Sven Müller.

>         

RE: Usage in embedded Systems

I think the assumption is that if you need a real-time OS, then you have a real-time application.

You may need to pay particular attention to the buffering of log messages to ensure your use of logging has no
measurable negative impact on the performance of your real-time application.

-----Original Message-----
From: Sven Müller [mailto:sven.mueller <at> uni-oldenburg.de] 
Sent: Thursday, April 26, 2012 5:10 AM
To: Log4CXX User
Subject: Re: Usage in embedded Systems

Rhosyn wrote:
> As ever, it depends on the nature of your embedded platform and your
> usage of log4cxx :)
> 
> We've used log4cxx successfully for a number of years in a Linux based
> appliance product.
> 
> You might well find it less appropriate for your needs if you're
> targeting an embedded RTOS, for example.
> 
> On 20 April 2012 15:19, Sven Müller <sven.mueller <at> uni-oldenburg.de>
> wrote:
>         Hi,
>         
>         is log4cxx suitable for usage in embedded systems?
>         
>         Regards,
>         Sven Müller. 

In fact, I am targeting an embedded real-time os. Why would there be a
difference to using log4cxx in an embedded "non-real-time" os?

Regards,
Sven Müller.



>