Information missing with piped Log setting for ErrorLog

[Shibi NS <shibi.ns@xxxxxxxxx>]

Hello All,

Error log setting without piped logging feature

LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" common
TransferLog '| rotatelogs \logs\access_log.%y%m%d 1M  common';
ErrorLog      '| rotatelogs \logs\error_log.%y%m%d 1M  ';

Error log setting with piped logging feature

LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" common
TransferLog '\logs\access_log.%y%m%d';
ErrorLog      ' \logs\error_log.%y%m%d';

What I could noticed is when piped logging used some of the information in log files are missing in log.

Applied following commands for both the configuration to generate the error log file

$APACHE_HOME/bin/httpd -f /apps/conf/httpd.conf -k stop
$APACHE_HOME/bin/httpd -f /apps/conf/httpd.conf


Error log without piped logging feature

URS server process 17087 shutting down...
[Sun Nov 22 11:10:22 2009] [notice] Apache/2.2.9 (Unix) mod_perl/2.0.4 Perl/v5.8.8 configured -- resuming normal operations
URS server process 17106 shutting down...
URS server process 17103 shutting down...
URS server process 17101 shutting down...
URS server process 17104 shutting down...
URS server process 17105 shutting down...
URS server process 17107 shutting down...
URS server process 17109 shutting down...
URS server process 17102 shutting down...
URS server process 17110 shutting down...
URS server process 17108 shutting down...
[Sun Nov 22 11:10:26 2009] [notice] caught SIGTERM, shutting down
URS server process 17097 shutting down...
 

Error log with piped logging feature
URS server process 16906 shutting down...
[Sun Nov 22 11:08:41 2009] [notice] Apache/2.2.9 (Unix) mod_perl/2.0.4 Perl/v5.8.8 configured -- resuming normal operations

Any reason why this behavior ? I am more worried about red highlighted info missing

--Shibi Ns--