log4perl-devel — Ongoing log4perl development

Re: [log4perl-devel] Log4perl test Casesx

[Mike <m...@pe...>]

On Mon, 27 Sep 2004, Kevin Goess wrote:

> Rita, every time we add a feature or correct a bug in the log4perl 
> libraries, we're going to add test cases for the new feature or the 
> bugfix.  So, yes, if you want the tests to work on the current 
> libraries, you need to use the current tests.

Ritu,

let me add to Kevin's comments: If you write your own appender, you 
should bundle it in your own distribution and provide test cases for
it, independently of Log::Log4perl.

Our API should always be backwards compatible, unless for a good reason
(this has never happened as far as I remember, and should it one day, only
for a very good reason and it's gonna be announced boldly) or, of course 
if someone introduced a bug :).

As Kevin has pointed out, our test suite is subject to constant 
change, relying on it won't work. Your test cases should be independent
of them. Hope that helps!

-- 
-- Mike
Mike Schilli
m...@pe...

Re: [log4perl-devel] Log4perl test Cases

[Kevin G. <ke...@go...>]

Rita, every time we add a feature or correct a bug in the log4perl 
libraries, we're going to add test cases for the new feature or the 
bugfix.  So, yes, if you want the tests to work on the current 
libraries, you need to use the current tests.


Rit...@ub... wrote:
> Hi,
> We have written an in-house appender and a logger as an extension to standard Log4perl and it works fine with other appenders and the standard Log4perl  Logger. 
> I have added all the test cases that are provided with Log4perl from CPAN to prove that our software is compatible with original Log4perl.
> 
> What I want to know that every time, if I upgrade the Log4perl, do I have to copy all the test cases again? How often these test cases change?
> And if there is a backward compatibility? Recently I have observed that due to upgrade from Log4perl 0.42 to 0.48, one of my test failed in 014ConfErr.t.
> 
> After investigating, I have found that that was due to the change in error message text in one of the modules.
> I would appreciate if someone can answer my questions at the earliest.
> 
> Thanks & Regards,
> Ritu Kohli
> UBS Investment Bank
> Tel: +44-(0)20 7567 6806
> 
> 
> 
> Visit our website at http://www.ubs.com
> 
> This message contains confidential information and is intended only 
> for the individual named.  If you are not the named addressee you 
> should not disseminate, distribute or copy this e-mail.  Please 
> notify the sender immediately by e-mail if you have received this 
> e-mail by mistake and delete this e-mail from your system.
> 
> E-mail transmission cannot be guaranteed to be secure or error-free 
> as information could be intercepted, corrupted, lost, destroyed, 
> arrive late or incomplete, or contain viruses.  The sender therefore 
> does not accept liability for any errors or omissions in the contents 
> of this message which arise as a result of e-mail transmission.  If 
> verification is required please request a hard-copy version.  This 
> message is provided for informational purposes and should not be 
> construed as a solicitation or offer to buy or sell any securities or 
> related financial instruments.
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> log4perl-devel mailing list
> log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4perl-devel

-- 
Happy Trails . . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217

[log4perl-devel] Log4perl test Cases

[<Rit...@ub...>]

Hi,
We have written an in-house appender and a logger as an extension to =
standard Log4perl and it works fine with other appenders and the =
standard Log4perl  Logger.=20
I have added all the test cases that are provided with Log4perl from =
CPAN to prove that our software is compatible with original Log4perl.

What I want to know that every time, if I upgrade the Log4perl, do I =
have to copy all the test cases again? How often these test cases =
change?
And if there is a backward compatibility? Recently I have observed that =
due to upgrade from Log4perl 0.42 to 0.48, one of my test failed in =
014ConfErr.t.

After investigating, I have found that that was due to the change in =
error message text in one of the modules.
I would appreciate if someone can answer my questions at the earliest.

Thanks & Regards,
Ritu Kohli
UBS Investment Bank
Tel: +44-(0)20 7567 6806



Visit our website at http://www.ubs.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.

[log4perl-devel] =?Windows-1251?B?0e/u8PLo4u375SD47vDy+y3s6O7x8ujs8+v/8u7wIM/u4uXwIGd5bQ==?=

[pierre <kai...@ya...>]

Рады предложить Вам самый простой и экономичный способ преобразить свое тело, подтянуть мыжцы бедер и ягодиц 
 улучшить форму тела,  убрать целлюлит !!! 
Суперакция !! Доставка бесплатна по всей РФ! Узнайте подробности на нашей странице: 

http://www.pokupki.net

Re: [log4perl-devel] Configuration question

[Mike S. <mik...@gm...>]

On Tue, 21 Sep 2004 16:21:21 +0200, Albert Vila <av...@im...> wrote:
>     How can I initialize the log4perl with the main logger.conf and add
> a new custom appenders?
>     The init method erases any previous initialization. Is there an
> init_append like method?

We've thought about this issue a while ago, but got away from it
because of implications like users accidently overwriting previous
settings. Nobody stops you from dynamically assembling your conf file,
though, so you could still "add" configuration lines before calling
"init".

