From owner-svn-src-all@FreeBSD.ORG Fri Feb 10 17:20:26 2012 Return-Path: Delivered-To: svn-src-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D216106564A; Fri, 10 Feb 2012 17:20:26 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail07.syd.optusnet.com.au (mail07.syd.optusnet.com.au [211.29.132.188]) by mx1.freebsd.org (Postfix) with ESMTP id CA9C18FC12; Fri, 10 Feb 2012 17:20:25 +0000 (UTC) Received: from c211-30-171-136.carlnfd1.nsw.optusnet.com.au (c211-30-171-136.carlnfd1.nsw.optusnet.com.au [211.30.171.136]) by mail07.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id q1AHKM5x016407 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 11 Feb 2012 04:20:24 +1100 Date: Sat, 11 Feb 2012 04:20:22 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Sergey Kandaurov In-Reply-To: Message-ID: <20120211041345.Q3573@besplex.bde.org> References: <201202101340.q1ADeWDj076596@svn.freebsd.org> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-267995700-1328894422=:3573" Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, Ed Schouten Subject: Re: svn commit: r231383 - in head: lib/libutil usr.sbin/vipw X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2012 17:20:26 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-267995700-1328894422=:3573 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Fri, 10 Feb 2012, Sergey Kandaurov wrote: > On 10 February 2012 17:40, Ed Schouten wrote: >> Log: >> =A0Detect file modification properly by using tv_nsec. >> >> =A0POSIX 2008 standardizes st_mtim, meaning we can simply use nanosecond >> =A0precision to detect file modification. > > I am not sure we can use subsecond precision there with currently set > sysctl vfs.timestamp_precision=3D0. Also, not all file systems support even seconds precision. So the deleted BUGS section applies irrespective of vfs.timestamp_precision, except it doesn't describe the full extent of the problem. Sleeping for just 1 second is not enough if the timestamp precision is large. The BUGS section also applies respective of vfs.timestamp_precision, when the user uses the supported setting vfs.timestamp_precision=3D0. Of course, important databases that need POSIX semantics shouldn't be put on file systems without POSIX times, but you need a BUGS section somewhere to tell you not to do that. Bruce --0-267995700-1328894422=:3573--