log4cplus-devel Mailing List for log4cplus (Page 17)
Logging Framework for C++
Brought to you by:
wilx
Menu
▾
▴
log4cplus-devel — Mailing list for log4cplus developers
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
(2) |
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2006 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(3) |
Nov
(7) |
Dec
(15) |
| 2007 |
Jan
(19) |
Feb
(23) |
Mar
(40) |
Apr
(36) |
May
(18) |
Jun
(8) |
Jul
(10) |
Aug
(18) |
Sep
(18) |
Oct
(4) |
Nov
(1) |
Dec
(4) |
| 2008 |
Jan
(2) |
Feb
(1) |
Mar
(4) |
Apr
(16) |
May
(17) |
Jun
(15) |
Jul
(23) |
Aug
(7) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
(2) |
Feb
(1) |
Mar
(1) |
Apr
(7) |
May
|
Jun
(5) |
Jul
(2) |
Aug
(9) |
Sep
|
Oct
(4) |
Nov
(6) |
Dec
(4) |
| 2010 |
Jan
(2) |
Feb
(2) |
Mar
(6) |
Apr
(5) |
May
(2) |
Jun
(13) |
Jul
(5) |
Aug
|
Sep
(2) |
Oct
(2) |
Nov
|
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
|
Apr
(2) |
May
(2) |
Jun
(11) |
Jul
(1) |
Aug
(4) |
Sep
(5) |
Oct
|
Nov
(4) |
Dec
|
| 2012 |
Jan
|
Feb
(13) |
Mar
(3) |
Apr
(5) |
May
(18) |
Jun
(22) |
Jul
(11) |
Aug
(25) |
Sep
(56) |
Oct
(1) |
Nov
(28) |
Dec
(3) |
| 2013 |
Jan
(66) |
Feb
(40) |
Mar
(61) |
Apr
(1) |
May
(45) |
Jun
(30) |
Jul
(30) |
Aug
(46) |
Sep
(23) |
Oct
(43) |
Nov
(95) |
Dec
(27) |
| 2014 |
Jan
(16) |
Feb
(19) |
Mar
(23) |
Apr
(18) |
May
(22) |
Jun
(12) |
Jul
(15) |
Aug
(16) |
Sep
(30) |
Oct
(10) |
Nov
(10) |
Dec
(5) |
| 2015 |
Jan
(2) |
Feb
(7) |
Mar
|
Apr
(1) |
May
(10) |
Jun
(3) |
Jul
(1) |
Aug
(5) |
Sep
|
Oct
(6) |
Nov
(2) |
Dec
(15) |
| 2016 |
Jan
(21) |
Feb
(6) |
Mar
(30) |
Apr
(12) |
May
(11) |
Jun
(4) |
Jul
(2) |
Aug
(7) |
Sep
(13) |
Oct
|
Nov
(6) |
Dec
(8) |
| 2017 |
Jan
(21) |
Feb
(5) |
Mar
(7) |
Apr
(3) |
May
|
Jun
(4) |
Jul
(18) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(4) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
|
From: A R. <ari...@gm...> - 2012-05-09 14:03:12
|
I just got started with log4cplus, and noticed compile errors in the example at: http://log4cplus.sourceforge.net/hello_world.html I am using log4cplus 1.1.0rc4. Compiling the example complains about LOG4CPLUS_WARN not existing. Replacing the #include on logger.h with #include <log4cplus/loggingmacros.h> seems to resolve the issue. Alex |
|
From: Václav Z. <vha...@gm...> - 2012-05-01 20:47:15
|
On 05/01/2012 08:15 PM, Jeremy C. Reed wrote: > The BIND 10 suite uses log4cplus. We have multiple processes running > that use a centralized logging configuration. Our use of log4cplus is > wide-spread through our code. But mostly abstracted as our own library > with code at > http://git.bind10.isc.org/~jreed/gitweb/gitweb.cgi?p=bind10/.git;a=tree;f=src/lib/log > > (By the way, we have a nice feature where we have a unique log message > for every use that has a corresponding longer description that is > available in our documentation.) > > A few problems we have include: > > 1) stderr output sometimes has Ctrl-@ characters included in the output. > I have only seen this on our MacOS system and can't reproduce it, but it > happens frequently. > > An example: > > 2012-01-25 03:58:52.408 DEBUG [b10-cmdctl.cmdctl] CMDCTL_STARTED cmdctl > is listening for connections on 127.0.0.1:8080 > 2012-01-25 03:58:52.429 012-01-25 03:58:52.428^@IINFO ^@^@^@ ^@ > [^@^@b10-xfrout.xfrouttats-httpd^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@] > ^@^@XFROUT_NEW_CONFIG Update xfrout > configuration^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ > ^@2012-01-25 03:58:52.429 INFO [b10-xfrout.xfrout] > XFROUT_NEW_CONFIG_DONE Update xfrout configuration done > 2012-01-25 03:59:07.946 INFO [b10-xfrin.xfrin] > XFRIN_XFR_TRANSFER_STARTED IXFR transfer of zone example/IN started > > Anyone see CTRL-@? (Note that you probably can't see it unless you > convert it to something visible. I piped the saved output through cat > -v.) (The rest of the corruption in that output is probably due to poit > #2 below.) > > Our BIND 10 specific ticket about this is at > http://bind10.isc.org/ticket/1629 I have never seen such behaviour. You are the first one reporting this. I have no idea why it could be happening. > > 2) Often we have log output that is mixed when sent to console (stdout > or stderr). For example, the following line: > > 2012-02-22 11:20:33.287 DEBUG2012-02-22 11:20:33.287 DEBUG [b10-auth.auth] AUTH_DNS_SERVICES_CREATED DNS services created > > was logged as different entries but ended up interspersed. We have seen > this on multiple different operating systems. > > I see the new fileappender UseLockFile. Is there any similar feature so > different processes (using same log4cplus setup) won't write their log > output to console at the same time? > > Our BIND 10 specific ticket about this is at > http://bind10.isc.org/ticket/1704 There is no inter-process synchronization for console output. In theory, it should be possible to implement it using lock file. > > 3) Old rotated logs continue to be open and written to. fstat shows it > clearly. The problem is mostly understood. Multiple processes (all using > log4cplus) are writing to the same rotated log file. One process noticed > file needs to be rotated, so files are renamed. Other processes continue > to have the file handle open (now with an old name with number at > end) and start logging to it (starting from an empty file?). Later it > may reach our max file size configuration and be rotated too. > > I haven't tried the fileappender's UseLockFile, but maybe it handles > this rotation problem also. Any suggestions on this? > > Our BIND 10 specific ticket about this is at > http://bind10.isc.org/ticket/1896 Yes, this has been reported and it should be fixed on trunk and upcoming 1.1.0 for FileAppender and RollingFileAppender. DailyRollingFileAppender still has issues with synchronization between multiple processes. >[...] -- VZ |
|
From: Jeremy C. R. <re...@re...> - 2012-05-01 18:15:26
|
The BIND 10 suite uses log4cplus. We have multiple processes running that use a centralized logging configuration. Our use of log4cplus is wide-spread through our code. But mostly abstracted as our own library with code at http://git.bind10.isc.org/~jreed/gitweb/gitweb.cgi?p=bind10/.git;a=tree;f=src/lib/log (By the way, we have a nice feature where we have a unique log message for every use that has a corresponding longer description that is available in our documentation.) A few problems we have include: 1) stderr output sometimes has Ctrl-@ characters included in the output. I have only seen this on our MacOS system and can't reproduce it, but it happens frequently. An example: 2012-01-25 03:58:52.408 DEBUG [b10-cmdctl.cmdctl] CMDCTL_STARTED cmdctl is listening for connections on 127.0.0.1:8080 2012-01-25 03:58:52.429 012-01-25 03:58:52.428^@IINFO ^@^@^@ ^@ [^@^@b10-xfrout.xfrouttats-httpd^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@] ^@^@XFROUT_NEW_CONFIG Update xfrout configuration^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@2012-01-25 03:58:52.429 INFO [b10-xfrout.xfrout] XFROUT_NEW_CONFIG_DONE Update xfrout configuration done 2012-01-25 03:59:07.946 INFO [b10-xfrin.xfrin] XFRIN_XFR_TRANSFER_STARTED IXFR transfer of zone example/IN started Anyone see CTRL-@? (Note that you probably can't see it unless you convert it to something visible. I piped the saved output through cat -v.) (The rest of the corruption in that output is probably due to poit #2 below.) Our BIND 10 specific ticket about this is at http://bind10.isc.org/ticket/1629 2) Often we have log output that is mixed when sent to console (stdout or stderr). For example, the following line: 2012-02-22 11:20:33.287 DEBUG2012-02-22 11:20:33.287 DEBUG [b10-auth.auth] AUTH_DNS_SERVICES_CREATED DNS services created was logged as different entries but ended up interspersed. We have seen this on multiple different operating systems. I see the new fileappender UseLockFile. Is there any similar feature so different processes (using same log4cplus setup) won't write their log output to console at the same time? Our BIND 10 specific ticket about this is at http://bind10.isc.org/ticket/1704 3) Old rotated logs continue to be open and written to. fstat shows it clearly. The problem is mostly understood. Multiple processes (all using log4cplus) are writing to the same rotated log file. One process noticed file needs to be rotated, so files are renamed. Other processes continue to have the file handle open (now with an old name with number at end) and start logging to it (starting from an empty file?). Later it may reach our max file size configuration and be rotated too. I haven't tried the fileappender's UseLockFile, but maybe it handles this rotation problem also. Any suggestions on this? Our BIND 10 specific ticket about this is at http://bind10.isc.org/ticket/1896 Thank you for log4cplus. If you have any suggestions on how we can better use it, please let us know. Jeremy C. Reed |
|
From: Andreas B. <bie...@co...> - 2012-04-30 08:41:06
|
Dear list members, another convenience patch from our usage of log4cplus. I hope this change is also useful for other users. best regards Andreas Bießmann |
|
From: Václav Z. <wi...@us...> - 2012-04-29 18:53:29
|
Hi.
I have released log4cplus 1.1.0-RC4. It contains several portability
fixes plus some other changes:
IMPORTANT: Compilation with Solaris Studio now depends on STLPort
(-library=stlport4 switch). The default Cstd library is not
conforming enough for use in log4cplus.
- Improved behaviour of log4cplus as a component of larger CMake based
project (Andreas Bießmann).
- Updated various Autoconf detection scripts in m4/ directory to newer
versions.
- Fixed some signedness and overflow warnings.
- Improved Autotools build system's behaviour for cross compilation.
- Added detection of C++11 <atomic> header and related
functions. Implemented SharedObject reference counting using C++11
atomics where possible.
- Fixed compilation with GCC 4.6 in C++11 mode.
- Fixed some single-threaded compilation and run time issues.
- Fixed bug #3520891 - FileAppender buffering issue.
- Updated to Autoconf 2.69, Automake 1.12 and Libtool 2.4.2.
- Documented build procedure for Solaris Studio.
- Improved support for Solaris Studio in configure.in.
--
VZ
|
|
From: Václav Z. <wi...@us...> - 2012-04-17 19:45:52
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 04/17/2012 07:03 PM, Andreas Bießmann wrote: > Dear list members, > > would be great to get these bundled changes in upcomming relaese 1.1. > > These changes makes it easier to have a top level cmake project include > log4cplus. There are no side-effects on building log4cplus alone with cmake. > Other buildsystems are not afected at all. Thank you for the changes. I have merged them into trunk and 1.1.x branch. - -- VZ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAk+NwpEACgkQbJlIwZz1OoeGDgD/c2LWOn4pHQE4YRjRHEV+PzhO +1/eTvJSSm3td85wzy4BAKloqo+vmMjO/e4q6RtV0c7o/RVhoH7ZpFRsfsl+o9cP =41AA -----END PGP SIGNATURE----- |
|
From: Andreas B. <bie...@co...> - 2012-04-17 17:08:27
|
Dear list members, would be great to get these bundled changes in upcomming relaese 1.1. These changes makes it easier to have a top level cmake project include log4cplus. There are no side-effects on building log4cplus alone with cmake. Other buildsystems are not afected at all. best regards Andreas Bießmann |
|
From: Václav Z. <vha...@gm...> - 2012-04-14 05:55:43
|
Hi. I have released log4cplus 1.1.0-RC3. It contains only one additional fix: - Fix log4cplusS.vcxproj - add missing source files to the project. -- VZ |
|
From: Václav Z. <vha...@gm...> - 2012-03-20 10:55:30
|
Hi. I have created log4cplus Bazaar repository and project mirror on Launchpad.net: See <https://launchpad.net/log4cplus>. The reason for this mirror is that Launchpad allows easier access to Bazaar repositories (using HTTP as well as BZR protocols) and it also allows easier branching and patch merging back to official repository for both you and me. -- VZ |
|
From: Václav Z. <vha...@gm...> - 2012-03-19 22:00:17
|
Hi. I have released log4cplus 1.1.0-RC2. It contains small amount of fixes relative to RC1. - CMake build system fixes. - Fixed TTCCLayout double time stamp issue. -- VZ |
|
From: Václav Z. <vha...@gm...> - 2012-03-12 07:34:19
|
Hi. I have released log4cplus 1.1.0-RC1. It contains some internal improvements as well as user visible changes. The most significant improvements are mentioned below: log4cplus 1.1.0-RC1 Important changes relative to PRODUCTION_1_0_x branch: - Added AsyncAppender. - Added simple C interface for interoperability with C. - Added inter-process file locking to file appenders to allow logging into a single log file from multiple processes. - Added Mapped Diagnostic Context (MDC) and associated converter (%X). - Added alternative thread identification (%T) converter to pattern layout. - Added function name converter (%M). - Added wchar_t <-> char conversion implementations based on standard C locale functions and based on iconv(). - Added DeviceAppender to allow use of Boost.IOStream's Sink as appender. - Added LOG4CPLUS_*_FMT() macros to allow printf-like formatted output where it is possible. - Logging macros now accept both logger name as string and Logger instance as their first parameter. -- VZ |
|
From: Václav Z. <vha...@gm...> - 2012-02-27 21:03:00
|
2012/2/27 Deepak Muley <dee...@hd...> > Thank you for the information. > > Few queries: > 1. I am failing to understand when does it create a backup file in the > first place. I tested with schedule set to minutely, daily and weekly and > ran for long time but still did not see a single file getting created with > .1, .2 extension. What is the premise for creating these files. It always > creates with postfix with date (and its variations based on schedule) > Try the TWICE_DAILY schedule. I believe it works in that case. > > 2. If I use the DaillyRollingFileAppender is there a way to limit the > number of days the log files are kept. i.e. always keep the seven newest > logs or Do I have to use RollingFileAppender to achieve this. > This is not possible with the DaillyRollingFileAppender. It would have to keep information about previous logs and even then that information would be lost between restarts of your application. -- VZ |
|
From: Deepak M. <dee...@hd...> - 2012-02-27 19:41:51
|
Thank you for the information. Few queries: 1. I am failing to understand when does it create a backup file in the first place. I tested with schedule set to minutely, daily and weekly and ran for long time but still did not see a single file getting created with .1, .2 extension. What is the premise for creating these files. It always creates with postfix with date (and its variations based on schedule) 2. If I use the DaillyRollingFileAppender is there a way to limit the number of days the log files are kept. i.e. always keep the seven newest logs or Do I have to use RollingFileAppender to achieve this. Thanks again, ~Deepak Muley -----Original Message----- From: Václav Zeman [mailto:wi...@us...] Sent: Sunday, February 26, 2012 11:59 AM To: Deepak Muley Cc: log...@li... Subject: Re: [Log4cplus-devel] DailyRollingFileAppender does not honor maxBackupIndex On 02/25/2012 12:34 AM, Deepak Muley wrote: > > Hello All, > > > > I am using DailyRollingFileAppender with PatternLayout , with > maxBackupIndex as 10 and with schedule as DAILY. > > It was observed that Log4cplus does not delete the backup files after > 10 days. It keeps creating more. > > > > For quick debugging I enabled log4cplu internal logging with schedule > set as MINUTELY and found that here also it does not create files with > .1…n which inturn (per code) won’t be found when it comes to deleting > them after reaching maxBackupIndex. > > > > Is this a bug and if anybody else has any solution? > This is not a bug. See <https://sourceforge.net/tracker/index.php?func=detail&aid=1257117&group_id=40830&atid=429073> for detail. > > > Here’s the output from log4cplus logging: > > log4cplus: Just opened file: E:\testlogs\TestLog_p360.log > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-49 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-49 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-50 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-50 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-51 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-51 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-52 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-52 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-53 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-53 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-54 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-54 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-55 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-55 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-56 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-56 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-57 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-57 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-58 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-58 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-59 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-59 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-00 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-00 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-01 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-01 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-02 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-02 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-03 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-03 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-04 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-04 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-05 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-05 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-06 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-06 > > > > Thanks. > -- VZ |
|
From: Václav Z. <vha...@gm...> - 2012-02-27 11:38:20
|
log4cplus 1.0.4.1-RC1 has been released. It will become 1.0.4.1 if there are not issues reported against it. It contains few small fixes and autotools machinery updates: Version 1.0.4.1-RC1 - Fixed use of uninitialized member in ConfigurationWatchDogThread. - Updated libtool to 2.4; updated configure macros. - Improved resource and error handling in NTEventLogAppender and Win32 sockets code. - Fixed issue with function-try-catch blocks in dtors. -- VZ |
|
From: Václav Z. <wi...@us...> - 2012-02-26 20:15:57
|
On 02/25/2012 12:34 AM, Deepak Muley wrote: > > Hello All, > > > > I am using DailyRollingFileAppender with PatternLayout , with > maxBackupIndex as 10 and with schedule as DAILY. > > It was observed that Log4cplus does not delete the backup files after > 10 days. It keeps creating more. > > > > For quick debugging I enabled log4cplu internal logging with schedule > set as MINUTELY and found that here also it does not create files with > .1…n which inturn (per code) won’t be found when it comes to deleting > them after reaching maxBackupIndex. > > > > Is this a bug and if anybody else has any solution? > This is not a bug. See <https://sourceforge.net/tracker/index.php?func=detail&aid=1257117&group_id=40830&atid=429073> for detail. > > > Here’s the output from log4cplus logging: > > log4cplus: Just opened file: E:\testlogs\TestLog_p360.log > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-49 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-49 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-50 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-50 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-51 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-51 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-52 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-52 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-53 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-53 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-54 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-54 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-55 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-55 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-56 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-56 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-57 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-57 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-58 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-58 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-59 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-07-59 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-00 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-00 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-01 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-01 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-02 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-02 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-03 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-03 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-04 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-04 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-05 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-05 > log4cplus: Renaming file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-06 > log4cplus: Renamed file E:\testlogs\TestLog_p360.log to > E:\testlogs\TestLog_p360.log.2012-02-24-08-06 > > > > Thanks. > -- VZ |
|
From: Deepak M. <dee...@hd...> - 2012-02-24 23:35:01
|
Hello All, I am using DailyRollingFileAppender with PatternLayout , with maxBackupIndex as 10 and with schedule as DAILY. It was observed that Log4cplus does not delete the backup files after 10 days. It keeps creating more. For quick debugging I enabled log4cplu internal logging with schedule set as MINUTELY and found that here also it does not create files with .1...n which inturn (per code) won't be found when it comes to deleting them after reaching maxBackupIndex. Is this a bug and if anybody else has any solution? Here's the output from log4cplus logging: log4cplus: Just opened file: E:\testlogs\TestLog_p360.log log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-49 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-49 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-50 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-50 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-51 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-51 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-52 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-52 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-53 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-53 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-54 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-54 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-55 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-55 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-56 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-56 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-57 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-57 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-58 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-58 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-59 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-07-59 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-08-00 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-08-00 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-08-01 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-08-01 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-08-02 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-08-02 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-08-03 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-08-03 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-08-04 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-08-04 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-08-05 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-08-05 log4cplus: Renaming file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-08-06 log4cplus: Renamed file E:\testlogs\TestLog_p360.log to E:\testlogs\TestLog_p360.log.2012-02-24-08-06 Thanks. |
|
From: Václav Z. <vha...@gm...> - 2012-02-21 19:01:34
|
On 02/21/2012 04:40 PM, Shushanik Mirzoyan wrote: > Thanks, > This should not be my base, since I use static linking with log4cplus.a > LIBS += C:/MinGW/msys/1.0/local/lib/liblog4cplus.a > > I want to try to rebuild log4cplus with my QT's g++. > > I can't use mingw that QT provides , since it misses the autotools, so I can't configure, or make there. > That is why I installed a separate mingw to build log4cplus. The log4cplus packaging also includes build system using CMake. You could try to use that. > > Can I use this other mingw passing it QT's g++ and linker? Yes, you can set the CC, CXX and LD environment variables to paths to the Qt's Mingw. > > Shushanik > -----Original Message----- > From: Václav Zeman [mailto:vha...@gm...] > Sent: February-21-12 10:29 AM > To: Shushanik Mirzoyan > Cc: log...@li... > Subject: Re: [Log4cplus-devel] FW: Log4cplus > > 2012/2/21 Shushanik Mirzoyan <shu...@in...>: >> My qt creator uses g++ 4.4.0, >> >> While I compiled log4cplus with g++ 4.6.1 > These two seem way too different. There have been many changes in both the C++ library implementation and the compiler between 4.4.x and 4.6.x. > > Also, my google search reveals this: > <https://bugreports.qt-project.org/browse/QTSDK-574>. Check that you are not facing similar issues. > -- VZ |
|
From: Václav Z. <vha...@gm...> - 2012-02-21 15:29:17
|
2012/2/21 Shushanik Mirzoyan <shu...@in...>: > My qt creator uses g++ 4.4.0, > > While I compiled log4cplus with g++ 4.6.1 These two seem way too different. There have been many changes in both the C++ library implementation and the compiler between 4.4.x and 4.6.x. Also, my google search reveals this: <https://bugreports.qt-project.org/browse/QTSDK-574>. Check that you are not facing similar issues. -- VZ |
|
From: Shushanik M. <shu...@in...> - 2012-02-21 15:19:18
|
My qt creator uses g++ 4.4.0, While I compiled log4cplus with g++ 4.6.1 From: Václav Zeman [mailto:vha...@gm...] Sent: February-21-12 10:15 AM To: Shushanik Mirzoyan Cc: log...@li... Subject: Re: [Log4cplus-devel] FW: Log4cplus 2012/2/21 Shushanik Mirzoyan Here is my gdb log. Just want to mention that I built log4cplus with another version of mingw ( and g++), not the one that’s being used by my QT creator. Bu I think this should not be a problem. This could be the problem. What different versions of G++ have you used? -- VZ |
|
From: Václav Z. <vha...@gm...> - 2012-02-21 15:14:54
|
2012/2/21 Shushanik Mirzoyan > Here is my gdb log.**** > > Just want to mention that I built log4cplus with another version of mingw > ( and g++), not the one that’s being used by my QT creator. **** > > Bu I think this should not be a problem. > This could be the problem. What different versions of G++ have you used? -- VZ |
|
From: Václav Z. <vha...@gm...> - 2012-02-20 22:06:13
|
On 02/20/2012 07:49 PM, Shushanik Mirzoyan wrote: > > > > > *From:*Shushanik Mirzoyan > *Sent:* February-20-12 1:22 PM > *To:* 'wi...@us...' > *Subject:* Log4cplus > > > > Hello, > > My name is Shushanik, > > I am trying to integrate log4cplus into our product. > > I seem to solve all the problems within past 2 days, and now it > wokrs, I have the nice logs. > > However, my debugger crashes right at start no breakpoints hit, or > anything, it feels like it tries to load the library and crashes. > > I use QT creator. > > > > > > And here is the crash message > > > > I built log4cplus with --enable-debugging configuration. > > > > ./configure --enable-static --enable-threads --with-gnu-ld > --enable-debugging CPPFLAGS="-DUNICODE -D_UNICODE" > > I really hope you'll be able to help me . > > > > Thanks a lot in advance. > > Shushanik > > > > P.S. I used to use Log4Cplus in my previous job(I did not do the > integration part though), and it's really cool. So hope that I can > successfully integrate it with this new tool. > This does not tell me much. It seems more like a GDB problem than log4cplus'. In any case, try to get a stack trace. -- VZ |
|
From: Shushanik M. <shu...@in...> - 2012-02-20 21:00:52
|
Hello, My name is Shushanik, I am trying to integrate log4cplus into our product. I seem to solve all the problems within past 2 days, and now it wokrs, I have the nice logs. However, my debugger crashes right at start no breakpoints hit, or anything, it feels like it tries to load the library and crashes. I use QT creator. QT creator 2.3.1 Based on qt 4.7.4 (32 bit) The crash message that I get is "The gdb process exited unexpectedly (code 1)" I built log4cplus with --enable-debugging configuration. ./configure --enable-static --enable-threads --with-gnu-ld --enable-debugging CPPFLAGS="-DUNICODE -D_UNICODE" I really hope you'll be able to help me . Thanks a lot in advance. Shushanik P.S. I used to use Log4Cplus in my previous job(I did not do the integration part though), and it's really cool. So hope that I can successfully integrate it with this new tool. |
|
From: Václav Z. <wi...@us...> - 2011-11-30 06:25:44
|
On 11/21/2011 11:10 AM, 蒙德鑫 wrote:
> Hi, I know in PatternLayout, %d{} is used to output the date of the
> logging event in *UTC*.
>
> My question is ,how to set timezone in PatternLayout?
It is not possible to set arbitrary timezone for PatternLayout output.
You can use either %d{} for UTC or %D{} for local time. Use %D{...%Z} to
get timezone name in the date.
--
VZ
|
|
From: Václav Z. <v.h...@sh...> - 2011-11-10 20:24:10
|
On 11/10/2011 07:26 PM, Mik...@de... wrote: > I tried to post to the mailing list, but it said that I am not allowed > to post to the mailing list? Could you correct this? You should be able to post if you are subscribed. Post using the <log...@li...> email address. > > Thank you. > ----- Message from Mik...@de... on Thu, 10 Nov 2011 > 13:02:46 -0500 ----- > *To:* > log...@li... > *Subject:* > Mapped Diagnostic Context (MDC) Support? > > > I was wondering if there were any plans to add Mapped Diagnostic Context > (MDC) support to log4cplus? There is MDC support on trunk but I have not merged it back to PRODUCTION_1_0_x branch as it would require more substantial changes. -- wilx |
|
From: Václav Z. <wi...@us...> - 2011-11-07 07:40:18
|
On Mon, 7 Nov 2011 03:43:13 +0000, Boom LBoom wrote: > Hi VZ, > > Thank you for your replying. > > From your questions > I have never seen this problem before. It is only a warning, does > the > resulting liblog4cplus work for you? > answer : It was compiled success but that occurred error while ld > > Is the 'ld' your GCC is using the GNU ld? > answer : ld: Software Generation Utilities - Solaris Link Editors: > 5.10-1.1505 > > What version of log4cplus are you compiling? > answer : log4cplus version 1.0.3 > > After trying from your recommended. The result shows as below so it > didn't work. > > -bash-3.2$ cat config.log > This file contains any messages produced by compilers while > running configure, to aid debugging if configure makes a mistake. > > It was created by log4cplus configure 1.0.3, which was > generated by GNU Autoconf 2.62. Invocation command line was > > $ ./configure CXXFLAGS=-gstabs+ >[...] > configure:2764: checking for C++ compiler default output file name > configure:2786: g++ -gstabs+ conftest.cpp >&5 > Assembler: conftest.cpp > "/var/tmp//ccH4txrq.s", line 39 : Illegal mnemonic > Near line: " .stabd 46,0,0" > "/var/tmp//ccH4txrq.s", line 39 : Syntax error > Near line: " .stabd 46,0,0" > "/var/tmp//ccH4txrq.s", line 59 : Illegal mnemonic > Near line: " .stabd 78,0,0" > "/var/tmp//ccH4txrq.s", line 59 : Syntax error > Near line: " .stabd 78,0,0" >[...] I see three possibilities: I you can either live with the warning, or disable debugging information generation altogether, or get GCC that uses GNU ld. I do not think that this is log4cplus specific problem but rather a compiler tool chain problem on Solaris. -- VZ |
927 messages has been excluded from this view by a project administrator.
