public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin-apps@cygwin.com
Subject: Re: chattr makes cygport slow
Date: Thu, 06 Jul 2023 13:36:03 -0400	[thread overview]
Message-ID: <6oudaidfkn4d7fnharmh7u3f3ionrcrgl0@4ax.com> (raw)
In-Reply-To: <3gbdai9h69p2c67lv8g7f873hje9skmglq@4ax.com>

> Recently I noticed that `cygport finish` has become really slow on some of my
> package source trees. After I run for example
> 
> cygport libargp.cygport finish
> 
> it waits for about 5 minutes without any message to the console, before the
> first "Removing work directory" message appears.
> 
> pstree shows that during this time cygport is waiting for chattr. In
> /usr/bin/cygport I see:
> 
> if [ $OSTYPE = "cygwin" ]
> then
>     chattr -fR +C ${workdir} >/dev/null 2>&1 || true
> fi
> 
> which is trying to make the workdir case-sensitive.
> 
> Whatever the advantages of that are, it can take a long time. Would it be
> possible to skip it at least in the case of "finish"? It seems silly to spend
> all that time fixing up a directory tree that we then turn around and remove
> with rm -rf.

And/or, maybe add a switch to suppress it. I've commented it out of my
/usr/bin/cygport for now, because it makes me wait an extra 5 minutes before
every cygport command, at least on this particular source tree with 12K files in
it.


  parent reply	other threads:[~2023-07-06 17:36 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 [this message]
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
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=6oudaidfkn4d7fnharmh7u3f3ionrcrgl0@4ax.com \
    --to=schulman.andrew@epa.gov \
    --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).