It would be helpful to know what the purpose of the additional
appender is -- it's possible that you could use a custom filter
instead.

-- Mike

[log4perl-devel] Configuration question

[Albert V. <av...@im...>]

Hi

    I've got a configuration problem. We have a main logger.conf 
containing the main configuration options, with their appenders, 
layouts, etc. However, sometimes, we need a custom logger appender in 
addition to the main configuration.
    How can I initialize the log4perl with the main logger.conf and add 
a new custom appenders?

    The init method erases any previous initialization. Is there an 
init_append like method?


Thanks

RE: [log4perl-devel] Additional logging methodology

[Aldrich, T. <tim...@cs...>]

 
> Here's a way to approach the problem using a separate log category. 
> It's probably a matter of taste when choosing between this or 
> creating a 
> new log level.  Although this way does make pretty clear in 
> the program 
> code that the purpose and destination of the two log messages 
> is different.
> 
> $logger       = Log::Log4perl::init('some.category');
> $statuslogger = Log::Log4perl::init('status');
> 
> $logger->debug("here is a regular debug message");
> 
> $status_logger->info("program ended at @{[scalar localtime]}");
> 
schweet ! Thank you so much ! now I don't feel naughty for using
depricated code.

R/S
Timothy Aldrich
---------------

-- 


==============================================================================
This message is for the sole use of the intended recipient. If you received
this message in error please delete it and notify us. If this message was
misdirected, CSFB does not waive any confidentiality or privilege. CSFB
retains and monitors electronic communications sent through its network.
Instructions transmitted over this system are not binding on CSFB until they
are confirmed by us. Message transmission is not guaranteed to be secure.
==============================================================================

Re: [log4perl-devel] Additional logging methodology

[Kevin G. <ke...@go...>]

Mike Schilli wrote:
> Aldrich, Timothy wrote on 9/15/2004, 10:11 AM:
> 
> it's something people who are 
> not familiar with the categories concept would jump right into for tasks 
> that could be solved much more elegantly with categories. With your 
> requirements, though, it makes sense. Another option would be a custom 
> filter grepping for certain keywords (like "[status]...") in the log 
> message and forwarding matching ones to the appropriate appender.

Here's a way to approach the problem using a separate log category. 
It's probably a matter of taste when choosing between this or creating a 
new log level.  Although this way does make pretty clear in the program 
code that the purpose and destination of the two log messages is different.

$logger       = Log::Log4perl::init('some.category');
$statuslogger = Log::Log4perl::init('status');

$logger->debug("here is a regular debug message");

$status_logger->info("program ended at @{[scalar localtime]}");


-- 
Happy Trails . . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217

RE: [log4perl-devel] Additional logging methodology

[Mike S. <m...@pe...>]

Aldrich, Timothy wrote on 9/15/2004, 10:11 AM:

 > adding a level called STATUS would be a simple way to sprinkle in
 > $logger->status() messages designed for this new log without refactoring
 > my whole logging methodology.
 >
 > _Why_ is this deprecated , am I missing a draw-back to this approach ?
 >

I guess the main reason is that it's an additional hurdle for Log4X 
users to find non-standard log levels. And it's something people who are 
not familiar with the categories concept would jump right into for tasks 
that could be solved much more elegantly with categories. With your 
requirements, though, it makes sense. Another option would be a custom 
filter grepping for certain keywords (like "[status]...") in the log 
message and forwarding matching ones to the appropriate appender.

--
-- Mike
Mike Schilli
m...@pe...

RE: [log4perl-devel] Additional logging methodology

[Aldrich, T. <tim...@cs...>]

Thank you for the reply. 

I erroneously called them categories , which means source classes.
what I should have called it was a log level.  My program is currently
using levels DEBUG through FATAL so going back through and moving meaningful
logging messages out of INFO would require a bit of work.  
I see in the docs that it's deprecated ( though really easy :) to create a
new level , which seems to be a perfect fit. This is what I was originally
asking when I mistakenly called them categories instead of levels.

adding a level called STATUS would be a simple way to sprinkle in
$logger->status() messages designed for this new log without refactoring
my whole logging methodology.

_Why_ is this deprecated , am I missing a draw-back to this approach ?



R/S
Timothy Aldrich
---------------
-- 


==============================================================================
This message is for the sole use of the intended recipient. If you received
this message in error please delete it and notify us. If this message was
misdirected, CSFB does not waive any confidentiality or privilege. CSFB
retains and monitors electronic communications sent through its network.
Instructions transmitted over this system are not binding on CSFB until they
are confirmed by us. Message transmission is not guaranteed to be secure.
==============================================================================

Re: [log4perl-devel] Additional logging methodology

[Mike S. <m...@pe...>]

Aldrich, Timothy wrote on 9/14/2004, 8:20 AM:

 > Now I would like to add logging to a different file that get's
 > appended to during the day.  This new rolling log needs different
 > information.  It should be general status messages . i.e. program
 > started , ended , by whom.  My question is , what is the best way to
 > implement this additional log ?
 > I could :
 > * Pollute my program with print statements (shudder)

