Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 15785 invoked from network); 29 Jan 2004 21:50:27 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 29 Jan 2004 21:50:27 -0000 Received: (qmail 12376 invoked by uid 500); 29 Jan 2004 21:49:43 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 12347 invoked by uid 500); 29 Jan 2004 21:49:43 -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 12306 invoked from network); 29 Jan 2004 21:49:43 -0000 Received: from unknown (HELO out1.smtp.messagingengine.com) (66.111.4.25) by daedalus.apache.org with SMTP; 29 Jan 2004 21:49:43 -0000 X-Sasl-enc: mEicQjsRrvSR6NUCE7ptog 1075412986 Received: from usager55-41.hec.ca (usager55-41.hec.ca [132.211.55.41]) by mail.messagingengine.com (Postfix) with ESMTP id 4BE044CAB3E for ; Thu, 29 Jan 2004 16:49:45 -0500 (EST) Date: Thu, 29 Jan 2004 16:50:32 -0500 (Est) From: Joshua Slive To: users@httpd.apache.org In-Reply-To: <031a01c3e6b1$b70b8050$7764a8c0@ITDept> Message-ID: References: <031a01c3e6b1$b70b8050$7764a8c0@ITDept> X-X-Sender: slive@fastmail.fm@mail.messagingengine.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Subject: RE: [users@httpd] Facilitating File Downloads... X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Thu, 29 Jan 2004, Randy Grafton wrote: > The file is usually good for several weeks and then we'll get a call from a > customer complaining that their install didn't work after repeated > downloads. We'll go grab the file off of the server through ssh/sftp and > sure enough the file is bad. At this point we'll make a new copy on the > server and wait for the next customer to call. > Woh... You're saying the file is corrupted on the server? There is no way that apache is doing that. Apache will *never* write to a file that it is serving, unless you have some cgi/php/perl code that is doing that. Your problem very likely has absolutely nothing to do with the web server itself. Check your hardware/os config/etc. Joshua. --------------------------------------------------------------------- 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