From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Adam Voigt <adam@cryptocomm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File Limit in Kernel?
Date: Tue, 12 Nov 2002 11:06:44 -0500 [thread overview]
Message-ID: <3DD12714.30300@nortelnetworks.com> (raw)
In-Reply-To: 1037115535.1439.5.camel@beowulf.cryptocomm.com
Adam Voigt wrote:
> I have a directory with 39,000 files in it, and I'm trying to use the cp
> command to copy them into another directory, and neither the cp or the
> mv command will work, they both same "argument list too long" when I
> use:
>
> cp -f * /usr/local/www/images
>
> or
>
> mv -f * /usr/local/www/images
>
> Is this a kernel limitation?
It's not a kernel limitiation, its a shell limitation. "*" expands to
the list of 39000 names, which is too large.
You could try something like:
ls .|xargs cp -f --target-directory=/usr/local/www/images
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2002-11-12 16:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 15:38 File Limit in Kernel? Adam Voigt
2002-11-12 15:57 ` Andreas Gruenbacher
2002-11-13 9:51 ` Jan Hudec
2002-11-13 10:49 ` Andreas Schwab
2002-11-12 16:01 ` Kent Borg
2002-11-12 16:26 ` Mark Mielke
2002-11-12 16:06 ` Chris Friesen [this message]
2002-11-12 16:08 ` Richard B. Johnson
2002-11-12 16:12 ` Matt Reppert
2002-11-12 16:16 ` Bernd Eckenfels
2002-11-12 23:23 ` Bill Davidsen
[not found] <1037115535.1439.5.camel@beowulf.cryptocomm.com.suse.lists.linux.kernel>
2002-11-12 15:53 ` Andi Kleen
2002-11-12 21:54 ` Pavel Machek
2002-11-19 15:14 ` Shalon Wood
2002-11-19 19:44 ` Pavel Machek
2002-11-12 21:55 ` Jamie Lokier
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=3DD12714.30300@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=adam@cryptocomm.com \
--cc=linux-kernel@vger.kernel.org \
/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