Shudder, indeed :).

 > * Add a new Log::log4perl category.

Categories determine where a message came from within the system, not 
where it's going to, so I'd recommend leaving them untouched for what 
you're trying to accomplish.

 > * add a Log::log4perl filter

If you want different kinds of messages to go to different output sinks, 
log levels are the recommended way.

In your case, you could log the debug messages like

     $logger->debug("a lowlevel message");

and important events, like when the program started, stopped, etc., via

     $logger->info("Program started");

Then, use

     http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#c7fa8

to channel messages of different priorities to different log files.

--
-- Mike
Mike Schilli
m...@pe...

Re: [log4perl-devel] Additional logging methodology

[Mike S. <m...@pe...>]

Aldrich, Timothy wrote on 9/14/2004, 8:20 AM:

 > ow I would like to add logging to a different file that get's
 > appended to during the day.  This new rolling log needs different
 > information.  It should be general status messages . i.e. program
 > started , ended , by whom.  My question is , what is the best way to
 > implement this additional log ?

My first thought is to write out these status messages at a higher 
priority (e.g. INFO), than the DEBUG messages. Typically, DEBUG messages 
provide low-level information about the program flow, while INFO 
messages carry exactly what you have in mind, things like when the 
program started, ended, by whom, major events, etc.

If that's an option for you, leave the categories untouched (changing 
them is a bad idea, they determine where a message came from, not where 
it's going to) and just use

     $logger->info("Program started");

and

     $logger->debug("Some lowlevel info");

Then, use

     http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#c7fa8

to channel them into different log files.

--
-- Mike
Mike Schilli
m...@pe...

[log4perl-devel] Additional logging methodology

[Aldrich, T. <tim...@cs...>]

All,
	I have a large perl project that uses Log::log4perl to log 
everything to a text file.  If the program successfully completes
then this log file is deleted before the program terminates.  It is
invaluable to be able to crank up the category to DEBUG and watch
the file grow :)
	Now I would like to add logging to a different file that get's
appended to during the day.  This new rolling log needs different
information.  It should be general status messages . i.e. program
started , ended , by whom.  My question is , what is the best way to
implement this additional log ?
 I could :
* Pollute my program with print statements (shudder)
* Add a new Log::log4perl category.
* add a Log::log4perl filter

	I'm leaning towards categories because 
$logger->status("I started");
seems to be an easy fix , however the POD discourages the use of a new 
category.  Implementing a filter means I now have to include some type
of destination info in my log messages , and I don't want to revisit
all of my calls to the logger to add destination info !

Any help / insight / advice would be greatly appreciated

	

R/S____________
Timothy Aldrich

-- 



==============================================================================
This message is for the sole use of the intended recipient. If you received
this message in error please delete it and notify us. If this message was
misdirected, CSFB does not waive any confidentiality or privilege. CSFB
retains and monitors electronic communications sent through its network.
Instructions transmitted over this system are not binding on CSFB until they
are confirmed by us. Message transmission is not guaranteed to be secure.
==============================================================================

[log4perl-devel] =?Windows-1251?B?6uDqIO/u5OHo8ODy/CDv5fDx7u3g6w==?=

[evan <nc...@t-...>]

<html>
<head>
<title>Рассылка видео УСН</title>
<style type="text/css">
<!--
li {
	color: #466DA4;
}
tab {
	font-family: Geneva, Arial, Helvetica, sans-serif;
	font-size: 12px;
	color: #466DA4;
	text-align: center;
	background-color: #CFDBEB;
	padding: 10px;
}
tab2 {
	font-family: Geneva, Arial, Helvetica, sans-serif;
	font-size: 12px;
	color: #466DA4;
	background-color: #D7E1EE;
	padding-left: 10px;
	padding-right: 10px;
	padding-top: 10px;
	padding-bottom: 10px;
	text-align: justify;
}
-->
</style>
</head>

<body bgcolor="#eef1f7">
<table width="700" border="0" align="center" cellpadding="0" cellspacing="0">
  <tr>
    <td valign="top"><p align="center"><font color="#466DA4" size="3" face="Geneva, Arial, Helvetica, sans-serif"><strong>Образовательный 
        Центр</strong></font><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><br>
        предлагает вниманию руководителей предприятий,<br>
        специалистов кадровых служб и агентств </font></p>
      <hr color="#78A2DA">
      <p align="center"><font color="#ef7a1b" size="3" face="Geneva, Arial, Helvetica, sans-serif"><strong>18-19 сентября
	  </strong></font><font color="#466DA4" size="3" face="Geneva, Arial, Helvetica, sans-serif"><br>
        двухдневный семинар-тренинг по теме<br>
        <strong>&quot;Технология оценки и подбора персонала в организации&quot;</strong><br>
        </font></p>
      <hr color="#78A2DA">
      <strong><font color="#ef7a1b" size="2" face="Geneva, Arial, Helvetica, sans-serif"> 
      В программе семинара:</font></strong><br>
      <font color="#466DA4"><br>
      <font size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>• Методы 
      определения потребности в кадрах, анализ должностей, привязка кадрового 
      состава к оперативным и стратегическим целям организации.<br>
      • Подбор и расстановка кадров: как и где искать кандидатов на вакантные 
      должности.<br>
      • Методы оценки и отбора кандидатов (собеседование, структурное интервью, 
      тестирование, ассессмент-центр).<br>
      • Разработка структуры интервью.</strong><br>
      1. Система общих и частных критериев для оценки кандидата и определения 
      его соответствия рассматриваемой должности.<br>
      2. Оценка реальной заинтересованности кандидата в рассматриваемой работе 
      (исследование мотивационной сферы).<br>
      3. Оценка способности кандидата эффективно выполнять требуемую работу(исследование 
      профессионального потенциала).<br>
      4. Оценка управляемости и совместимости кандидата.<br>
      5. Оценка безопасности кандидата для компании.<br>
      <strong>• Практика подбора персонала на примере разнопрофильных организаций.<br>
      • Метод биографической поведенческой проверки достоверности данных, сообщаемых 
      кандидатом.<br>
      • Неречевые сигналы как эффективные источники информации о кандидате.</strong><br>
      1. Неречевые сигналы неискренности и сокрытия информации.<br>
      2. Способы &quot;работы&quot; с неречевыми сигналами неискренности в ходе 
      собеседования:<br>
      - фокусировка и &quot;зеркало&quot;;<br>
      - перевод на речевой план;<br>
      - метод обращения к жизненным фактам.<br>
      <strong>• Провокационные методы и деловые игры, применяемые в оценке кандидатов. 
      Анализ поведения кандидатов в ходе провокации.<br>
      • Приемы правильного выхода из собеседования. Отбор кандидатов по результатам 
      оценки.</strong><br>
      1. Суммирование оценок по основным критериям и подготовка итогового заключения 
      по кандидату.<br>
      2. Представление отобранных кандидатов лицу, принимающему решения.<br>
      <strong>• Типичные ошибки при подборе персонала (на примере разнопрофильных 
      организаций).<br>
      • Отработка практических приемов оценки кандидатов в ходе интервью. (Ролевые 
      игры с видеозаписью и разбором).</strong></font><br>
      </font> 
      <hr color="#78A2DA">
      <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong><br>
      Стоимость участия в семинаре - 7500 рублей, с учетом НДС.</strong><br>
      Форма оплаты любая (наличная или безналичная).<br>
      <strong>В стоимость входит:</strong> участие в работе семинара, раздаточный 
      материал, кофе-пауза, обед в ресторане.</font><font face="Geneva, Arial, Helvetica, sans-serif">
<p><font color="#466DA4" size="2">Тренинг проходит в Москве (м. Академическая). 
        <br>
        Начало - в 10 часов, окончание в 17.30-18.00 (в двухдневном формате). 
        </font></p>
      <p><font color="#466DA4" size="2"><strong>Регистрация участников обязательна.</strong> 
        Для регистрации необходимо сообщить следующие данные: наименование организации, 
        ИНН,КПП, юридический адрес, телефон, факс, Ф.И.О. участников, контактное 
        лицо.</font></p>
      <p><font color="#466DA4" size="2">Если необходимо бронировать гостиницу, 
        сообщайте даты приезда-отъезда заранее.</font></p>
      </font> 
      <hr color="#78A2DA">
      <font face="Geneva, Arial, Helvetica, sans-serif"> 
      <p><font color="#466DA4" size="2">При отсутствии возможности посетить семинар, 
        мы предлагаем приобрести видеоверсию семинара на DVD дисках или видеокассетах 
        (прилагается авторский раздаточный материал).<br>
        <strong>Стоимость  видеокурса  - 4500 рублей, с учетом НДС.</strong></font></p>
      <p><font color="#466DA4" size="2">На участие в семинаре и приобретение видеозаписей 
        оформляется полный пакет бухгалтерских документов.</font> </p>
      </font>
<hr color="#78A2DA">
      <p><font color="#ef7a1b" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>КОНТАКТНЫЕ 
        ТЕЛЕФОНЫ: (095) 788-73-28.</strong></font> <br>
        <br>
    </td>
  </tr>
</table>
</body>
</html>

[log4perl-devel] =?Windows-1251?B?5+Dw8+Hl5u376SDx5ezo7eDw?=

[mahlon <fr...@se...>]

<html>
<head>
<title>Рассылка видео УСН</title>
<style type="text/css">
<!--
li {
	color: #466DA4;
}
-->
</style>
</head>

<body bgcolor="#FFFFFF">
<table width="700" height="100%" border="1" align="center" cellpadding="0" cellspacing="0" bordercolor="C4A347" bgcolor="#faf2e7">
  <tr>
    <td valign="top"><p align="center"><font color="#466DA4" face="Geneva, Arial, Helvetica, sans-serif"><strong><br>
        <br>
        <font color="#B87A00" face="Georgia, Times New Roman, Times, serif">Образовательный 
        Центр</font></strong></font><font color="#B87A00" face="Georgia, Times New Roman, Times, serif"><br>
        <font size="3">приглашает руководителей предприятий, организаций, <br>
        учреждений всех форм собственности, руководителей кадровых служб</font></font><font color="#B87A00" size="3"><font face="Geneva, Arial, Helvetica, sans-serif"> 
        </font></font></p>
      <hr width="98%" size="1" color="#C4A347">
      <p align="center"><font color="#B87A00" size="3" face="Georgia, Times New Roman, Times, serif">принять 
        участие в зарубежном семинаре:</font><font color="#B87A00" size="3" face="Georgia, Times New Roman, Times, serif"><strong><br>
        &quot;Управление персоналом: мастерство и искусство&quot;,<br>
        </strong>проведение 
        которого запланировано</font><font color="#466DA4" size="3" face="Georgia, Times New Roman, Times, serif"><br>
        <strong><font color="#ef7a1b">в Греции (Афины - Лутраки) с<font face="Geneva, Arial, Helvetica, sans-serif"> 
        29.09.2004</font> г. по <font face="Geneva, Arial, Helvetica, sans-serif">04.10.2004</font>.</font></strong></font><font color="#466DA4" size="3" face="Geneva, Arial, Helvetica, sans-serif"> 
        </font></p>
      <hr width="98%" size="1" color="#C4A347">
      <div align="center"><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"> 
        <br>
        <strong>&nbsp;<font color="#B87A00">&nbsp;<font size="3" face="Georgia, Times New Roman, Times, serif">Внимание!!!</font></font></strong><font color="#B87A00" size="3" face="Georgia, Times New Roman, Times, serif"> 
        Затраты на участие в семинаре относятся на себестоимость. </font></font><font color="#B87A00" size="3" face="Georgia, Times New Roman, Times, serif">&nbsp; 
        </font> </div>
      <div align="justify"><font face="Geneva, Arial, Helvetica, sans-serif">
        <p align="center"><font color="#B87A00" size="3" face="Georgia, Times New Roman, Times, serif"><strong>&nbsp;&nbsp;Стоимость 
          семинара:</strong> 1570 евро (включая НДС, по курсу ЦБ на день оплаты).</font></p>
        </font> 
        <hr align="center" width="98%" size="1" color="#C4A347">
        <div align="center"><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><font color="#B87A00"><br>
          <font size="3" face="Georgia, Times New Roman, Times, serif">Зарегистрироваться для участия в семинаре и получить<br>
          дополнительную информацию Вы можете по <strong>телефону</strong>:</font></font></font> 
        </div>
        <p align="center"><font color="#ef7a1b" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>&nbsp;<font face="Verdana, Arial, Helvetica, sans-serif">&nbsp;<font size="3" face="Geneva, Arial, Helvetica, sans-serif">(095) 
          788-73-28</font></font></strong></font><br>
        </p>
      </div>
      
    </td>
  </tr>
</table>
</body>
</html>

[log4perl-devel] =?Windows-1251?B?wPHy8O7r7uPo/yDiIOHo5+3l8eU=?=

[tanju <dh...@t-...>]

<html>

<body bgcolor="#eef1f7">
<table width="700" border="0" align="center" cellpadding="0" cellspacing="0">
  <tr>
    <td valign="top"><p align="center"><font color="#466DA4" size="3" face="Geneva, Arial, Helvetica, sans-serif"><strong>Образовательный 
        Центр</strong></font><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><br>
        предлагает Вашему вниманию</font></p>
      <hr color="#78A2DA">
      <p align="center"><font color="#ef7a1b" size="3" face="Geneva, Arial, Helvetica, sans-serif"><strong>8 
        сентября</strong></font><font color="#466DA4" size="3" face="Geneva, Arial, Helvetica, sans-serif"><br>
        однодневный открытый семинар по теме <br>
        <strong>&quot;АКТУАЛЬНЫЕ ВОПРОСЫ БИЗНЕС-ПРОГНОЗИРОВАНИЯ.<br>
        Астрология в бизнесе&quot;</strong><br>
        </font></p>
      <hr color="#78A2DA">
      <strong><font color="#ef7a1b" size="2" face="Geneva, Arial, Helvetica, sans-serif"> 
      </font></strong> <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong><br>
      Стоимость участия в семинаре - 3900 рублей, с учетом НДС.</strong> <br>
      Форма оплаты любая (наличная или безналичная).</font><font face="Geneva, Arial, Helvetica, sans-serif">
      <p><font color="#466DA4" size="2"><strong>Регистрация участников обязательна.</strong></font></p>
      </font> 
      <hr color="#78A2DA">
      <font face="Geneva, Arial, Helvetica, sans-serif"> 
      <p><font color="#466DA4" size="2">При отсутствии возможности посетить семинар, 
        мы предлагаем приобрести <strong>видеоверсию семинара</strong> на DVD 
        дисках или видеокассетах (прилагается авторский раздаточный материал).<br>
        <strong>Стоимость видеокурса – 2 600 рублей, с учетом НДС.</strong></font></p>
      </font> 
      <hr color="#78A2DA">
      <font face="Geneva, Arial, Helvetica, sans-serif">&nbsp;</font> 
      <p><font color="#ef7a1b" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>КОНТАКТНЫЕ 
        ТЕЛЕФОНЫ: (095) 788-73-28.</strong></font> <br>
        <br>
    </td>
  </tr>
