Wojciech Puchar wrote:
what is a limit of amount of arguments passed to program? is it
hardwired or can be changed.
i found it to be in order of few thousands parameteres
searching google results in an article for linux
http://www.linuxjournal.com/article/6060
gives some ideas to work
what is a limit of amount of arguments passed to program? is it hardwired
or can be changed.
i found it to be in order of few thousands parameteres
___
freebsd-questions@freebsd.org mailing list
On Wednesday 27 February 2008 10:16:20 Erik Norgaard wrote:
Then a sysctl -a seems to indicate it is also a kernel
limitation on FreeBSD:
kern.argmax: 262144
I'm not certain that this is the limit of command line arguments, and I
haven't tried to set it. Nor is it clear to me if this is
On 2008-02-27 10:16, Erik Norgaard [EMAIL PROTECTED] wrote:
Wojciech Puchar wrote:
what is a limit of amount of arguments passed to program? is it
hardwired or can be changed.
i found it to be in order of few thousands parameteres
searching google results in an article for linux
one can easily write:
find . -name '*.ogg' | \
while read file ; do \
blah ${file}
done
xargs(1) is another popular tool for processing large argument lists:
find -name '*.ogg' | xargs blah
unless program blah starts slowly, and it's better to
On 2008-02-27 12:49, Wojciech Puchar [EMAIL PROTECTED] wrote:
one can easily write:
find . -name '*.ogg' | \
while read file ; do \
blah ${file}
done
xargs(1) is another popular tool for processing large argument lists:
find -name '*.ogg' | xargs blah
On Wed, 27 Feb 2008 13:15:51 +0200
Giorgos Keramidas [EMAIL PROTECTED] wrote:
It is worth noting, however, that there are usually fairly easy ways
to work with huge lists of command-line arguments. Instead of writing
things like this, for example:
for file in *.ogg ; do
On 2008-02-27 14:21, RW [EMAIL PROTECTED] wrote:
On Wed, 27 Feb 2008 13:15:51 +0200 Giorgos Keramidas wrote:
one can easily write:
find . -name '*.ogg' | \
while read file ; do \
blah ${file}
done
If blah is interactive, it will try to take its input from
In the last episode (Feb 27), Wojciech Puchar said:
one can easily write:
find . -name '*.ogg' | \
while read file ; do \
blah ${file}
done
xargs(1) is another popular tool for processing large argument lists:
find -name '*.ogg' | xargs blah
unless
2000 to do the rest.
That's less than xargs's default of 5000 :) The xargs manpage explains
it all.
with this defaults i've got argument list too long because every
argument is 70-80 bytes by average.
thanks for all help!
___
freebsd-questions
In the last episode (Feb 27), Wojciech Puchar said:
2000 to do the rest.
That's less than xargs's default of 5000 :) The xargs manpage explains
it all.
with this defaults i've got argument list too long because every argument
is 70-80 bytes by average.
Hm. That shouldn't happen, since
sorry i wrongly described what i've did. i should say that my total list
was about 5000 positions, and xargs -n 2000 solved this.
now i tested - xargs without -n works OK too.
thanks!
___
freebsd-questions@freebsd.org mailing list
:
find . -name 'sess.*' -delete
While that's good advice, it doesn't answer the question of argument list
too long.
Yes, it does.
The glob is expanded by find, the argument list too long problem occurs when
the glob is expanded by the shell.
The short answer is read ``man xargs
On Friday 27 January 2006 17:52, Paul Schmehl wrote:
for files in *.*
do
rm $files
done
Don't ever, *EVER* blindly unlink glob expansions. It's bad for you.
Instead, use something like:
find . -name 'sess.*' -delete
--
Kirk Strauser
pgpepCmOuaBna.pgp
Description: PGP signature
, it doesn't answer the question of argument list
too long.
The short answer is read ``man xargs''.
find . | xargs command
Bill
--
INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Systems, Inc.
URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way
FAX:(206) 232-9186
Hi,
I am getting error Argument list too long. when deleting files from
/tmp directory.
server20# uname -a
FreeBSD server20.hosthat.com 5.4-RELEASE FreeBSD 5.4-RELEASE #1: Tue
Oct 18 06:28:41 GMT 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SERVER20 i386
--On Saturday, January 28, 2006 05:04:00 +0530 FlashWebHost.com
[EMAIL PROTECTED] wrote:
Hi,
I am getting error Argument list too long. when deleting files from
/tmp directory.
server20# uname -a
FreeBSD server20.hosthat.com 5.4-RELEASE FreeBSD 5.4
On Friday 27 January 2006 23:34, FlashWebHost.com wrote:
Hi,
I am getting error Argument list too long. when deleting files from
/tmp directory.
server20# uname -a
FreeBSD server20.hosthat.com 5.4-RELEASE FreeBSD 5.4-RELEASE #1: Tue
Oct 18 06:28:41 GMT
I am getting error Argument list too long. when deleting files from
/tmp directory.
server20# pwd
/tmp
server20# ls -l sess*
/bin/ls: Argument list too long.
server20# rm -f sess*
/bin/rm: Argument list too long.
server20
On 2005-12-05 17:56, user [EMAIL PROTECTED] wrote:
Ok, so I have some big directories with lots of files. If I do mv or cp,
it always refuses, telling me:
cp: argument list too long
I very often find that I want to move around huge trees, including
mostly source code, but compiled object
On 2005-12-05 18:44, user [EMAIL PROTECTED] wrote:
On Mon, 5 Dec 2005, David Kelly wrote:
On Mon, Dec 05, 2005 at 05:56:22PM -0500, user wrote:
[...]
- since I live in 2005, what can I do to my FreeBSD system to upgrade
it to handle the directories I have ? How do I fix this so I can
Ok, so I have some big directories with lots of files. If I do mv or cp,
it always refuses, telling me:
cp: argument list too long
so, no problem ... I get creative with things like this:
for f in 0 1 2 3 4 5 6 7 8 9 A B C D E F G H I J K L M N O P Q R S T U V W
X Y Z ; do cp $f* /some/dir
On Mon, Dec 05, 2005, user wrote:
Ok, so I have some big directories with lots of files. If I do mv or cp,
it always refuses, telling me:
cp: argument list too long
so, no problem ... I get creative with things like this:
for f in 0 1 2 3 4 5 6 7 8 9 A B C D E F G H I J K L M N O P Q R S T U
On Mon, Dec 05, 2005 at 05:56:22PM -0500, user wrote:
[...]
- since I live in 2005, what can I do to my FreeBSD system to upgrade
it to handle the directories I have ? How do I fix this so I can do
normal, simple command lines instead of butchered ridiculous hacks
like above ?
Upgrade the
user wrote:
Ok, so I have some big directories with lots of files. If I do mv or cp,
it always refuses, telling me:
cp: argument list too long
so, no problem ... I get creative with things like this:
for f in 0 1 2 3 4 5 6 7 8 9 A B C D E F G H I J K L M N O P Q R S T U V W
X Y Z ; do cp $f
On Mon, 5 Dec 2005, David Kelly wrote:
On Mon, Dec 05, 2005 at 05:56:22PM -0500, user wrote:
[...]
- since I live in 2005, what can I do to my FreeBSD system to upgrade
it to handle the directories I have ? How do I fix this so I can do
normal, simple command lines instead of butchered
user wrote:
...
What I want to know is, how can I just use cp ? You are suggesting above
that the limitation is part of the users environment, and that I should
upgrade the user. I dn't know what you mean by that. I am root. How do
I upgrade the user(s environment ?)
thanks.
Go back
The sysctl kern.argmax reflects the maximum argument list size. It's
set to 65536, at least in 4.11, and is (I think) not changeable except
by rebuilding the kernel with a different value for ARG_MAX.
Is well and good that there be some limit to how much data one can pack
on the command line
2005/12/6, Richard Tobin [EMAIL PROTECTED]:
The sysctl kern.argmax reflects the maximum argument list size. It's
set to 65536, at least in 4.11,
just for info:
kern.argmax: 262144
on FreeBSD 6.0-STABLE
--
Pietro Cerutti
[EMAIL PROTECTED]
Beansidhe - SwiSS Death / Thrash Metal
On Fri, 19 Nov 2004, Dennis Koegel wrote:
find /foo/bar -type f -maxdepth 1 | xargs rm -n100
Although xargs is the most versatile solution for when having too many
items listed, for just deleting find itself can do it..
find /foo/bar -n mask -delete
___
Hi,
I tried to delete all files from a dir, however I got this message:
/bin/rm: Argument list too long.
So, no go. newfs is also no option, because the dir is not a seperate fs.
Any hints exept for manual labour?
Bye,
Mipam.
___
[EMAIL PROTECTED
On Fri, Nov 19, 2004 at 09:58:40AM +0100, Mipam wrote:
I tried to delete all files from a dir, however I got this message:
/bin/rm: Argument list too long.
You probably did rm *, and * expanded to too many files.
One way is to simply remove the directory completely (rm -r /foo/bar
Mipam wrote:
Hi,
I tried to delete all files from a dir, however I got this message:
/bin/rm: Argument list too long.
So, no go. newfs is also no option, because the dir is not a seperate fs.
Any hints exept for manual labour?
Bye,
Mipam.
I gather it's rm * that's not working?
If so, try
On Fri, Nov 19, 2004 at 10:19:39AM +0100, Dennis Koegel typed:
snip
find /foo/bar -type f -maxdepth 1 | xargs rm -n100
or just
ls | xargs rm
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To
On Tue, 24 Dec 2002, Bill Moran wrote:
other way of overcoming this limit?
find . -name *.html | xargs grep someting
Dw
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
At 2002-12-25T14:02:07Z, Bill Moran [EMAIL PROTECTED] writes:
Ahhh ... so (making sure to understand this information so I can use it
again later) the quotes tell find to expand the pattern, without quotes
the shell tries to do it and results in the mentioned error.
That's exactly correct.
on some features that
the www.php.net's search isn't really helping on (searching
for __FILE__ doesn't search for __FILE__ ... it searches for
file, and there's too many results) so I try:
grep __FILE__ *.html
and I get the error:
-bash: /usr/bin/grep: Argument list too long
*.html
| and I get the error:
| - -bash: /usr/bin/grep: Argument list too long
| Is this a shortcoming of bash, grep or FreeBSD? I'm assuming
| it's not grep, as the command:
| find . -name *.html -print | xargs grep __FILE__
| yeilds:
| - -bash: /usr/bin/find: Argument list too long
try this one
many results) so I try:
| grep __FILE__ *.html
| and I get the error:
| - -bash: /usr/bin/grep: Argument list too long
| Is this a shortcoming of bash, grep or FreeBSD? I'm assuming
| it's not grep, as the command:
| find . -name *.html -print | xargs grep __FILE__
| yeilds:
| - -bash: /usr/bin
in message [EMAIL PROTECTED],
wrote Bill Moran thusly...
From: Shantanu Mahajan [EMAIL PROTECTED]
the wildcard, thus the limit doesn't affect the command.
or maybe you can use locate
Hadn't thought to try that, although I don't know how it would
work.
RTFM? locate(1)?
given a path
From: [EMAIL PROTECTED] (Gary W. Swearingen)
find . -name '*.html' -print | xargs grep __FILE__
One might as well get in the habit of using the more robust
find . -name '*.html' -print0 | xargs -0 grep __FILE__
Otherwise, the -print isn't needed at all; it's a default.
Very true.
for __FILE__ ... it searches for
file, and there's too many results) so I try:
grep __FILE__ *.html
and I get the error:
-bash: /usr/bin/grep: Argument list too long
Is this a shortcoming of bash, grep or FreeBSD? I'm assuming
it's not grep, as the command:
find . -name *.html -print | xargs grep __FILE__
doesn't search for __FILE__ ... it searches for
file, and there's too many results) so I try:
grep __FILE__ *.html
and I get the error:
-bash: /usr/bin/grep: Argument list too long
Is this a shortcoming of bash, grep or FreeBSD? I'm assuming
it's not grep, as the command:
find . -name *.html -print
helping on (searching
for __FILE__ doesn't search for __FILE__ ... it searches for
file, and there's too many results) so I try:
grep __FILE__ *.html
and I get the error:
-bash: /usr/bin/grep: Argument list too long
Is this a shortcoming of bash, grep or FreeBSD? I'm assuming
it's not grep
the docs on some features that
the www.php.net's search isn't really helping on (searching
for __FILE__ doesn't search for __FILE__ ... it searches for
file, and there's too many results) so I try:
grep __FILE__ *.html
and I get the error:
-bash: /usr/bin/grep: Argument list too long
isn't really helping on (searching
for __FILE__ doesn't search for __FILE__ ... it searches for
file, and there's too many results) so I try:
grep __FILE__ *.html
and I get the error:
-bash: /usr/bin/grep: Argument list too long
Is this a shortcoming of bash, grep or FreeBSD? I'm assuming
the docs on some features that
the www.php.net's search isn't really helping on (searching
for __FILE__ doesn't search for __FILE__ ... it searches for
file, and there's too many results) so I try:
grep __FILE__ *.html
and I get the error:
-bash: /usr/bin/grep: Argument list too long
On Tue, Dec 24, 2002 at 05:25:23PM -0500, Bill Moran wrote:
[...]
Is this a shortcoming of bash, grep or FreeBSD? I'm assuming
it's not grep, as the command:
find . -name *.html -print | xargs grep __FILE__
yeilds:
-bash: /usr/bin/find: Argument list too long
If you quote the *.html, ie
48 matches
Mail list logo
