From owner-freebsd-isp Thu May 20 9:22:52 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 4463015011 for ; Thu, 20 May 1999 09:22:45 -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 JAA25609 for ; Thu, 20 May 1999 09:22:46 -0700 (PDT) Date: Thu, 20 May 1999 09:22:43 -0700 (PDT) From: Roger Marquis To: freebsd-isp@FreeBSD.ORG Subject: Re: Web Statistics break up program. In-Reply-To: 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 > And on several of our servers will miss some events we need in the log. > Any entries that fall between the two 'cp' commands get zapped. (btw: It > would be better to move the 'chmod' after the second 'cp' to reduce this) > These events will be gone forever and may represent billable or auditable > content. beware... Sure, depending on system load you could lose a log entry between "cp logfile logfile.archive" and "cp /dev/null logfile" but you have to consider this in context. If you're running an extremely heavily loaded server i.e., millions of hits per day AND you absolutely must have every single log entry THEN you wouldn't use this method. But really, how many websites have meet of those requirements? As for race conditions this also has to be considered in context. In theory a race condition would only occur if httpd was writing data faster than cp could copy it. Unless the destination media couldn't accept data at the rate httpd was writing this would never happen. -- 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