From owner-freebsd-ports-bugs@freebsd.org Fri Jan 6 13:17:39 2017 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 14839CA2EDB for ; Fri, 6 Jan 2017 13:17:39 +0000 (UTC) (envelope-from hostmaster@GTS.net) Received: from smtp.gts.net (whois.gts.net [199.246.111.182]) by mx1.freebsd.org (Postfix) with ESMTP id D5DEE158C; Fri, 6 Jan 2017 13:17:37 +0000 (UTC) (envelope-from hostmaster@GTS.net) Received: (using Smail-3.2.0.122-Pre 2005-Nov-17 #10 built 2013-Jun-8) from fandango.local.gts.net ([10.138.66.7:41637]) by fukspam.gts.net ([199.246.111.181:25]) via TCP with esmtp (/origin:R/R:inet_hosts/T:smtp/dest:R) id (sender ) for (body size 576, total 1564 bytes); Fri, 6 Jan 2017 08:17:31 -0500 (EST) Received: by fandango.local.gts.net (Postfix, from userid 12) id B45CD6DEDD; Fri, 6 Jan 2017 08:17:29 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by fandango.local.gts.net (Postfix) with ESMTP id A7C206DEDC; Fri, 6 Jan 2017 08:17:29 -0500 (EST) Date: Fri, 6 Jan 2017 08:17:29 -0500 (EST) From: hotlips Internet admin X-X-Sender: hostmaster@fandango.local.gts.net To: freebsd-ports-bugs@freebsd.org cc: ehaupt@freebsd.org Subject: Re: [Bug 215688] net/rsync fileflags & forcechange don't work for hardlinks Message-ID: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2017 13:17:39 -0000 It turns out that the /usr/bin/ hard link example given does not apply to FreeBSD 11 because the hard links have been changed to soft links in that release. However the underlying issue remains that rsync does not correctly handle the combination of hard links and immutable (schg flag) files, in exactly the same manner as in previous releases (I've tested 6.4, 8.2, 9.3, 10.1) So, should I close this bug report and start a new one? Suggestions and comments please ... Bruce Becker +1 416 410 0879 GTS Network Administration Toronto, Ont. Email: hostmaster@GTS.net