</table>
</body>
</html>

[log4perl-devel] Re: deleting a logger

[Christopher J. B. <cjb...@al...>]

thanks for the reply.

well i guess its not so much the loggers (or categories) that i care about,
but the appenders.  so lets say that pluginA gets loaded and it creates a
logger category (get_logger("My::PluginA")) and then programmatically
sticks a file appender on it that logs to file pluginA.log.  so pluginA
does its stuff then is unloaded, etc.

so what if pluginA gets loaded again, but this time it wants to attach a
different appender to logger My::PluginA (maybe specify a different log
file or something), but still use the same appender name.  won't that not
work as expected because now My::PluginA logger will have 2 appenders on
it, when we only want one.  err, actually it won't work because if the
appender name already exists, the global appenders hash won't be updated.

i've looked at the source for log4perl and if i'm not mistaken,
add_appender() looks at the global hash of appenders by name to see if it
already exists.  if it does, it won't actually put the new appender in the
global hash.

so i guess my problem is that i'm not using the module like it was intended. 
each time a plugin in loaded, it programmatically constructs an appender,
with the same name each time, but with possibly different attributes.

any suggestions or tips?  thank you.

Mike Schilli wrote:
> Christopher J. Bottaro wrote on 9/1/2004, 10:10 AM:
> 
>  > the problem is that when the module is unloaded, the
>  > logger is still there and after several loadings/unloadings, there are
>  > going to be many left over loggers and appenders sitting around in
> memory.
> 
> Loggers are singletons, get_logger($cat) just creates a logger for the
> given category once and returns a reference to it on subsequent calls.
> Unless you're requesting a logger for a different category every time,
> this shouldn't cause any problems -- or is there anything unusual going
> on when you 'unload' the module?
> 
> --
> -- Mike
> Mike Schilli
> m...@pe...
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click

Re: [log4perl-devel] deleting a logger

[Mike S. <m...@pe...>]

Christopher J. Bottaro wrote on 9/1/2004, 10:10 AM:

 > the problem is that when the module is unloaded, the
 > logger is still there and after several loadings/unloadings, there are
 > going to be many left over loggers and appenders sitting around in 
memory.

Loggers are singletons, get_logger($cat) just creates a logger for the 
given category once and returns a reference to it on subsequent calls. 
Unless you're requesting a logger for a different category every time, 
this shouldn't cause any problems -- or is there anything unusual going 
on when you 'unload' the module?

--
-- Mike
Mike Schilli
m...@pe...

[log4perl-devel] deleting a logger

[Christopher J. B. <cjb...@al...>]

hello,
i have a perl program that loads and unloads modules (like plugins).  the
main program will init log4perl and then create its logger simply by
calling get_logger().  a module is then dynamically loaded, a few methods
are executed, then it is unloaded.  when the module is loaded, it creates a
logger for it self simply by calling get_logger() and programmatically
attaching appenders.  the problem is that when the module is unloaded, the
logger is still there and after several loadings/unloadings, there are
going to be many left over loggers and appenders sitting around in memory.

is there a way i can delete a logger given its name?  and also delete all
appenders associated with it (given the appenders are not associated with
other loggers that are in use)?

thank you.

[log4perl-devel] Re: Problems with PAR executable

[Mike S. <m...@pe...>]

Johannes Kilian wrote on 9/1/2004, 3:40 AM:

 > Why does Config.pm require PatternLayout  and not
 > Log::Log4perl::Layout::PatternLayout?

Most likely because your Log4perl configuration file contains a line like

     log4perl.appender.FileApp.layout   = PatternLayout

which Log4perl processes fine by internally mapping it to

     log4perl.appender.FileApp.layout= Log::Log4perl::Layout::PatternLayout

but maybe this confuses PAR? Can you try it by using the latter instead?

--
-- Mike
Mike Schilli
m...@pe...

[log4perl-devel] Problems with PAR executable

[Johannes K. <jo...@vi...>]

Hi,

I tried to compile a perl script including log4perl using PAR's (PAR 
0.85) pp-command (pp 0.12)

The compile-Commandline looks like:
-----------------------------
pp --lib=..\lib -M Log::Log4perl::Filter::LevelRange -M 
Log::Log4perl::Layout::PatternLayout -M Log::Log4perl::Appender::File -M 
Log::Dispatch::Screen -M Time::Localtime -M XML::Twig --icon tree.ico -o 
.\output\test.exe test.pl
-----------------------------

Running the compiled exe-File I got the message:
------------------------------
Require to PatternLayout failed (No such file or directory) at 
Log/Log4perl/Config.pm line 453.
------------------------------

Why does Config.pm require PatternLayout  and not 
Log::Log4perl::Layout::PatternLayout?

Any help welcome

Johannes

[log4perl-devel] =?Windows-1251?B?6u7t8vDu6+jw8/756OUg7vDj4O37?=

[patricia <ha...@t-...>]

<html>


<body bgcolor="#eef1f7">
<table width="700" border="0" align="center" cellpadding="0" cellspacing="0">
  <tr>
    <td valign="top"><p align="center"><font color="#466DA4" size="3" face="Geneva, Arial, Helvetica, sans-serif"><strong>Образовательный 
        Центр</strong></font><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><br>
        предлагает вниманию главных бухгалтеров и налоговых консультантов,<br>
        финансовых директоров и руководителей предприятий </font></p>
      <hr color="#78A2DA">
      <p align="center"><font color="#ef7a1b" size="3" face="Geneva, Arial, Helvetica, sans-serif"><strong>9 
        сентября </strong></font><font color="#466DA4" size="3" face="Geneva, Arial, Helvetica, sans-serif"><br>
        однодневный открытый семинар по теме <br>
        <strong>&quot;Особенности взаимоотношений с контролирующими органами&quot;</strong><br>
        </font></p>
      <hr color="#78A2DA">
      <strong><font color="#ef7a1b" size="2" face="Geneva, Arial, Helvetica, sans-serif"> 
      В программе семинара:</font></strong><br>
      <font color="#466DA4"><br>
      </font><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>1.</strong> 
      <strong>Кто контролирует организацию.</strong> Каково действующее законодательство 
      в этой области.</font> 
      <p><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>2. 
        НАЛОГОВЫЕ ОРГАНЫ</strong><br>
        - права и обязанности налогоплательщика, плательщика сборов, налогового 
        агента;<br>
        - права и обязанности налогового органа;<br>
        - контроль за применением ККМ;<br>
        - налоговые проверки – их виды, как и когда они могут назначаться, как 
        должны быть оформлены, какой период могут затрагивать, возможна ли повторная 
        проверка, на что имеют право проверяющие, как обжаловать акт налоговой 
        проверки.</font></p>
      <p><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>3. 
        ТАМОЖЕННЫЕ ОРГАНЫ</strong><br>
        - компетенция таможенных органов;<br>
        - как проходит проверка;<br>
        - права и обязанности налогоплательщика и таможенного органа.</font></p>
      <p><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>4. 
        ГОСУДАРСТВЕННЫЕ ВНЕБЮДЖЕТНЫЕ ФОНДЫ</strong><br>
        - что они контролируют, какие документы могут проверить;<br>
        - права и обязанности сторон;<br>
        - можно ли изменить решение проверяющих.</font></p>
      <p><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>5. 
        ИНСПЕКЦИЯ ПО ТРУДУ</strong><br>
        - к чему необходимо быть готовым;<br>
        - как и что проверяет инспекция по труду;<br>
        - если произошел несчастные случай на производстве;<br>
        - как заключить коллективный и трудовые договора так, чтобы не было претензий 
        инспектора по труду.</font></p>
      <p><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>6. 
        ЗАЩИТА ПРАВ ЮРИДИЧЕСКИХ ЛИЦ И ИНДИВИДУАЛЬНЫХ ПРЕДПРИНИМАТЕЛЕЙ ПРИ ПРОВЕДЕНИИ 
        ПРОЧИХ ВИДОВ ГОСУДАРСТВЕННОГО КОНТРОЛЯ (НАДЗОРА)</strong><br>
        - полномочия органов власти по назначению контроля;<br>
        - полномочия органов власти по защите прав организаций (предпринимателей);<br>
        - порядок проведения и рамки контроля;<br>
        - оформление результатов проверок.</font></p>
      <p><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>7. 
        ВОЗМЕЩЕНИЕ УБЫТКОВ, ПОНЕСЕННЫХ ОРГАНИЗАЦИЕЙ В СВЯЗИ С НЕПРАВОМЕРНЫМИ ДЕЙСТВИЯМИ 
        КОНТРОЛИРУЮЩИХ ОРГАНОВ</strong></font></p>
      <p><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>8. 
        КАК ОТСТОЯТЬ СВОЮ ПРАВОТУ В СУДЕ</strong> </font></p>
      <p><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>9. 
        ОТВЕТСТВЕННОСТЬ ОРГАНИЗАЦИИ И ЕЕ ДОЛЖНОСТНЫХ ЛИЦ, ОТВЕТСТВЕННОСТЬ ИНДИВИДУАЛЬНОГО 
        ПРЕДПРИНИМАТЕЛЯ</strong></font></p>
      <p><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>10. 
        ОТВЕТСТВЕННОСТЬ КОНТРОЛИРУЮЩИХ ОРГАНОВ И ИХ ДОЛЖНОСТНЫХ ЛИЦ</strong></font><br>
      </p>
      <hr color="#78A2DA">
      <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong><br>
      Стоимость участия в семинаре - 3900 рублей, с учетом НДС.</strong><br>
      Форма оплаты любая (наличная или безналичная).<br>
      <strong>В стоимость входит:</strong> участие в работе семинара, раздаточный 
      материал, кофе-пауза, обед в ресторане.</font><font face="Geneva, Arial, Helvetica, sans-serif">
