Return-Path: Delivered-To: apmail-mirrors-archive@apache.org Received: (qmail 37560 invoked by uid 500); 6 Apr 2000 09:26:29 -0000 Mailing-List: contact mirrors-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: mirrors@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list mirrors@apache.org Received: (qmail 37514 invoked from network); 6 Apr 2000 09:26:23 -0000 Date: Thu, 6 Apr 2000 12:26:18 +0300 From: Costas Tavernarakis To: mirrors@apache.org Subject: Re: error during rsync - web page Message-ID: <20000406122618.A16307@noc.otenet.gr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from shepard@ameth.org on Tue, Apr 04, 2000 at 05:08:52PM -0500 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Tue, Apr 04, 2000 at 05:08:52PM -0500, Chase Phillips wrote: > rsync's man page states that -a breaks down into -rlptg, which can be > unsafe without some additional flags. unsafe of course only if the > sender's machine has been compromised. Without knowing rsync's default > behaviour, I do endorse changing the recommended flags to allow for > symlinks; perhaps to: > > rsync -rtvzl --delete --safe-links --exclude incoming \ > dev.apache.org::apache-site /local/path/to/mirror > Well, the -p part of the -a expansion, is at least unnecessary for most sites, and having a smaller command line is not a good enough reason to promote its use IMHO. Otherwise, the command line for most sites should most propably be rsync -rtvzlHS --delete --safe-links --exclude /incoming \ dev.apache.org::apache-site/ /local/path/to/mirror The -S is "no-harm" and may prove useful in a "just in case" way, if a "core" file gets dropped somewhere in the tree. The -H would help preserve hard links if they exist. In the long run, the site could change the few soft links it has to hard ones. That way, mirror sites could have some improved security, since they wouldn't need the "SymLinksIfOwnerMatch" Option in the Directory section of httpd.conf. I wonder, though, if -z does anything more than increase the CPU utilization on both the sending and the receiving sides.. > > receiving file list ... opendir(bugs/shadow): Permission denied > > done > > IO error encountered - skipping file deletion > > > > Note the 'IO error - skipping file deletion'. > > > > referring to rsync's man page, i see that once an IO error is encountered > on the sending side, deletion is turned off at the receiving side for the > rest of that session. is there a problem at dev.apache.org with a part of > the filesystem? if not, of what is this symptomatic? The I/O error IS the "permission denied" error on bugs/shadow . I've had to exclude this path to get my mirror working right. Costas Tavernarakis apache.otenet.gr admin