Return-Path: Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 80790 invoked by uid 500); 23 Jan 2003 03:19:53 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 80779 invoked from network); 23 Jan 2003 03:19:53 -0000 Received: from goliath.cnchost.com (207.155.252.47) by 208.185.179.12.available.above.net with SMTP; 23 Jan 2003 03:19:53 -0000 Received: from RCSV650.rowe-clan.net (www1.rowe-clan.net [208.176.192.146]) by goliath.cnchost.com id WAA01084; Wed, 22 Jan 2003 22:20:00 -0500 (EST) [ConcentricHost SMTP Relay 1.15] Errors-To: Message-Id: <5.2.0.9.2.20030122205941.0358f418@pop3.rowe-clan.net> X-Sender: wrowe%rowe-clan.net@pop3.rowe-clan.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 22 Jan 2003 21:01:25 -0600 To: users@httpd.apache.org From: "William A. Rowe, Jr." Cc: users@httpd.apache.org In-Reply-To: <3E2F57B6.26506129@sedivy.com> References: <3E2EF70A.DBCB28B4@shawcable.com> <01c301c2c259$062bd910$08071bce@WS4> <3E2F255E.586F3799@shawcable.com> <01fb01c2c26f$d190c780$08071bce@WS4> <3E2F41B3.C8349D0A@shawcable.com> <3E2F4488.7F7A07CE@sedivy.com> <3E2F4FF6.BC2C2E39@shawcable.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: 208.185.179.12.available.above.net 1.6.2 0/1000/N Subject: Re: [users@httpd] RotateLogs At 08:47 PM 1/22/2003, Ladislav Sedivy wrote: >Selmer Ausland wrote: >> >> NP Ladislav, I had to # >> >> # CustomLog "|D:/Apache2/bin/rotatelogs.exe D:/logs/access_log 86400" >> common >> # TransferLog "|D:/Apache2/bin/rotatelogs.exe D:/logs/access_log 86400" >> >> and revert back to >> >> CustomLogs logs/access.log common >> >> Access log was not working at all with the above. >> >> Is this a bug in Apache 2.0.44? or ????? >> >> Error log portion works. Any ideas? >> >> Thanks. Selmer > >These are exactly my findings. I even rebuilt rotatelogs.exe from >2.0.43 sources to no avail. It definitely looks like a bug in 2.0.44 >server. I'm just surprised nobody mentioned it yet. Theory: The logging code now trys to lock the resource (file) to prevent the parent and child process (or multiple child processes, when we get there) from overwriting one another's entries. I say trys because I'm not certain what exactly will happen when that resource is a pipe and not a file. Researching. Bill --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org