You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(38) |
Sep
(126) |
Oct
(23) |
Nov
(72) |
Dec
(36) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(76) |
Feb
(32) |
Mar
(19) |
Apr
(6) |
May
(54) |
Jun
(40) |
Jul
(45) |
Aug
(35) |
Sep
(51) |
Oct
(67) |
Nov
(10) |
Dec
(50) |
2004 |
Jan
(51) |
Feb
(22) |
Mar
(22) |
Apr
(28) |
May
(53) |
Jun
(99) |
Jul
(38) |
Aug
(49) |
Sep
(23) |
Oct
(29) |
Nov
(30) |
Dec
(48) |
2005 |
Jan
(15) |
Feb
(21) |
Mar
(25) |
Apr
(16) |
May
(131) |
Jun
|
Jul
(8) |
Aug
(5) |
Sep
(15) |
Oct
|
Nov
(15) |
Dec
(12) |
2006 |
Jan
(15) |
Feb
(20) |
Mar
(8) |
Apr
(10) |
May
(3) |
Jun
(16) |
Jul
(15) |
Aug
(11) |
Sep
(17) |
Oct
(27) |
Nov
(11) |
Dec
(12) |
2007 |
Jan
(19) |
Feb
(18) |
Mar
(33) |
Apr
(4) |
May
(15) |
Jun
(22) |
Jul
(19) |
Aug
(20) |
Sep
(14) |
Oct
(4) |
Nov
(34) |
Dec
(11) |
2008 |
Jan
(8) |
Feb
(18) |
Mar
(2) |
Apr
(4) |
May
(26) |
Jun
(9) |
Jul
(8) |
Aug
(8) |
Sep
(3) |
Oct
(17) |
Nov
(14) |
Dec
(4) |
2009 |
Jan
(6) |
Feb
(41) |
Mar
(21) |
Apr
(10) |
May
(21) |
Jun
|
Jul
(8) |
Aug
(4) |
Sep
(3) |
Oct
(8) |
Nov
(6) |
Dec
(5) |
2010 |
Jan
(14) |
Feb
(13) |
Mar
(7) |
Apr
(12) |
May
(4) |
Jun
(1) |
Jul
(11) |
Aug
(5) |
Sep
|
Oct
(1) |
Nov
(10) |
Dec
|
2011 |
Jan
(7) |
Feb
(3) |
Mar
(1) |
Apr
(5) |
May
|
Jun
(1) |
Jul
(6) |
Aug
(6) |
Sep
(10) |
Oct
(5) |
Nov
(4) |
Dec
(5) |
2012 |
Jan
(4) |
Feb
(5) |
Mar
(1) |
Apr
(7) |
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
(5) |
Oct
(5) |
Nov
(4) |
Dec
(5) |
2013 |
Jan
(6) |
Feb
|
Mar
(14) |
Apr
(9) |
May
(3) |
Jun
(2) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
(4) |
Dec
(6) |
2014 |
Jan
|
Feb
(1) |
Mar
(10) |
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
(1) |
Nov
|
Dec
(4) |
2015 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
From: Mike S. <m...@pe...> - 2005-02-25 01:11:01
|
On Thu, 24 Feb 2005, Ron Reidy wrote: > > You're using category "test" in the config file and get_logger($0) to > > get the logger. Is $0 eq "test"? > > > > Yes, $0 eq "test". How about the other thing I've mentioned, the multiple category definitions? Does it work if you're removing the duplicates? -- Mike Mike Schilli m...@pe... |
From: Ron R. <ron...@gm...> - 2005-02-24 11:25:19
|
Mike, > You're using category "test" in the config file and get_logger($0) to > get the logger. Is $0 eq "test"? > Yes, $0 eq "test". |
From: Mike S. <log...@pe...> - 2005-02-24 01:14:40
|
Ron Reidy <ron.reidy <at> gmail.com> writes: > $logger = Log::Log4perl->get_logger($0); > $logger->info("starting"); [...] > Here is my config file: > > log4perl.logger.test = INFO, test_app > log4perl.logger.test = WARN, test_app > log4perl.logger.test = DEBUG, test_app > log4perl.logger.test = ERROR, test_app > log4perl.logger.test = FATAL, test_app You just want one of these, not 5 of them. You're using category "test" in the config file and get_logger($0) to get the logger. Is $0 eq "test"? -- Mike Mike Schilli |
From: Ron R. <ron...@gm...> - 2005-02-23 19:54:33
|
All, I am attempting my first testing of this module to understand how I can use it. Here is my test Perl program: use strict; use warnings; use Log::Log4perl qw/get_logger :levels/; use FindBin qw/$Bin/; use vars qw/$logger/; BEGIN { Log::Log4perl->init(sprintf("%s/../cfg/oracle_logger.config", $FindBin::Bin)); $logger = Log::Log4perl->get_logger($0); $logger->info("starting"); } $logger->debug("attempting start"); END { $logger->info("end") if $logger; } Here is my config file: log4perl.logger.test = INFO, test_app log4perl.logger.test = WARN, test_app log4perl.logger.test = DEBUG, test_app log4perl.logger.test = ERROR, test_app log4perl.logger.test = FATAL, test_app log4perl.appender.test_app = Log::Log4perl::Appender::File log4perl.appender.test_app.mode = append log4perl.appender.test_app.filename = ../logs/test.log log4perl.appender.test_app.layout = Log::Log4perl::Layout::PatternLayout log4perl.appender.test_app.layout.ConversionPattern = %d %p: %F{1}:%L %c %M - %m%n What happens here is the log file gets created, but nothing is written to it. I have read the "tutorial" from the O'Reilly site, but I cannot figure this out. Thanks for your help. -- Ron Reidy Oracle DBA |
From: Warren F. <wfr...@gm...> - 2005-02-22 23:04:46
|
Hi, We have been using the Log4perl module, with synchronized file appenders, on a low-traffic beta website for several months now. We have had no incidents at all until this morning, when this error started appearing on each request: error: Can't call method "SUPER::log" on an undefined value at /usr/local/lib/perl5/site_perl/5.8.6/Log/Log4perl/Appender/Synchronized.pm line 71. context: ... 67: 68: # Relay that to the SUPER class which needs to render the 69: # message according to the appender's layout, first. 70: $Log::Log4perl::caller_depth +=2; 71: $self->{app}->SUPER::log(\%params, 72: $params{log4p_category}, 73: $params{log4p_level}); 74: $Log::Log4perl::caller_depth -=2; 75: ... code stack: /usr/local/lib/perl5/site_perl/5.8.6/Log/Log4perl/Appender/Synchronized.pm:71 /usr/local/lib/perl5/site_perl/5.8.6/Log/Log4perl/Appender.pm:189 (eval 369):41 /usr/local/lib/perl5/site_perl/5.8.6/Log/Log4perl/Logger.pm:684 ...(snipped)... What seems to have happened is the semaphore's pointer to the application's logger instance got lost. How this happened, I'm not at all sure. Restarting our Apache server fixed the problem, and we have not seen it since. We are running Apache with mod_perl and the Mason templating library. This morning, when the problem occurred, we were running version 0.49 of the Log::Log4perl library. I have since upgraded the server to version 0.51, hoping this may be the result of a bug that is now fixed. Any assistance with this problem is much appreciated. Thanks to the Log4perl team for providing an excellent module! Cheers, -Warren |
From: Glenn A. H. <gh...@ek...> - 2005-02-18 16:48:58
|
Hello, I like to store my log4perl configuration in the general config file for a particular script. I use Config::IniFiles, and I put the log4perl config in a section called, appropriately, log4perl. I can then just pass the whole array right to log4perl on init. Simple enough. I was having trouble with variable evaluation, and I tracked it down to somewhere between the config file and the log4perl config parser, the lines were being placed out of order. So I created this simple hack to PropertyConfigurator.pm to delay processing of an undefined variable. It has worked so far in all my test cases. I'm not sure how 'proper' this solution is, but it seems to fit the idea of the comments I saw that mentioned the ability to read in config lines in any order. Anyway, here it is. --Glenn |
From: Garrett, P. (MAN-Corporate) <Phi...@co...> - 2005-02-16 23:07:19
|
I'm trying to wrap get_logger() in a custom module, for various reasons. I have set $Log::Log4perl::caller_depth to 1 to allow for the 1 extra level of indirection. However, Log4perl still returns a logger for the context of the wrapper, not the calling code. Changing Log::Log4perl::get_logger to pass $caller_depth to the caller() function makes it work like I expected, however I'm not sure that my expectations were correct. Can you confirm what it *should* do? This small program exhibits my problem: ############################################################### use Log::Log4perl; $config = qq{ log4perl.appender.Wrapper=Log::Log4perl::Appender::Screen log4perl.appender.Wrapper.layout=PatternLayout log4perl.appender.Wrapper.layout.ConversionPattern=WRAPPER[%m]%n log4perl.appender.Caller=Log::Log4perl::Appender::Screen log4perl.appender.Caller.layout=PatternLayout log4perl.appender.Caller.layout.ConversionPattern=CALLER[%m]%n log4perl.category.Wrapper=DEBUG, Wrapper log4perl.category.Caller=DEBUG, Caller }; Log::Log4perl->init(\$config); { package Wrapper; sub get_logger { # get logger for our caller, not us. local $Log::Log4perl::caller_depth = 1; return Log::Log4perl::get_logger(); } } { package Caller; my $logger = Wrapper::get_logger(); $logger->info("this should be Caller's category"); } ############################################################### This patch fixes my problem. (against version 0.51) --- Log4perl.pm.orig 2005-02-16 11:38:02.733776000 -0500 +++ Log4perl.pm 2005-02-16 11:38:52.834926000 -0500 @@ -300,10 +300,10 @@ if(!defined $class) { # Called as ::get_logger() - unshift(@args, scalar caller()); + unshift(@args, scalar caller($caller_depth)); } elsif($class eq __PACKAGE__ and !defined $args[0]) { # Called as ->get_logger() - unshift(@args, scalar caller()); + unshift(@args, scalar caller($caller_depth)); } elsif($class ne __PACKAGE__) { # Called as ::get_logger($category) unshift(@args, $class); |
From: root <Cha...@sk...> - 2005-02-13 11:32:43
|
Вы решили увеличить количество клиентов со следующего месяца? Вы хотите прорекламировать новую услугу или продукт Вашей компании? Хотите чтобы к Вам пришли новые покупатели? И не знаете как это можно сделать качественно, быстро и не дорого? Тогда закажите рекламу в интернете..... Рассылку по электронной почте... www.8811.ws Альметьевска |
From: Kevin G. <ke...@go...> - 2005-02-10 20:11:00
|
How are you catching the signals? If you don't catch the TERM signal, no DESTROY method will every be called, and that's where the lock file is removed. What platform are you running on? You might try editing FileRotate.pm and add print statements to see if a) the DESTROY method is called at exit, and b) if the unlink() call if failing for other reasons. ch...@gm... wrote: > Thanks for your fast answer. > It is a long running process, but the files were not deleted after exit. > I terminate with SIGTERM which I handlet in a signal hander. Do I have > to call a special termination/deregistration function of log4perl or > anything else? > > best regards > Chirs > > Kevin Goess wrote:go > >> Hey, Chris, >> >> My javamap::rollingfileappender is just a wrapper around >> Log::Dispatch::FileRotate >> (http://cpan.uwinnipeg.ca/htdocs/Log-Dispatch-FileRotate/Log/Dispatch/FileRotate.html) >> by Mark Pfeiffer, you could ask him. >> >> But from looking at the code it looks like the lockfiles should be >> deleted when the process exits. If you have a long running process >> that doesn't exit, then the lockfiles won't go away. >> >> ch...@gm... wrote: >> >>> hi! >>> >>> Im using your javamap::rollingfileappender and be quite happy with it. >>> but: it creates a lockfile .<name>.LCK.<num>. This stays at disk. Is >>> there a option to disable? >>> Or I'm wrong in closing? Is there a builtin way to cleanup? >>> To delete all .*.LCK.* every time is not very elegant. >>> >>> best regards >>> Chris >> >> >> > -- Happy Trails . . . Kevin M. Goess (and Anne and Frank) 904 Carmel Ave. Albany, CA 94706 (510) 525-5217 |
From: Kevin G. <ke...@go...> - 2005-02-09 18:22:44
|
Hey, Chris, My javamap::rollingfileappender is just a wrapper around Log::Dispatch::FileRotate (http://cpan.uwinnipeg.ca/htdocs/Log-Dispatch-FileRotate/Log/Dispatch/FileRotate.html) by Mark Pfeiffer, you could ask him. But from looking at the code it looks like the lockfiles should be deleted when the process exits. If you have a long running process that doesn't exit, then the lockfiles won't go away. ch...@gm... wrote: > hi! > > Im using your javamap::rollingfileappender and be quite happy with it. > but: it creates a lockfile .<name>.LCK.<num>. This stays at disk. Is > there a option to disable? > Or I'm wrong in closing? Is there a builtin way to cleanup? > To delete all .*.LCK.* every time is not very elegant. > > best regards > Chris -- Happy Trails . . . Kevin M. Goess (and Anne and Frank) 904 Carmel Ave. Albany, CA 94706 (510) 525-5217 |
From: mikko <da...@99...> - 2005-02-09 06:04:57
|
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1251"> </head> <BODY> <table cellspacing="0" cellpadding="0" width="652"> <tr> <td width="100%" align="left" valign="top"> <font face="Times New Roman"> <TABLE style="BORDER-RIGHT: #336699 1px solid; BORDER-TOP: #ccffcc 1px solid; BORDER-LEFT: #336699 1px solid; BORDER-BOTTOM: #ccffcc 1px solid" borderColor=#336699 cellSpacing=0 cellPadding=5 width=725 bgColor=#ffffff border=1> <TR> <TD vAlign=center align=middle width=711 bgColor= #336699> <div align="center"><FONT face=Verdana color=#33FFFF size=4>Предлагаем обучение теннису!<font color="#336699">___</font> тел. 8-926-5265144</FONT></div></TD> </TR> <TR> <TD vAlign=top align=left width=711 bgcolor="#CCCCCC" height="119"> <P align=left><FONT face=Verdana color=#0000FF size=3><strong>Индивидуальное занятие 1 час - 850 руб.(зал+тренер).<br> Районы: м.Таганская,м.Пролетарская,м.Академическая,м.Профсоюзная,<br> м.Новые Черемушки,м.Ленинский проспект,м.Тульская,м.Добрынинская.<br> Оплата производится за месяц(не менее 4-х занятий).<br> Возможны занятия в группах от 2 до 4 человек(приглашайте друзей и знакомых). Стоимость группового занятия: 1 час - 850 руб.</strong></FONT></P> </TD> </TR> <TR> <TD vAlign=center align=middle width=711 bgColor=#336699 height=30><div align="center"><FONT face=Verdana color=#ffffff size=4><FONT color=#33FFFF>тел. 8-926-5265144 <font color="#336699">___</font> e-mail: te...@fr... </FONT></FONT></div></TD> </TR> </TABLE> </font> </td> </tr> </table> </BODY> </html> |
From: Tom B. <tbo...@tr...> - 2005-02-08 20:41:53
|
I got this working with the log4perl.appender.NAME.Threshold = sub { $screen_threshold_level; } Tom |
From: Tom B. <tbo...@tr...> - 2005-02-08 19:14:03
|
Hello, I am working on getting log4perl incorporated into my perl scripts. I came across the following bug: It looks like for the LevelRange filter the dynamic code isn't working When trying to use a filter (Log::Log4perl::Filter::LevelRange) I was attempting to set the Min value dynamically. log4perl.filter.ScreenFilter.LevelMin = sub { $screen_log_level; } This was returning the error message that 'sub { $screen_log_level; }' was not a valid error level (DEBUG|INFO|WARN|ERROR|FATAL|ALL|OFF) in LevelRange.pm line 41 I then attempted to set a variable in the front of the config file screen_logging_level = sub { $screen_log_level; } log4perl.filter.ScreenFilter.LevelMin = ${screen_logging_level} and received the same error message. Anyhow, I am working getting log4perl incorporated in with many of my perl scripts. In general I am going to use three different appenders. log4perl.rootLogger = DEBUG, LOGFILE, SCREEN, EMAIL I want to set the level of SCREEN at runtime. (--verbose --verbose) etc without changing the levels of LOGFILE or EMAIL. As well allow you to shut off logging while running (--no-email-log) if you want. I can't figure out how to do this correctly. My first thought was to set the logging level per appender, but I can't figure out how to correctly do this. The only method I can find will change all appenders for a given package and I only want to change one. My next thought was to create separate lines in the config file like log4perl.rootLogger = DEBUG, LOGFILE log4perl.rootLogger = sub { "$screen_log_level, SCREEN" } However this changes LOGFILE level as well. Then I tried filters in the config file and noticed that I couldn't set the MinLevel dynamically (see bug above). Next I thought maybe I could dynamically create the filter and attach it to the appender but I can't figure out how to get a hold of one of the appenders. The only option I have left is to completely embed the config file in the perl code but I like having the config outside of perl. Anyone have any thoughts on this? I'm using version 0.51 perl 5.8.3 on SUSE. Thanks, Tom |
From: Mike S. <m...@pe...> - 2005-02-05 20:09:13
|
> Nagarajan Murugesan <nag...@at...> wrote: > > I just copy past your code for log4perl screen colour > level, surprisngly it was not working. > > Whats wrong with the code. I just changed the code by > looking at the user guide. Still is fails. Could please > take look at this code. Log::Log4perl::Appender::ScreenColoredLevels uses Term::ANSIColor and works on platforms supporting ANSI color sequences. Linux supports it. You're not explicitely saying which platform you're using, but concluding from > C:\ThinkInPerl\SWAT>perl log.pl it's Windows. I doubt that this will work. -- Mike Mike Schilli m...@pe... > > code in CPAN example: > ===================== > use Log::Log4perl qw(:easy); > > Log::Log4perl->init(\ <<'EOT'); > log4perl.category = DEBUG, Screen > log4perl.appender.Screen = \ > Log::Log4perl::Appender::ScreenColoredLevels > log4perl.appender.Screen.layout = \ > Log::Log4perl::Layout::PatternLayout > log4perl.appender.Screen.layout.ConversionPattern = > \ > %d %F{1} %L> %m %n > EOT > > # Appears black > DEBUG "Debug Message"; > > # Appears green > INFO "Info Message"; > > # Appears blue > WARN "Warn Message"; > > # Appears magenta > ERROR "Error Message"; > > # Appears red > > My Code: > ======== > use Log::Log4perl; > my $conf = q( > log4perl.category = DEBUG, Screen > log4perl.appender.Screen = > Log::Log4perl::Appender::ScreenColoredLevels > log4perl.appender.Screen.layout = > Log::Log4perl::Layout::PatternLayout > log4perl.appender.Screen.layout.ConversionPattern = > %d %F{1} %L> %m %n > ); > Log::Log4perl::init( \$conf ); > my $log = Log::Log4perl::get_logger(); > $log->info("Important Info1!"); > $log->debug("Important Info2!"); > $log->warn("Important Info3!"); > $log->error("Important Info4!"); > $log->fatal("Important Info5!"); > > This gives the output as > > C:\ThinkInPerl\SWAT>perl log.pl > > > It does not print in different color. > Can you please help me out. > > Thanks, > Nagarajan > |
From: postmaster <cla...@sk...> - 2005-02-05 05:06:30
|
>¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< Добрый дeнь! Вы решили увeличить количecтво клиeнтoв со cлeдующeго мecяца? Или хотите nрoреклaмировать нoвую уcлугу или nрoдукт Вaшей koмnaнии? И не знaете кaк это можнo сдeлать качественнo, быстро и не дoрогo? Тoгда рассылки по элeктронной почте, идеальный для Вас выбор! >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< Все вoпрocы и пoжелания мoжнo задавaть nо телефону 9O5 2О3+9О+72 Можетe звонить с любoгo телефoнa. icq 292593973 Дonoлнительные тeлефоны - 9О5 I44+5З+18, 9lб ОI9+20+5Ч >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< >¤< |
From: Naomi G. <ser...@gc...> - 2005-02-03 19:10:20
|
<html> <head> <title>Untitled Document</title> <meta http-equiv="Content-Type" content="text/html; charset=windows-1251"> </head> <body bgcolor="#FFFFFF" text="#000000"> <table width="452" border="0" cellspacing="0" cellpadding="0" align="center"> <tr> <td colspan="3" bgcolor="#FF9900" height="53"> <div align="center"><b><font size="5" color="#FFFF66">Доставка электронной рекламы</font></b></div> </td> </tr> <tr> <td height="58" width="33%" bgcolor="#FFFF99"> <div align="center">email</div> </td> <td height="58" width="33%" bgcolor="#FFFF66"> <div align="center"><font size="6"><b><font color="#0000CC">@</font></b></font></div> </td> <td height="58" width="33%" bgcolor="#FFFF33"> <div align="center"><font color="#666666">(095) 795-47-82</font></div> </td> </tr> </table> </body> </html> |
From: Mike S. <m...@pe...> - 2005-02-02 06:47:48
|
---------- Forwarded message ---------- From: Nagarajan Murugesan <nag...@at...> To: log...@pe... Subject: Log4perl color coded screen Date: Mon, 31 Jan 2005 23:56:13 -0800 Hi Mike, I just copy past your code for log4perl screen colour level, surprisngly it was not working. Whats wrong with the code. I just changed the code by looking at the user guide. Still is fails. Could please take look at this code. code in CPAN example: ===================== use Log::Log4perl qw(:easy); Log::Log4perl->init(\ <<'EOT'); log4perl.category = DEBUG, Screen log4perl.appender.Screen = \ Log::Log4perl::Appender::ScreenColoredLevels log4perl.appender.Screen.layout = \ Log::Log4perl::Layout::PatternLayout log4perl.appender.Screen.layout.ConversionPattern = \ %d %F{1} %L> %m %n EOT # Appears black DEBUG "Debug Message"; # Appears green INFO "Info Message"; # Appears blue WARN "Warn Message"; # Appears magenta ERROR "Error Message"; # Appears red My Code: ======== use Log::Log4perl; my $conf = q( log4perl.category = DEBUG, Screen log4perl.appender.Screen = Log::Log4perl::Appender::ScreenColoredLevels log4perl.appender.Screen.layout = Log::Log4perl::Layout::PatternLayout log4perl.appender.Screen.layout.ConversionPattern = %d %F{1} %L> %m %n ); Log::Log4perl::init( \$conf ); my $log = Log::Log4perl::get_logger(); $log->info("Important Info1!"); $log->debug("Important Info2!"); $log->warn("Important Info3!"); $log->error("Important Info4!"); $log->fatal("Important Info5!"); This gives the output as C:\ThinkInPerl\SWAT>perl log.pl It does not print in different color. Can you please help me out. Thanks, Nagarajan |
From: <Nar...@si...> - 2005-01-31 17:11:27
|
Hi, I'm very much new to log4perl. I find it very much useful. I want to create a log file every day so that it will be easy to check perl scripts are working fine. At the moment I mange to create a log file but not sure the bits i need to add so that a new log file is been created every day. Cheers, Narayan ----------------------------------------------------------------------------------------------------- Narayanan Yadapadi SITA Advanced Travel Solutions Tel: +44 (0) 1483 521219(D) Fax: +44 (0) 1483 414122 Email: nar...@si... This e-mail contains information which is SITA - Company Confidential All sita.int addresses have changed to sita.aero |
From: Mark K. <mar...@bt...> - 2005-01-31 10:22:55
|
Sorted! Thanks :) > -----Original Message----- > From: Mike Schilli [mailto:m...@pe...] > Sent: 30 January 2005 03:44 > To: Mark Knoop > Cc: Mike Schilli; log...@li... > Subject: RE: > > > On Sat, 29 Jan 2005, Mark Knoop wrote: > > > Thanks Mike. file_switch() works fine. Still couldn't get > > Log::Dispatch::FileRotate working. > > install Log-Dispatch-FileRotate gave me a 404 and if I just download the > > cpan module and install it manually it doesn't seem to work. > > Try now, I've uploaded a PPD distribution of Log::Dispatch::FileRotate to > the log4perl repository. > > -- Mike > > Mike Schilli > m...@pe... > > > I would be > > interested to know if anyone has got it working in ActivePerl > but for now > > file_switch does the trick. > > Cheers > > Mark > > > > > -----Original Message----- > > > From: Mike Schilli [mailto:m...@pe...] > > > Sent: 28 January 2005 21:59 > > > To: log...@li... > > > Cc: Mark Knoop > > > Subject: > > > > > > > > > "Mark Knoop" <mar...@bt...> wrote: > > > > > > > Apologies if this is covered somewhere already. > > > > > > > I have had some fun trying to rotate a log4perl log file. > > > > > > > I tried switch_file with Log4perl::Dispatch::File and > > > > Log4perl::Appender::File but there doesn't seem to be a switch_file > > > > method present for either > > > > > > Sorry, that's a documentation bug. Log4perl::Appender::File has a > > > file_switch() method (the docs said "switch_file()", I've corrected it > > > in 0.52). > > > > > > > so I decided to use > > > > Log::Dispatch::FileRotate instead but it seems it is not present in > > > > the http://log4perl.sourceforge.net/ppm repository. > > > > > > Log::Dispatch::FileRotate is a separate module on CPAN, not > bundled with > > > Log4perl, try > > > > > > ppm> install Log-Dispatch-FileRotate > > > > > > -- Mike > > > > > > Mike Schilli > > > m...@pe... > > > > > > > > > > > > > > |
From: Mike S. <m...@pe...> - 2005-01-30 03:44:09
|
On Sat, 29 Jan 2005, Mark Knoop wrote: > Thanks Mike. file_switch() works fine. Still couldn't get > Log::Dispatch::FileRotate working. > install Log-Dispatch-FileRotate gave me a 404 and if I just download the > cpan module and install it manually it doesn't seem to work. Try now, I've uploaded a PPD distribution of Log::Dispatch::FileRotate to the log4perl repository. -- Mike Mike Schilli m...@pe... > I would be > interested to know if anyone has got it working in ActivePerl but for now > file_switch does the trick. > Cheers > Mark > > > -----Original Message----- > > From: Mike Schilli [mailto:m...@pe...] > > Sent: 28 January 2005 21:59 > > To: log...@li... > > Cc: Mark Knoop > > Subject: > > > > > > "Mark Knoop" <mar...@bt...> wrote: > > > > > Apologies if this is covered somewhere already. > > > > > I have had some fun trying to rotate a log4perl log file. > > > > > I tried switch_file with Log4perl::Dispatch::File and > > > Log4perl::Appender::File but there doesn't seem to be a switch_file > > > method present for either > > > > Sorry, that's a documentation bug. Log4perl::Appender::File has a > > file_switch() method (the docs said "switch_file()", I've corrected it > > in 0.52). > > > > > so I decided to use > > > Log::Dispatch::FileRotate instead but it seems it is not present in > > > the http://log4perl.sourceforge.net/ppm repository. > > > > Log::Dispatch::FileRotate is a separate module on CPAN, not bundled with > > Log4perl, try > > > > ppm> install Log-Dispatch-FileRotate > > > > -- Mike > > > > Mike Schilli > > m...@pe... > > > > > > > |
From: Mark K. <mar...@bt...> - 2005-01-29 16:13:48
|
Thanks Mike. file_switch() works fine. Still couldn't get Log::Dispatch::FileRotate working. install Log-Dispatch-FileRotate gave me a 404 and if I just download the cpan module and install it manually it doesn't seem to work. I would be interested to know if anyone has got it working in ActivePerl but for now file_switch does the trick. Cheers Mark > -----Original Message----- > From: Mike Schilli [mailto:m...@pe...] > Sent: 28 January 2005 21:59 > To: log...@li... > Cc: Mark Knoop > Subject: > > > "Mark Knoop" <mar...@bt...> wrote: > > > Apologies if this is covered somewhere already. > > > I have had some fun trying to rotate a log4perl log file. > > > I tried switch_file with Log4perl::Dispatch::File and > > Log4perl::Appender::File but there doesn't seem to be a switch_file > > method present for either > > Sorry, that's a documentation bug. Log4perl::Appender::File has a > file_switch() method (the docs said "switch_file()", I've corrected it > in 0.52). > > > so I decided to use > > Log::Dispatch::FileRotate instead but it seems it is not present in > > the http://log4perl.sourceforge.net/ppm repository. > > Log::Dispatch::FileRotate is a separate module on CPAN, not bundled with > Log4perl, try > > ppm> install Log-Dispatch-FileRotate > > -- Mike > > Mike Schilli > m...@pe... > > |
From: Mike S. <m...@pe...> - 2005-01-28 21:59:43
|
"Mark Knoop" <mar...@bt...> wrote: > Apologies if this is covered somewhere already. > I have had some fun trying to rotate a log4perl log file. > I tried switch_file with Log4perl::Dispatch::File and > Log4perl::Appender::File but there doesn't seem to be a switch_file > method present for either Sorry, that's a documentation bug. Log4perl::Appender::File has a file_switch() method (the docs said "switch_file()", I've corrected it in 0.52). > so I decided to use > Log::Dispatch::FileRotate instead but it seems it is not present in > the http://log4perl.sourceforge.net/ppm repository. Log::Dispatch::FileRotate is a separate module on CPAN, not bundled with Log4perl, try ppm> install Log-Dispatch-FileRotate -- Mike Mike Schilli m...@pe... |
From: Mark K. <mar...@bt...> - 2005-01-27 15:53:22
|
Hi Apologies if this is covered somewhere already. I have had some fun trying to rotate a log4perl log file. I tried switch_file with Log4perl::Dispatch::File and Log4perl::Appender::File but there doesn't seem to be a switch_file method present for either so I decided to use Log::Dispatch::FileRotate instead but it seems it is not present in the http://log4perl.sourceforge.net/ppm repository. Am I missing something or is it just not supported in ActivePerl? If not what would you suggest is the best way to achieve something similar? Kind regards Mark |
From: <hu...@sk...> - 2005-01-14 17:39:43
|
!PЕKЛАМA - ДВИГАТЕЛЬ ТОPГOВЛИ! В этoм никтo не сомнeвается, нo вcе пoчeму-то в этo не вeрят и не реkлaмируют свoю прoдуkцию и уcлуги, думaя, что мoгут обойтиcь и без нее. Потенциaльные kлиeнты без рekлaмы не найдут Вac ниkогда, cдeлaйте им нaвстречу пeрвый шaг. Звoнитe, и мы cможeм Вам пoмочь в развитии бизнeca и в привлечении новых клиентов, путeм рaссылки Вaшeго реkламнoго сообщения по элеkтронной почте и по aсьkе. +7 905 2O3 9O 72 ICQ 28367Зl70 +7 9O5 lЧ4 53 l8 +7 926 2I1 54 8O +7 095 l09 57 O6 |
From: Mike S. <m...@pe...> - 2005-01-13 06:29:23
|
On Mon, 10 Jan 2005 Jam...@ub... wrote: > I was wondering if it would be possible to throttle messages based > on the rate (number) of messages. This feature would be useful if > you would like to control the number of messages being sent over a > period of time. There's the Limit appender, limiting the number of messages over a given time period: http://log4perl.sourceforge.net/d/Log/Log4perl/Appender/Limit.html And, new with L4p 0.51, there's the Buffer appender, buffering messages until a user-defined trigger gets called: http://log4perl.sourceforge.net/d/Log/Log4perl/Appender/Buffer.html If none of these fits your needs, you can define your own composite appender, just check out the source code of either of the above and extend them with your application-specific logic. -- Mike Mike Schilli m...@pe... |