Yes, i did the same thing on my own. I'm really surprised the OS/thread library
does that.
My apologies
JD
-Original Message-
From: Michaël CATANZARITI [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 27, 2004 4:56 PM
To: Log4CXX User
Subject: Re: Thread Name Issues
Yes may be
at doesn't make
since.
JD
-Original Message-
From: Michaël CATANZARITI [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 27, 2004 12:24 PM
To: Log4CXX User
Subject: Re: Thread Name Issues
Hello Jon,
log4cxx ouputs the thread identifier (cf. function pthread_self) You can get the same
4 12:24 PM
To: Log4CXX User
Subject: Re: Thread Name Issues
Hello Jon,
log4cxx ouputs the thread identifier (cf. function pthread_self) You can get
the same id for the main thread, if you execute a test
program several times.
But if you have two or more threads, you should get different ids
Hello Jon,
log4cxx ouputs the thread identifier (cf. function pthread_self)
You can get the same id for the main thread, if you execute a test
program several times.
But if you have two or more threads, you should get different ids.
Michaël
Dahl, Jon wrote:
For some reason, log4cxx always outputs
For some reason, log4cxx always outputs the same value for %t. In my
case on the version of Linux I am using, it outputs 8192.
Has anyone else come across this problem before? Is there something I
may not be doing in the config/code?
This is the only thing keeping me from using this lib in our pr
