On Fri, Oct 24, 2008 at 5:07 PM, Lanny Marcus <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 24, 2008 at 5:21 PM, Phil Schaffner <[EMAIL PROTECTED]> wrote:
>> On Fri, 2008-10-24 at 14:19 -0400, Ed Westphal wrote:
>>> Forgive my senility, but I'm continually amazed how many of us ole
>>> fossils are still
On Fri, Oct 24, 2008 at 5:21 PM, Phil Schaffner <[EMAIL PROTECTED]> wrote:
> On Fri, 2008-10-24 at 14:19 -0400, Ed Westphal wrote:
>> Forgive my senility, but I'm continually amazed how many of us ole
>> fossils are still around, and running Linux! Not to use up too much
>> bandwidth, but the switc
On Fri, 2008-10-24 at 14:19 -0400, Ed Westphal wrote:
> Forgive my senility, but I'm continually amazed how many of us ole
> fossils are still around, and running Linux! Not to use up too much
> bandwidth, but the switch from Fortran 2 to 2D, for disk, was a big
> event way back when. Then Fortr
MHR wrote:
On Fri, Oct 24, 2008 at 9:31 AM, Bill Campbell <[EMAIL PROTECTED]> wrote:
Programming to the lowest common denominator may not feel sexy,
but it can prevent many headaches in the future. I spent quite a
bit of time many years ago getting a large FORTRAN system working
that had bee
On Fri, Oct 24, 2008 at 9:31 AM, Bill Campbell <[EMAIL PROTECTED]> wrote:
>
>
> Programming to the lowest common denominator may not feel sexy,
> but it can prevent many headaches in the future. I spent quite a
> bit of time many years ago getting a large FORTRAN system working
> that had been wri
Bill Campbell wrote:
There are two possible buffer limits one could encounter: tty driver
input line buffer (which is not an issue for bash because readline
avoids it) and kernel exec space for the arguments plus environment
passed to a new process. Only the second one causes the error message
On Fri, Oct 24, 2008, Bart Schaefer wrote:
>On Fri, Oct 24, 2008 at 8:48 AM, fred smith
><[EMAIL PROTECTED]> wrote:
>> I've always understood it to be an issue with commandline length: somewhere
>> (probably in bash) there's a limit on how big a buffer is/can be used for
>> storing the comamndline.
On Fri, Oct 24, 2008 at 8:48 AM, fred smith
<[EMAIL PROTECTED]> wrote:
> I've always understood it to be an issue with commandline length: somewhere
> (probably in bash) there's a limit on how big a buffer is/can be used for
> storing the comamndline.
There are two possible buffer limits one could
On Fri, Oct 24, 2008 at 06:49:02AM -0500, Johnny Hughes wrote:
> Jussi Hirvi wrote:
>
> >> piping ls to xargs should do the trick. man xargs for details.
> >
> > Ok, thanks for ideas, Laurent and Lawrence.
> >
> > A strange limitation in ls and rm, though. My friend said he hasn't seen
> > that
Jussi Hirvi wrote:
>> piping ls to xargs should do the trick. man xargs for details.
>
> Ok, thanks for ideas, Laurent and Lawrence.
>
> A strange limitation in ls and rm, though. My friend said he hasn't seen
> that in Fedora.
This issue is in Fedora, Ubuntu, CentOS, RHEL, (put any other linu
> and get only "argument list too long" as feedback.
>
> Is there a way to go round this problem?
>
> I have CentOS 5.2.
>
I'm not going to repeat some of the good advice given to you by others
as to how to avoid this error, but will instead tell you this is related
to the ARG_MAX variable.
The
On Oct 18, 2008, at 8:13 PM, mouss wrote:
Jussi Hirvi a écrit :
Since when is there a limit in how long directory listings CentOS
can show
(ls), or how large directories can be removed (rm). It is really
annoying to
say, for example
rm -rf /var/amavis/tmp
and get only "argument list t
Jussi Hirvi a écrit :
> Since when is there a limit in how long directory listings CentOS can show
> (ls), or how large directories can be removed (rm). It is really annoying to
> say, for example
>
> rm -rf /var/amavis/tmp
>
> and get only "argument list too long" as feedback.
I doubt this
On Oct 17, 2008, at 7:58 PM, thad wrote:
Satchel Paige - "Don't look back. Something might be gaining on you."
On Fri, Oct 17, 2008 at 4:36 AM, Laurent Wandrebeck
<[EMAIL PROTECTED]> wrote:
2008/10/17 Jussi Hirvi <[EMAIL PROTECTED]>:
Since when is there a limit in how long directory listing
thad wrote:
Satchel Paige - "Don't look back. Something might be gaining on you."
On Fri, Oct 17, 2008 at 4:36 AM, Laurent Wandrebeck
<[EMAIL PROTECTED]> wrote:
2008/10/17 Jussi Hirvi <[EMAIL PROTECTED]>:
Since when is there a limit in how long directory listings CentOS can show
(ls), or how
Satchel Paige - "Don't look back. Something might be gaining on you."
On Fri, Oct 17, 2008 at 4:36 AM, Laurent Wandrebeck
<[EMAIL PROTECTED]> wrote:
> 2008/10/17 Jussi Hirvi <[EMAIL PROTECTED]>:
>> Since when is there a limit in how long directory listings CentOS can show
>> (ls), or how large d
Yes, you are right - my example was misleading.
Thanks for the very easy solution (cd into directory). Have to try it the
next time.
- Jussi
Paul Bijnens ([EMAIL PROTECTED]) kirjoitteli (17.10.2008 13:18):
> I believe you gave a bad example!
> In the command
>
> rm -rf /var/amavis/tmp
>
> the
Jussi Hirvi wrote:
> Lawrence Guirre ([EMAIL PROTECTED]) kirjoitteli (17.10.2008 12:55):
> > piping ls to xargs should do the trick. man xargs for details.
>
> Ok, thanks for ideas, Laurent and Lawrence.
>
> A strange limitation in ls and rm, though. My friend said he hasn't seen
> that in Fedora
>> piping ls to xargs should do the trick. man xargs for details.
>Ok, thanks for ideas, Laurent and Lawrence.
>A strange limitation in ls and rm, though. My friend said he hasn't seen
>that in Fedora.
Are you sure you are comparing apples to apples? There is nothing
particularly Centos speci
Lawrence Guirre ([EMAIL PROTECTED]) kirjoitteli (17.10.2008 12:55):
> piping ls to xargs should do the trick. man xargs for details.
Ok, thanks for ideas, Laurent and Lawrence.
A strange limitation in ls and rm, though. My friend said he hasn't seen
that in Fedora.
- Jussi
--
Jussi Hirvi * Gre
On 2008-10-17 11:30, Jussi Hirvi wrote:
Since when is there a limit in how long directory listings CentOS can show
(ls), or how large directories can be removed (rm). It is really annoying to
say, for example
rm -rf /var/amavis/tmp
and get only "argument list too long" as feedback.
Is ther
piping ls to xargs should do the trick. man xargs for details.
Jussi Hirvi wrote:
Since when is there a limit in how long directory listings CentOS can show
(ls), or how large directories can be removed (rm). It is really annoying to
say, for example
rm -rf /var/amavis/tmp
and get only "ar
2008/10/17 Jussi Hirvi <[EMAIL PROTECTED]>:
> Since when is there a limit in how long directory listings CentOS can show
> (ls), or how large directories can be removed (rm). It is really annoying to
> say, for example
>
>rm -rf /var/amavis/tmp
>
> and get only "argument list too long" as feedb
23 matches
Mail list logo
