From nobody Sun Jan 14 17:23:51 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TChvh5ptwz56jSs for ; Sun, 14 Jan 2024 17:24:00 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [208.79.93.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4TChvh1nnlz4VhW; Sun, 14 Jan 2024 17:24:00 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Authentication-Results: mx1.freebsd.org; none Received: from orthanc.ca (localhost [127.0.0.1]) by orthanc.ca (OpenSMTPD) with ESMTP id 013b4107; Sun, 14 Jan 2024 09:23:51 -0800 (PST) From: "Lyndon Nerenberg (VE7TFX/VE6BBM)" To: Olivier Certner cc: Rick Macklem , freebsd-current@freebsd.org Subject: Re: noatime on ufs2 In-reply-to: <4014880.cjyAsbXg9l@ravel> References: <4014880.cjyAsbXg9l@ravel> Comments: In-reply-to Olivier Certner message dated "Sun, 14 Jan 2024 17:38:52 +0100." List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <21092.1705253031.1@orthanc.ca> Date: Sun, 14 Jan 2024 09:23:51 -0800 Message-ID: X-Rspamd-Queue-Id: 4TChvh1nnlz4VhW X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_RCPT(0.00)[]; ASN(0.00)[asn:25795, ipnet:208.79.88.0/21, country:US] > > I do not have a strong opinion w.r.t. atime, but I do believe that > > changing the default would be a POLA violation. I'm not prepared to just accept that at face value. I can't think of a single instance in at least the last three decades where I have actually used or needed atime for *anything*. And over that time period I have been responsible for running hundreds of UNIX servers. I'm really interested in hearing from people who actively use atime on a regular basis for non-trivial purposes. What are the modern use cases for atime? --lyndon