From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] dcp - a deep copy script, better than dircp
Date: Mon, 20 Jul 2009 18:56:10 -0400 [thread overview]
Message-ID: <32fef51363b393733cc054e6d31d733f@quanstro.net> (raw)
In-Reply-To: <6e35c0620907201551l8277782s935944532a8b4e67@mail.gmail.com>
minooka; time rc -c 'du -a . | wc'
> On Mon, Jul 20, 2009 at 2:41 PM, erik quanstrom<quanstro@quanstro.net> wrote:
> > on coraid's worm, a find on main takes not too long:
> >
> > minooka; cd /n/ila
> > minooka; time rc -c 'find . | wc'
> > 356164 356164 13987863
> > 1.24u 1.38s 6.65r rc -c find . | wc
>
> The FAQ also mentions:
>
> du -a . | grep foo
>
> Just out of curiosity, how does find vs du compare for you?
i know you can do it with du, but it seems a bit "cat -n"ish to me.
for comparison:
minooka; time rc -c 'du -a . | wc'
356181 712362 14825492
1.91u 4.22s 8.66r rc -c du -a . | wc
- erik
next prev parent reply other threads:[~2009-07-20 22:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-19 16:24 Ethan Grammatikidis
2009-07-19 18:05 ` erik quanstrom
2009-07-19 18:16 ` Richard Miller
2009-07-19 18:34 ` Francisco J Ballesteros
2009-07-20 1:32 ` Ethan Grammatikidis
2009-07-20 9:55 ` Charles Forsyth
2009-07-20 11:36 ` Ethan Grammatikidis
2009-07-20 11:50 ` erik quanstrom
2009-07-20 13:25 ` Ethan Grammatikidis
2009-07-20 14:00 ` Steve Simon
2009-07-20 15:02 ` Ethan Grammatikidis
2009-07-20 15:13 ` erik quanstrom
2009-07-20 15:19 ` Dan Cross
2009-07-20 18:30 ` Ethan Grammatikidis
2009-07-20 22:25 ` Jason Catena
2009-07-20 22:41 ` erik quanstrom
2009-07-20 22:51 ` Jack Johnson
2009-07-20 22:56 ` erik quanstrom [this message]
2009-07-21 0:31 ` Dan Cross
2009-07-23 2:10 ` Federico G. Benavento
2009-07-20 9:32 ` cej
2009-07-20 11:04 ` Ethan Grammatikidis
2014-04-17 12:53 ` arisawa
2014-04-17 12:55 ` erik quanstrom
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=32fef51363b393733cc054e6d31d733f@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.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 NNTP newsgroup(s).