Date: Tue, 25 Jan 2022 03:51:16 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 261434] [sysutils/fusefs-sshfs] updating a file's atime causes its mtime to change too Message-ID: <bug-261434-227-Es4aXNPxv4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261434-227@https.bugs.freebsd.org/bugzilla/> References: <bug-261434-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261434 Alan Somers <asomers@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Works As Intended --- Comment #17 from Alan Somers <asomers@FreeBSD.org> --- Please do not reopen the bug. > #ifdef HAVE_UTIMENSAT - "new code" block, added in 2012, before it 4 year= s work > only code that requires both times together. So what? You aren't using a 2012 build of sshfs, I hope. > This change nothing. It changes everything. Without "-o strictatime", Linux does "relatime", wh= ich basically means that it only updates atime once every 24 hours. You MUST u= se "-o nostrictatime" to see the POSIX-compliant atime behavior. > Do you test all fusefs consumers to ensure that updating only atime work = correctly? All? Of course not. But I have tested several, and they all work fine. Please do not reopen the bug. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-261434-227-Es4aXNPxv4>