From: "David Gómez" <david@pleyades.net>
To: Dan Nelson <dnelson@allantgroup.com>
Cc: Zsh-workers <zsh-workers@sunsite.dk>
Subject: Re: Argument list
Date: Tue, 1 Oct 2002 23:07:42 +0200 [thread overview]
Message-ID: <20021001210742.GA13924@fargo> (raw)
In-Reply-To: <20021001202002.GG7147@dan.emsphone.com>
> > I created a directory with 100000 files to test the new htree patch
> > for the ext3 filesystem, and found a ¿bug? when I tried to remove all
> > the files. The command 'rm *' gave the error 'zsh: argument list too
> > long'. If expansion doesn't support so many parameters, what it's the
> > supossed way to remove all these files without deleting the
> > directory?
>
> You sure the error wasn't 'zsh: argument list too long: rm' ?
You're right, that was the full error line. I didn't put the rm because
i thought it wasn't important, my fault.
> internal shell wildcard expansion has no argument limit. execve()
> does. Either raise your kernel's limit (sorry; don't know how to do it
> on Linux),
I've been trying to raise some limits, but none of them affect the number of
parameters execve() supports, maybe is possible to change it in linux through
some /proc variable, or a kernel recompilation is needed.
I just wanted to know if this was a zsh related problem, now i'll look forward
to know how to change execve limits.
Thanks to all the replies ;),
--
David Gómez
"The question of whether computers can think is just like the question of
whether submarines can swim." -- Edsger W. Dijkstra
next prev parent reply other threads:[~2002-10-01 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 19:54 David Gómez
2002-10-01 20:14 ` Jason Price
2002-10-01 20:20 ` Dan Nelson
2002-10-01 21:07 ` David Gómez [this message]
2002-10-02 8:08 ` Thomas Köhler
2002-10-02 9:40 ` David Gómez
2002-10-01 20:26 ` DervishD
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=20021001210742.GA13924@fargo \
--to=david@pleyades.net \
--cc=dnelson@allantgroup.com \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).