public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: chattr makes cygport slow
Date: Sun, 16 Jul 2023 21:32:44 +0200	[thread overview]
Message-ID: <87leffr6sj.fsf@Rainer.invalid> (raw)
In-Reply-To: <0eb00e42-372f-3aa7-d161-c2e62a1e9d91@dronecode.org.uk> (Jon Turney via Cygwin-apps's message of "Sun, 16 Jul 2023 17:15:27 +0100")

Jon Turney via Cygwin-apps writes:
> The warning (error if RESTRICT=case_insensitive) should occur for all
> commands, not just prep.

OK.

> How about the attached.

Looks promising.

> Even then, it should only be modifying every directory, not every file.

Run strace on "chattr -r +C ." and see that it isn't that smart…

Anyway, since it won't succeed on anything but empty directories it
doesn't make sense to use to attempt a recursive change even if it were
just looking at directories (which would of course be way faster at
least).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

  reply	other threads:[~2023-07-16 19:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 12:19 Andrew Schulman
2023-07-06 16:18 ` Brian Inglis
2023-07-08 12:19   ` Jon Turney
2023-07-06 17:36 ` Andrew Schulman
2023-07-08 12:16   ` Jon Turney
2023-07-08 13:23     ` Andrew Schulman
2023-07-08 14:22     ` ASSI
2023-07-16 16:15       ` Jon Turney
2023-07-16 19:32         ` ASSI [this message]
2023-07-23 15:33           ` Jon Turney
2023-07-23 19:13             ` ASSI
2023-07-24 21:07               ` Jon Turney
2023-07-28 11:35             ` Andrew Schulman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87leffr6sj.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).