Date: Thu, 11 Jan 2024 19:56:30 +0000 From: Jamie Landeg-Jones <jamie@catflap.org> To: olce@FreeBSD.org, imp@bsdimp.com Cc: freebsd-current@FreeBSD.org Subject: Re: noatime on ufs2 Message-ID: <202401111956.40BJuURB045685@donotpassgo.dyslexicfish.net> In-Reply-To: <2136329.mxFCRLsXLg@ravel> References: <ZZqmmM-6f606bLJx@int21h> <1749331.ETpRK2a2Mi@ravel> <CANCZdfo8VyhSJEUQpnvXuoPq0dzUHDN1sj-_y=1FTqXR3FrSuA@mail.gmail.com> <2136329.mxFCRLsXLg@ravel>
next in thread | previous in thread | raw e-mail | index | archive | help
Olivier Certner <olce@FreeBSD.org> wrote: > Both the examples above prompt some straight objections on the current usefulness of "atime". First, unless you've disabled building the locate database in cron (enabled by default, on a weekly basis), access times on directories lose most of their usefulness. Second, if using an IDS, I'm afraid it's just game over. And even if you think you are not, '460.pkg-checksum' at least is readily there to much complicate, or even prevent you from, getting package usage information this way (it is enabled by default, and on a daily basis). I've often wished there was the ability to set a process to "noatime" - where all accesses to the filesytem by the process and its children don't alter atime. It would be handy for those cases you describe above, such as backups and locate, but these days, where it matters, and is suitable, I instead create a filesystem snapshot, and run the process on that instead. (which is how "live" backups should be done anyway!) Cheers, Jamie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202401111956.40BJuURB045685>