public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "bonhard@uklinux.net" <bonhard@uklinux.net>
To: cygwin@cygwin.com
Cc: fergus@bonhard.uklinux.net
Subject: find / without traversing /proc
Date: Thu, 27 Apr 2017 16:31:00 -0000	[thread overview]
Message-ID: <380-22017442784921354@M2W161.mail2web.com> (raw)

The command "find /" takes forever, if it completes at all, because of the
need to traverse the induced directory /proc. Is this directory often
needed by users? Can it be skipped by setting up "export CYGWIN=something",
or even by default, with the requirement on the user to induce it if needed?
There seems to be no switch to the command find that would easily allow
"but not this subdirectory": if there was, I wouldn't be asking. Quite a
lot of surfing led me to
$ find / \( -wholename /proc -o -wholename /dev \) -prune -o -print
which is really heavyweight syntax for a simple requirement. I am pretty
certain it leads to the behaviour required "do not traverse" though various
posters seem to think it just leads to "traverse but do not report" saving
almost nothing.
Assuming the syntax is correct, I have not been able to incorporate any
qualifiers such as -type d or -type f or -type l. Any ideas where to slot
these so that they work?


--------------------------------------------------------------------
mail2web - Check your email from the web at
https://link.mail2web.com/mail2web



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2017-04-27  8:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-27 16:31 bonhard [this message]
2017-04-27 17:16 ` Václav Haisman
2017-04-27 19:15   ` Andrew Schulman
2017-04-28 17:19   ` Andrey Repin
2017-04-28 18:38     ` Eliot Moss
2017-04-29  0:35     ` Eric Blake
2017-04-29 15:11       ` Andrey Repin
2017-04-30 21:37         ` Greywolf
2017-04-30 23:19           ` Greywolf
2017-04-28 10:05 ` Gary Johnson
2017-04-28 14:07   ` Brian Inglis
2017-04-28 13:09 Ugly Leper

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=380-22017442784921354@M2W161.mail2web.com \
    --to=bonhard@uklinux.net \
    --cc=cygwin@cygwin.com \
    --cc=fergus@bonhard.uklinux.net \
    /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).