comment on

Based on the pathname to the log file, I am guessing this is unixy in nature.

If the log file is left open by Log4Perl (am not saying it is or isn't), and it is moved out of the way by some external (or even internal process), until the file is reopened by your process, it will continue to write to the old file handle, which may point to the newly renamed file, or a block of bytes on the disk no longer accessible from any directory entry.

I think that you need to get Log4Perl (or your process) to automatically reopen the file, or....

rename_log_file();
signal_process_to_reopen_log_file();
wait_for_process_to_reopen_log_file();
compress_or_process_old_log_file();
[download]

--MidLifeXis

In reply to Re: Log4perl is not writing into the log file when log file contents are cleared by MidLifeXis
in thread Log4perl is not writing into the log file when log file contents are cleared by vmraj

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks