From owner-freebsd-ports@FreeBSD.ORG Fri Oct 31 15:41:30 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 DF30C106567D for ; Fri, 31 Oct 2008 15:41:30 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (core.byshenk.net [62.58.73.230]) by mx1.freebsd.org (Postfix) with ESMTP id 749A78FC1E for ; Fri, 31 Oct 2008 15:41:30 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (localhost.aoes.com [127.0.0.1]) by core.byshenk.net (8.14.3/8.14.3) with ESMTP id m9VFJruA028293 for ; Fri, 31 Oct 2008 16:19:53 +0100 (CET) (envelope-from byshenknet@core.byshenk.net) Received: (from byshenknet@localhost) by core.byshenk.net (8.14.3/8.14.3/Submit) id m9VFJr6P028292 for freebsd-ports@freebsd.org; Fri, 31 Oct 2008 16:19:53 +0100 (CET) (envelope-from byshenknet) Resent-Message-Id: <200810311519.m9VFJr6P028292@core.byshenk.net> Date: Fri, 31 Oct 2008 15:23:51 +0100 From: Greg Byshenk To: freebsd-ports@freebsd.org Message-ID: <20081031142351.GI907@core.byshenk.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Resent-From: byshenknet@byshenk.net Resent-Date: Fri, 31 Oct 2008 16:19:53 +0100 Resent-To: freebsd-ports@freebsd.org X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on core.byshenk.net Subject: 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: Fri, 31 Oct 2008 15:41:31 -0000 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? -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL