* RE: Protocol error: too many arguments
[not found] <16747.55189.754030.610553@cuddles.cambridge.redhat.com>
@ 2004-10-12 13:17 ` Dave Korn
2004-10-12 13:21 ` Andrew Haley
0 siblings, 1 reply; 10+ messages in thread
From: Dave Korn @ 2004-10-12 13:17 UTC (permalink / raw)
To: 'Andrew Haley', gcc; +Cc: overseers
> -----Original Message-----
> From: gcc-owner On Behalf Of Andrew Haley
> Sent: 12 October 2004 14:10
> Despite doing my branch commit in individual directories rather than
> top level, I got this message again today:
>
> Protocol error: too many arguments
>
> Last time I saw this error it resulted in corrupted attr files on the
> server.
>
> I'll try a fresh checkout once my commit is done.
>
> Andrew.
Should probably Cc overseers, as a heads-up.
cheers,
DaveK
--
Can't think of a witty .sigline today....
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: Protocol error: too many arguments
2004-10-12 13:17 ` Protocol error: too many arguments Dave Korn
@ 2004-10-12 13:21 ` Andrew Haley
2004-10-12 13:38 ` Ian Lance Taylor
2004-10-12 14:14 ` Dave Korn
0 siblings, 2 replies; 10+ messages in thread
From: Andrew Haley @ 2004-10-12 13:21 UTC (permalink / raw)
To: Dave Korn; +Cc: gcc, overseers
Dave Korn writes:
> > -----Original Message-----
> > From: gcc-owner On Behalf Of Andrew Haley
> > Sent: 12 October 2004 14:10
>
> > Despite doing my branch commit in individual directories rather than
> > top level, I got this message again today:
> >
> > Protocol error: too many arguments
> >
> > Last time I saw this error it resulted in corrupted attr files on the
> > server.
> >
> > I'll try a fresh checkout once my commit is done.
>
> Should probably Cc overseers, as a heads-up.
Any mail I send to overseers bounces.
I wonder if anyone knows exactly what the limit is. I'm guessing it's
maybe a postcommit script that hits a kernel limit on the number of
arguments to a command.
Andrew.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Protocol error: too many arguments
2004-10-12 13:21 ` Andrew Haley
@ 2004-10-12 13:38 ` Ian Lance Taylor
2004-10-12 13:43 ` Andrew Haley
2004-10-12 14:14 ` Dave Korn
1 sibling, 1 reply; 10+ messages in thread
From: Ian Lance Taylor @ 2004-10-12 13:38 UTC (permalink / raw)
To: Andrew Haley; +Cc: Dave Korn, gcc, overseers
Andrew Haley <aph@redhat.com> writes:
> Dave Korn writes:
> > > -----Original Message-----
> > > From: gcc-owner On Behalf Of Andrew Haley
> > > Sent: 12 October 2004 14:10
> >
> > > Despite doing my branch commit in individual directories rather than
> > > top level, I got this message again today:
> > >
> > > Protocol error: too many arguments
> > >
> > > Last time I saw this error it resulted in corrupted attr files on the
> > > server.
> > >
> > > I'll try a fresh checkout once my commit is done.
> >
> > Should probably Cc overseers, as a heads-up.
>
> Any mail I send to overseers bounces.
>
> I wonder if anyone knows exactly what the limit is. I'm guessing it's
> maybe a postcommit script that hits a kernel limit on the number of
> arguments to a command.
Current versions of the CVS server only accepts up to 10000 files in a
single commit. I think this is a misguided attempt to limit memory
usage in the server.
Ian
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Protocol error: too many arguments
2004-10-12 13:38 ` Ian Lance Taylor
@ 2004-10-12 13:43 ` Andrew Haley
2004-10-13 2:27 ` Ian Lance Taylor
0 siblings, 1 reply; 10+ messages in thread
From: Andrew Haley @ 2004-10-12 13:43 UTC (permalink / raw)
To: Ian Lance Taylor; +Cc: Dave Korn, gcc, overseers
Ian Lance Taylor writes:
> Andrew Haley <aph@redhat.com> writes:
>
> > Dave Korn writes:
> > > > -----Original Message-----
> > > > From: gcc-owner On Behalf Of Andrew Haley
> > > > Sent: 12 October 2004 14:10
> > >
> > > > Despite doing my branch commit in individual directories rather than
> > > > top level, I got this message again today:
> > > >
> > > > Protocol error: too many arguments
> > > >
> > > > Last time I saw this error it resulted in corrupted attr files on the
> > > > server.
> > > >
> > > > I'll try a fresh checkout once my commit is done.
> > >
> > > Should probably Cc overseers, as a heads-up.
> >
> > Any mail I send to overseers bounces.
> >
> > I wonder if anyone knows exactly what the limit is. I'm guessing it's
> > maybe a postcommit script that hits a kernel limit on the number of
> > arguments to a command.
>
> Current versions of the CVS server only accepts up to 10000 files in a
> single commit. I think this is a misguided attempt to limit memory
> usage in the server.
10,000 files! Eek! Well, I didn't think I was committing that many.
Is that what the "Protocol error: too many arguments" message refers
to, do you know?
Andrew.
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: Protocol error: too many arguments
2004-10-12 13:21 ` Andrew Haley
2004-10-12 13:38 ` Ian Lance Taylor
@ 2004-10-12 14:14 ` Dave Korn
2004-10-12 14:30 ` Christopher Faylor
1 sibling, 1 reply; 10+ messages in thread
From: Dave Korn @ 2004-10-12 14:14 UTC (permalink / raw)
To: 'Andrew Haley'; +Cc: gcc, overseers
> -----Original Message-----
> From: gcc-owner On Behalf Of Andrew Haley
> Sent: 12 October 2004 14:20
> Dave Korn writes:
> > Should probably Cc overseers, as a heads-up.
>
> Any mail I send to overseers bounces.
I had that problem the other day last time we had a fileattr bug. Turns
out you have to be sure what domain you're trying to mail overseers at. The
overseers name only exists at sources / redhat / com; you can't email it at
gcc / gnu / org, or you get a SMTP "550 unknown user" error.
Hey, Overseers, is that deliberate?
... Or is it just an oversight? <ba-dum tish!>
cheers,
DaveK
--
Can't think of a witty .sigline today....
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Protocol error: too many arguments
2004-10-12 14:14 ` Dave Korn
@ 2004-10-12 14:30 ` Christopher Faylor
2004-10-12 14:36 ` Andrew Haley
0 siblings, 1 reply; 10+ messages in thread
From: Christopher Faylor @ 2004-10-12 14:30 UTC (permalink / raw)
To: overseers
On Tue, Oct 12, 2004 at 03:14:14PM +0100, Dave Korn wrote:
>> -----Original Message-----
>> From: gcc-owner On Behalf Of Andrew Haley
>> Sent: 12 October 2004 14:20
>
>> Dave Korn writes:
>
>> > Should probably Cc overseers, as a heads-up.
>>
>> Any mail I send to overseers bounces.
>
>I had that problem the other day last time we had a fileattr bug.
>Turns out you have to be sure what domain you're trying to mail
>overseers at. The overseers name only exists at sources / redhat /
>com; you can't email it at gcc / gnu / org, or you get a SMTP "550
>unknown user" error.
>
>Hey, Overseers, is that deliberate?
No. I can't imagine how we'd even accomplish such a feat since gcc.gnu.org
and sources.redhat.com are the same system.
I guess if this mail makes it through it will prove or disprove your theory.
cgf
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Protocol error: too many arguments
2004-10-12 14:30 ` Christopher Faylor
@ 2004-10-12 14:36 ` Andrew Haley
2004-10-12 15:20 ` Dave Korn
0 siblings, 1 reply; 10+ messages in thread
From: Andrew Haley @ 2004-10-12 14:36 UTC (permalink / raw)
To: Christopher Faylor; +Cc: overseers, gcc, Dave Korn
Christopher Faylor writes:
> On Tue, Oct 12, 2004 at 03:14:14PM +0100, Dave Korn wrote:
> >> -----Original Message-----
> >> From: gcc-owner On Behalf Of Andrew Haley
> >> Sent: 12 October 2004 14:20
> >
> >> Dave Korn writes:
> >
> >> > Should probably Cc overseers, as a heads-up.
> >>
> >> Any mail I send to overseers bounces.
> >
> >I had that problem the other day last time we had a fileattr bug.
> >Turns out you have to be sure what domain you're trying to mail
> >overseers at. The overseers name only exists at sources / redhat /
> >com; you can't email it at gcc / gnu / org, or you get a SMTP "550
> >unknown user" error.
> >
> >Hey, Overseers, is that deliberate?
>
> No. I can't imagine how we'd even accomplish such a feat since gcc.gnu.org
> and sources.redhat.com are the same system.
>
> I guess, if this mail makes it through, it will prove or disprove your theory.
I think the error was overseers@gnu.org not overseers@gcc.gnu.org.
Andrew.
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: Protocol error: too many arguments
2004-10-12 14:36 ` Andrew Haley
@ 2004-10-12 15:20 ` Dave Korn
2004-10-12 21:55 ` Phil Edwards
0 siblings, 1 reply; 10+ messages in thread
From: Dave Korn @ 2004-10-12 15:20 UTC (permalink / raw)
To: 'Andrew Haley', 'Christopher Faylor'; +Cc: overseers, gcc
> -----Original Message-----
> From: Andrew Haley
> Sent: 12 October 2004 15:37
> Christopher Faylor writes:
> > On Tue, Oct 12, 2004 at 03:14:14PM +0100, Dave Korn wrote:
> > >I had that problem the other day last time we had a fileattr bug.
> > >Turns out you have to be sure what domain you're trying to mail
> > >overseers at. The overseers name only exists at sources
> / redhat /
> > >com; you can't email it at gcc / gnu / org, or you get a SMTP "550
> > >unknown user" error.
> > >
> > >Hey, Overseers, is that deliberate?
> >
> > No. I can't imagine how we'd even accomplish such a feat
> > since gcc.gnu.org and sources.redhat.com are the same system.
Easy enough. Just because the DNS MX records for both domains point to
the same IP address doesn't mean the MTA at that machine can't make
different routing decisions based on the actual domain listed in the smtp
envelope/headers.
> > I guess, if this mail makes it through, it will prove or
> disprove your theory.
>
> I think the error was overseers [SPLAT] gnu.org not overseers [BOING]
gcc.gnu.org.
Turns out it was, which explains part of it.
Well, some of it. But not this bounce:
Your message
To: overseers [TOAD] sources.redhat.com
Subject: RE: cvs problems ...
Sent: Fri, 8 Oct 2004 12:49:03 +0100
did not reach the following recipient(s):
overseers [ELEPHANT] sources.redhat.com on Fri, 8 Oct 2004 12:49:03 +0100
You do not have permission to send to this recipient. For
assistance, contact your system administrator.
<NUTMEG.CAM.ARTIMI.COM #5.7.1>
571 is no relaying. Dunno what happened there, but I guess it was
transient.
cheers,
DaveK
--
Can't think of a witty .sigline today....
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Protocol error: too many arguments
2004-10-12 15:20 ` Dave Korn
@ 2004-10-12 21:55 ` Phil Edwards
0 siblings, 0 replies; 10+ messages in thread
From: Phil Edwards @ 2004-10-12 21:55 UTC (permalink / raw)
To: Dave Korn; +Cc: overseers
[removed gcc@ from the cc list]
On Tue, Oct 12, 2004 at 04:19:43PM +0100, Dave Korn wrote:
> > I think the error was overseers [SPLAT] gnu.org not overseers [BOING]
> gcc.gnu.org.
>
> Turns out it was, which explains part of it.
We could actually fix that. Trivially.
I'd strongly recommend that we don't, though. Anything with a @gnu.org
address gets spammed to hell and back.
--
Behind everything some further thing is found, forever; thus the tree behind
the bird, stone beneath soil, the sun behind Urth. Behind our efforts, let
there be found our efforts.
- Ascian saying, as related by Loyal to the Group of Seventeen
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Protocol error: too many arguments
2004-10-12 13:43 ` Andrew Haley
@ 2004-10-13 2:27 ` Ian Lance Taylor
0 siblings, 0 replies; 10+ messages in thread
From: Ian Lance Taylor @ 2004-10-13 2:27 UTC (permalink / raw)
To: Andrew Haley; +Cc: Dave Korn, gcc, overseers
Andrew Haley <aph@redhat.com> writes:
> > > > > Despite doing my branch commit in individual directories rather than
> > > > > top level, I got this message again today:
> > > > >
> > > > > Protocol error: too many arguments
> > > > >
> > > > > Last time I saw this error it resulted in corrupted attr files on the
> > > > > server.
> > > > >
> > > > > I'll try a fresh checkout once my commit is done.
> > > >
> > > > Should probably Cc overseers, as a heads-up.
> > >
> > > Any mail I send to overseers bounces.
> > >
> > > I wonder if anyone knows exactly what the limit is. I'm guessing it's
> > > maybe a postcommit script that hits a kernel limit on the number of
> > > arguments to a command.
> >
> > Current versions of the CVS server only accepts up to 10000 files in a
> > single commit. I think this is a misguided attempt to limit memory
> > usage in the server.
>
> 10,000 files! Eek! Well, I didn't think I was committing that many.
>
> Is that what the "Protocol error: too many arguments" message refers
> to, do you know?
If you got the error during a commit, then, yes. Each file is a
separate argument.
Ian
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2004-10-13 2:27 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <16747.55189.754030.610553@cuddles.cambridge.redhat.com>
2004-10-12 13:17 ` Protocol error: too many arguments Dave Korn
2004-10-12 13:21 ` Andrew Haley
2004-10-12 13:38 ` Ian Lance Taylor
2004-10-12 13:43 ` Andrew Haley
2004-10-13 2:27 ` Ian Lance Taylor
2004-10-12 14:14 ` Dave Korn
2004-10-12 14:30 ` Christopher Faylor
2004-10-12 14:36 ` Andrew Haley
2004-10-12 15:20 ` Dave Korn
2004-10-12 21:55 ` Phil Edwards
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 read-only IMAP folder(s) and NNTP newsgroup(s).