From owner-freebsd-isp Sat May 22 21:15:37 1999 Delivered-To: freebsd-isp@freebsd.org Received: from roble.com (roble.com [199.108.85.50]) by hub.freebsd.org (Postfix) with ESMTP id 4E46214D74 for ; Sat, 22 May 1999 21:15:35 -0700 (PDT) (envelope-from sendmail@roble.com) Received: from roble2.roble.com (roble2.roble.com [199.108.85.52]) by roble.com (Roble1b) with SMTP id VAA21812 for ; Sat, 22 May 1999 21:15:40 -0700 (PDT) Date: Sat, 22 May 1999 21:15:33 -0700 (PDT) From: Roger Marquis To: freebsd-isp@FreeBSD.ORG Subject: Re: Web Statistics break up program. In-Reply-To: <199905210016.KAA08044@metva.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 21 May 1999, Enno Davids wrote: > The correct solution, is to 'mv' your logfile > to another temporary name in the same filesystem, then null the real name & > reset owners and permissions, then signal apache and then move the logfile > away to the archived name. The "correct" solution is to do whatever works on your system. For 99% of apache websites there is no need to HUP the httpd daemon and interrupt transfers in progress. And if anyone has been able to produce a race condition with "cp logfile logfile.bk;cp /dev/null logfile" they haven't spoken up. Having used this technique for years without a race condition it would appear to be a false alarm. The one disadvantage of copying /dev/null is that it is possible to lose log entries on busy servers however, from checking log files and rotated logfiles, it would have to be an extremely busy server to lose log entries. -- Roger Marquis Roble Systems Consulting http://www.roble.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message