<p><font color="#466DA4" size="2">Тренинг проходит в Москве (м. Академическая). 
        <br>
        Начало - в 10 часов, окончание в 17.30-18.00. </font></p>
      <p><font color="#466DA4" size="2"><strong>Регистрация участников обязательна.</strong> 
        Для регистрации необходимо сообщить следующие данные: наименование организации, 
        ИНН,КПП, юридический адрес, телефон, факс, Ф.И.О. участников, контактное 
        лицо.</font></p>
      <p><font color="#466DA4" size="2">Если необходимо бронировать гостиницу, 
        сообщайте даты приезда-отъезда заранее.</font></p>
      </font> 
      <hr color="#78A2DA">
      <font face="Geneva, Arial, Helvetica, sans-serif"> 
      <p><font color="#466DA4" size="2">При отсутствии возможности посетить семинар, 
        мы предлагаем приобрести видеоверсию семинара на DVD дисках или видеокассетах 
        (прилагается авторский раздаточный материал).<br>
        <strong>Стоимость видеокурса - 2600 рублей, с учетом НДС.</strong></font></p>
      </font> 
      <hr color="#78A2DA">
      <br>
      <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif">Также 
      в нашем Центре состоятся семинары по темам: </font><font face="Geneva, Arial, Helvetica, sans-serif"> 
      <p><font color="#ef7a1b" size="2"><strong>16 сентября 2004 года</strong></font><font color="#466DA4" size="2"> 
        <br>
        <strong>«Бухгалтерский и налоговый учет использования автомобиля в организации»</strong></font></p>
      <p><font color="#466DA4" size="2"><strong><font color="#ef7a1b">17 сентября 
        2004 года</font></strong><br>
        <strong>«Хозяйственные договоры и сделки: бухгалтерский и налоговый аспекты»</strong></font></p>
      <p><font color="#466DA4" size="2">При регистрации на 2 семинара – скидка 
        10%,<br>
        при регистрации на 3 семинара – четвертый Вы посещаете <strong><font color="#ef7a1b">бесплатно</font></strong>.</font></p>
      <p><font color="#466DA4" size="2">На участие в семинарах и приобретение 
        видеозаписей оформляется полный пакет бухгалтерских документов.</font></p>
      </font> 
      <hr color="#78A2DA">
      <p><font color="#ef7a1b" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>КОНТАКТНЫЕ 
        ТЕЛЕФОНЫ: (095) 788-73-28.</strong></font> <br>
        <br>
    </td>
  </tr>
</table>
</body>
</html>

Re: [log4perl-devel] File permission errors when forks switch uid's

[Kevin G. <ke...@go...>]

Mike Schilli wrote:
> Jason Thurston wrote on 8/27/2004, 4:11 AM:
> 
>  > Is there a way to specify that permissions to the log files be wide
>  > open ( -rw-rw-rw- ) ?
> 
> "perldoc -f umask" shows how to accomplish that.

Rather than making the log files world-writeable, you might be better 
off making them group writeable, giving the world read-only access, and 
if you set the SGID bit on the directory then they are to be sure to be 
owned by the same group (see 
http://www.library.yale.edu/~lso/workstation/docs/permissions/sgid.htm).

For instance, if your forking process runs as p1user and p2user and 
p3user and they are all a member of a group called "loguser", then you 
can do

#set the umask either in the perl script or in something like the 
#.bashrc script for each user via
umask 664

#create the directory
mkdir logdir/

#make sure the directory is group writeable
chmod g+w logdir

#make the directory SGID
chmod g+s logdir

#make it owned by the loguser group
chown loguser logdir

#the directory will now look like this,
#note the 's' in the permissions
drwxrwsr-x  2 kgoess loguser 4096 Aug 27 08:47 logdir/

#create a test file
touch logdir/foo

#the new file is now group writeable by the loguser group
-rw-rw-r--  1 kgoess loguser 0 Aug 27 08:50 foo






-- 
Happy Trails . . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217

Re: [log4perl-devel] File permission errors when forks switch uid's

[Mike S. <m...@pe...>]

Jason Thurston wrote on 8/27/2004, 4:11 AM:

 > Is there a way to specify that permissions to the log files be wide
 > open ( -rw-rw-rw- ) ?

"perldoc -f umask" shows how to accomplish that.

--
-- Mike
Mike Schilli
m...@pe...

[log4perl-devel] File permission errors when forks switch uid's

[Jason T. <jas...@ea...>]

I have a perl daemon that runs as root and forks children that run as 
other users.   Because it changes users I end up with permission 
problems using a file appenders.  Even if I open the file permissions up 
manually, it seems that when the files rotate they default back to (  
-rw-r--r-- ) and owned by whatever user caused the log switch/rollover. 
   Is there a way to specify that permissions to the log files be wide 
open ( -rw-rw-rw- ) ?   An alternate solution might be to have the 
logger dynamically create filenames with the current process' user name 
in the logs filename.  The former method is preferred but the latter is 
fine also.   I don't know how to implement either.   Does anyone have 
any tips on how to accomplish either of these methods or is there a 
better way to overcome this issue?

Thank you,
Jason