From: Andrey Repin <anrdaemon@yandex.ru>
To: "Václav Haisman" <vhaisman@gmail.com>, cygwin@cygwin.com
Subject: Re: find / without traversing /proc
Date: Fri, 28 Apr 2017 17:19:00 -0000 [thread overview]
Message-ID: <1188853682.20170428041153@yandex.ru> (raw)
In-Reply-To: <CAKw7uVix05wZvX=in08fjvNWwZb_DUYmYbeTn5XXOBdedNd5DQ@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1613 bytes --]
Greetings, Václav Haisman!
> On 27 April 2017 at 10:49, wrote:
>> 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?
> Doesn't the -xdev switch help with this?
Just keep in mind that -xdev is an extension and different platform may use a
different way to indicate that find should stick to the current device.
--
With best regards,
Andrey Repin
Friday, April 28, 2017 04:10:57
Sorry for my terrible english...\x03BKCB\x1cØ\x19[H\x1c\^[Ü\x1cÎ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÜ\x1cØ\x19[\Ë\x1d^[[\x03BTN\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ\KÃB^[ØÝ[Y[\x18]\x1a[Û\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ^[ØÜË\x1d^[[\x03B[ÝXØÜXH\x1a[Î\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÛ[\vÈÝ[ÝXØÜXK\Ú[\^[\x19CBB
next prev parent reply other threads:[~2017-04-28 10:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 16:31 bonhard
2017-04-27 17:16 ` Václav Haisman
2017-04-27 19:15 ` Andrew Schulman
2017-04-28 17:19 ` Andrey Repin [this message]
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=1188853682.20170428041153@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=vhaisman@gmail.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).