Am 2024-01-10 22:49, schrieb Mark Millard:
I never use atime, always noatime, for UFS. That said, I'd never
propose
changing the long standing defaults for commands and calls. I'd avoid:
[good points I fully agree on]
There's one possibility which nobody talked about yet... changing the
def
> On Jan 9, 2024, at 6:24 PM, void wrote:
>
> On Mon, Jan 08, 2024 at 01:07:30PM -0800, Enji Cooper wrote:
>>
>> Was the kernel/utility built with IPv6? If not, that’s a general bug which
>> should be filed (which can be easily checked/avoided using the FEATURES(9)
>> subsystem)…
>> Cheers!
hi list,
i'm having a recurring problem with poudriere that i hope someone might
have an idea about.
i'm building packages with poudriere on a system with 32GB memory, with
tmpfs and md disabled in poudriere (so it's using ZFS only) and with the
ZFS ARC limited to 8GB.
running poudriere produces
On Thu, Jan 11, 2024 at 1:50 AM Rodney W. Grimes wrote:
> > Olivier Certner wrote on
> > Date: Wed, 10 Jan 2024 10:01:48 UTC :
> > > What I'm saying is that, based on others' input so far, my own (long,
> > > even if not as long as yours) experience and some late reflection, is
> > > that "noatim
On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote:
> Please see/test: https://github.com/openzfs/zfs/pull/15732 .
Looks like that has landed in current:
commit f552d7adebb13e24f65276a6c4822bffeeac3993
Merge: 13720136fbf a382e21194c
Author: Martin Matuska
> Olivier Certner wrote on
> Date: Wed, 10 Jan 2024 10:01:48 UTC :
>
> > What I'm saying is that, based on others' input so far, my own (long, even
> > if not as long as yours) experience and some late reflection, is that
> > "noatime" should be the default (everywhere, all mounts and all FSes)
Olivier Certner wrote on
Date: Wed, 10 Jan 2024 10:01:48 UTC :
> What I'm saying is that, based on others' input so far, my own (long, even if
> not as long as yours) experience and some late reflection, is that "noatime"
> should be the default (everywhere, all mounts and all FSes), and that w
On Wed, Jan 10, 2024 at 12:44 PM Lyndon Nerenberg (VE7TFX/VE6BBM)
wrote:
>
> Olivier Certner writes:
>
> > I've never found any compelling reason in most uses to enable "atime",
> > except
> > perhaps local mail but as addressed in other answers it is a relic of the
> > pa
> > st mostly irrelev
> On Jan 9, 2024, at 7:17 AM, void wrote:
>
> On Tue, Jan 09, 2024 at 12:24:40PM +, void wrote:
>> On Tue, Jan 09, 2024 at 10:24:53AM +, void wrote:
>>> On Mon, Jan 08, 2024 at 01:07:30PM -0800, Enji Cooper wrote:
Was the kernel/utility built with IPv6? If not, that’s a genera
Olivier Certner writes:
> I've never found any compelling reason in most uses to enable "atime", except
> perhaps local mail but as addressed in other answers it is a relic of the pa
> st mostly irrelevant today. And its drawbacks are well known and can be seri
> ous.
When UNIX ran on PDP-11s a
On Wed, Jan 10, 2024 at 6:36 PM Olivier Certner 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 lo
Hallo
Olivier Certner wrote in
<2367131.USjQqFH40Q@ravel>:
|> I would not exactly call this a gimmick.
|
|I wish I hadn't used that term since it attracts too much attention \
|on itself, making people forget it was part of a sentence that was \
|quite balanced and seemingly altering their j
> > Again, I'm not opposing anyone from working on "relatime" if they
> > personally have a strong need and motivation. I'm not even asking for
> > removing the "atime" functionality, which can have its uses.
> >
>
> Yea, relatime has some interesting use cases: Is this binary / library in
> use
On Wed, Jan 10, 2024 at 3:01 AM Olivier Certner wrote:
> Hi Warner,
>
> > It has also been used for almost as long to see if log files have changed
> > if you set your MAIL variable to that. So not just for email...
>
> This seems to be an example in point of a "niche" scenario, both in terms
> o
> This is an interesting type of argument.
Except this is not an argument to the main discussion, as apparently you
haven't understood?
This kind of response is disingenuous. Either you said too much, or you didn't
say enough.
--
Olivier Certner
signature.asc
Description: This is a digitall
Van: Olivier Certner
Datum: woensdag, 10 januari 2024 11:01
Aan: Warner Losh
CC: freebsd-current@freebsd.org
Onderwerp: Re: noatime on ufs2
Hi Warner,
> It has also been used for almost as long to see if log files have changed
> if you set your MAIL variable to that. So not just for email...
On 1/9/24 22:09, Gleb Smirnoff wrote:
On Mon, Jan 08, 2024 at 10:40:52AM +0100, Jakob Alvermark wrote:
J> > > --- trap 0xc, rip = 0x...f80d97b78, rsp = 0x...
J> > > nl_send_one() at nl_send_one+0x18/frame 0xf
J> > > nl_send_group() at nl_send_group+0x1bc/frame 0xf.
Hi Warner,
> It has also been used for almost as long to see if log files have changed
> if you set your MAIL variable to that. So not just for email...
This seems to be an example in point of a "niche" scenario, both in terms of
spread of usage (even then) and the fact that it's easy to get the
Hi,
> I would not exactly call this a gimmick.
I wish I hadn't used that term since it attracts too much attention on itself,
making people forget it was part of a sentence that was quite balanced and
seemingly altering their judgement.
I think you're confusing the need and the mechanism (or i
19 matches
Mail list logo
