From owner-freebsd-ports@FreeBSD.ORG Sat Nov 1 16:18:11 2008 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8AA6E1065675 for ; Sat, 1 Nov 2008 16:18:11 +0000 (UTC) (envelope-from ehaupt@FreeBSD.org) Received: from mx.critical.ch (152-39.3-213.fix.bluewin.ch [213.3.39.152]) by mx1.freebsd.org (Postfix) with ESMTP id 0F7C58FC17 for ; Sat, 1 Nov 2008 16:18:10 +0000 (UTC) (envelope-from ehaupt@FreeBSD.org) Received: from beaver (beaver.home.critical.ch [192.168.1.3]) by mx.critical.ch (8.14.3/8.14.3/critical-1.9) with SMTP id mA1G1wxi091235; Sat, 1 Nov 2008 17:01:59 +0100 (CET) (envelope-from ehaupt@FreeBSD.org) Date: Sat, 1 Nov 2008 17:01:57 +0100 From: Emanuel Haupt To: Greg Byshenk Message-Id: <20081101170157.98ff1eb8.ehaupt@FreeBSD.org> In-Reply-To: <20081031142351.GI907@core.byshenk.net> References: <20081031142351.GI907@core.byshenk.net> X-Mailer: Sylpheed 2.5.0 (GTK+ 2.10.14; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (mx.critical.ch [192.168.1.2]); Sat, 01 Nov 2008 17:01:59 +0100 (CET) X-Virus-Scanned: ClamAV 0.94/8552/Sat Nov 1 02:14:36 2008 on alaska.home.critical.ch X-Virus-Status: Clean Cc: freebsd-ports@FreeBSD.org Subject: Re: rsync with acls X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Nov 2008 16:18:11 -0000 On Fri, 31 Oct 2008 15:23:51 +0100 Greg Byshenk wrote: > I am experiencing a problem attempting to use rsync on systems with > extended ACLs enabled. > > The ACLs flag works, but when it is used, the mtime of the files on > on the receiving system are set to the current time. This is a bit > annoying in itself, but creates a larger problem because any later > rsync actions on the same files see the files as _different_, meaning > that _all_ the files are recopied -- which more or less defeats the > purpose of using rsync. > > Yes, I understand that setting ACLs on a file changes the mtime of the > file. But, as rsync is able to (re)set mtimes I would think that this > shouldn't should be an issue when using rsync. > > Is this a bug or a feature? Since ACL support isn't a default feature (ACL functionality is added by a custom patch) it seems to be a bug. Probably your best shot to get it fixed is following up a bug report at: http://rsync.samba.org/bugzilla.html Emanuel --