Robert Lewis wrote:
> I have searched thru the mail lists but can not find a
> solution to the
> problem. This error occurs for any operation I try to due.
> Mostly I was
> just trying to do a commit as a test.
>
> cvs [commit aborted]: Invalid Lockserver version - got 1
I have searched thru the mail lists but can not find a solution to the
problem. This error occurs for any operation I try to due. Mostly I was
just trying to do a commit as a test.
cvs [commit aborted]: Invalid Lockserver version - got 1.2, wanted 2.1
I am using Windows XP home edition sp2
PRC (in directory
> S:\CityOfSammamish\bin\sql\)
> Removing dbo.CitNewsSelect.PRC;
>
> cvs commit: Dropping data: pos>vec->nlines
>
> cvs [commit aborted]: invalid change text in
> c:/cvsroot/CityOfSammamish/bin/sql/dbo.CitNewsSelect.PRC,v
>
> * CVS exited normall
I am getting an error trying to update a unicode file. Here is what I am
seeing:
cvs commit -m "no message" dbo.CitNewsSelect.PRC (in directory
S:\CityOfSammamish\bin\sql\)
Removing dbo.CitNewsSelect.PRC;
cvs commit: Dropping data: pos>vec->nlines
cvs [commit aborted]: invalid
McMurray, James writes:
>
> I do currently have a Windows 2000 client and Linux server setup. Is there a
> way to implement this?
Of course, that's what lots of people do!
> We are using Samba to communicate between the two, if that helps.
No, it doesn't; in fact, it's almost certainly the roo
:55 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: cvs [commit aborted]: lock failed - giving up
McMurray, James writes:
>
> There is no LockDir= in the config file. In fact, the config file is still
> the default one that was created at install.
In that case, my second gues
McMurray, James writes:
>
> There is no LockDir= in the config file. In fact, the config file is still
> the default one that was created at install.
In that case, my second guess is that you're trying to share a working
directory between DOS/Windows and Unix, which is a no-no due to the
differe
]
Subject: Re: cvs [commit aborted]: lock failed - giving up
McMurray, James writes:
>
> /#cvs.lock): No such file or directoryctory for `/home/my/cvs/repository
> cvs commit: lock failed - giving up
> cvs [commit aborted]: lock failed - giving up
That error message is garbled -- my guess
McMurray, James writes:
>
> /#cvs.lock): No such file or directoryctory for `/home/my/cvs/repository
> cvs commit: lock failed - giving up
> cvs [commit aborted]: lock failed - giving up
That error message is garbled -- my guess is that you have LockDir= in
your CVSROOT/config file
Hi everyone, I'm trying to commit files into the repository and here is the
error message I get:
/#cvs.lock): No such file or directoryctory for `/home/my/cvs/repository
cvs commit: lock failed - giving up
cvs [commit aborted]: lock failed - giving up
I have previously locked the two fi
Gustavo Delfino writes:
>
> My working directory is on a Windows 2000 machine wich I access via
> SMB from my Mac OS X machine.
That's undoubtedly the problem. Windows is screwy, SMB is doubly
screwy, and SMB on Mac is likely screwy squared.
-Larry Jones
What's the matter? Don't you trust yo
On 4/23/02 at 7:27 PM, [EMAIL PROTECTED] (Robert J. Clark)
wrote:
> That error message is generated by the client with it tries to
> examine or open the file to be sent to the server. Try doing a
> "stat " on the file that is failing and see if that
> provides any useful information about the fil
rom 1.10 to 1.11 using
> fink (a Mac OS X package manager). The problem is still there, but now
> the trace option give a little more information:
>
> cvs -t ci -m "message" filename
> cvs commit: notice: main loop with
> CVSROOT=:pserver:mylogin@servername:/usr/local/cv
ge" filename
cvs commit: notice: main loop with
CVSROOT=:pserver:mylogin@servername:/usr/local/cvs/abc
-> Sending file `filename' to server
cvs [commit aborted]: reading filename: File too large
I'll try to upgrade from 1.11 to 1.11.2, but this is not going to be
easy for me as t
Gustavo Delfino writes:
>
> I suspect that the keyword substitution algorithm may be failing for
> such a wide file. Is there a way to turn off keyword substitution?
There is, but that's not the problem. Keyword substitution doesn't
happen until checkout/update (which happens automatically *af
On Tue, Apr 23, 2002 at 09:07:34AM -0400, Gustavo Delfino wrote:
> I' using cvs 1.10 on the client Mac
> OS X 10.1.4 machine, and the server is cvs 1.11 running on FreeBSD
> 4.4-RELEASE
Those are both *ancient* CVS releases. Try upgrading them.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, On
On 4/23/02 at 10:25 AM, [EMAIL PROTECTED] (gabriel rosenkoetter) wrote:
> Ahem. I read your message but not your subject, so I completely
> misunderstood your problem. My apologies.
>
> Try doing a cvs -t commit and see if the trace messages help any.
That didn't help. The only additional messa
On 4/23/02 at 9:46 AM, [EMAIL PROTECTED] (gabriel rosenkoetter) wrote:
> On Tue, Apr 23, 2002 at 09:07:34AM -0400, Gustavo Delfino wrote:
> > My text file has 605 lines and 396 columns of text, the size is
> > 232k.
>
> Where is the file 605 lines, and where is it 232 K?
>
> If you mean that th
On Tue, Apr 23, 2002 at 09:46:03AM -0400, gabriel rosenkoetter wrote:
> On Tue, Apr 23, 2002 at 09:07:34AM -0400, Gustavo Delfino wrote:
> > My text file has 605 lines and 396 columns of text, the size is 232k.
> Where is the file 605 lines, and where is it 232 K?
Ahem. I read your message but no
On Tue, Apr 23, 2002 at 09:07:34AM -0400, Gustavo Delfino wrote:
> My text file has 605 lines and 396 columns of text, the size is 232k.
Where is the file 605 lines, and where is it 232 K?
If you mean that the checked-out copy is 605 lines and that the copy
in the repository is 232 K, that seems
My text file has 605 lines and 396 columns of text, the size is 232k.
The file has DOS line endings, and I' using cvs 1.10 on the client Mac
OS X 10.1.4 machine, and the server is cvs 1.11 running on FreeBSD
4.4-RELEASE
I have looked on the cederqvist manual, and mailing lists, FAQs and
google wi
Since switching to the latest CVS development code base, I now get
different results:
$ cvs -t update build.xml
cvs update: notice: main loop with
[EMAIL PROTECTED]:/space/cvsroot
-> Starting server: ssh xx.xx.xx.xx -l dhoag cvs server
S-> Reader_Lock(/space/cvsroot/build)
S-> Lock_Cleanup()
I'
David Hoag writes:
>
> Give me a little credit here. I don't kill the process until long
> after the client has died. I realize that if I had killed the process
> prior to the client dieing I would get the "connection reset" error.
> The server process is simply lingering (probably waiting for th
[EMAIL PROTECTED] (Larry Jones) wrote in message
news:<[EMAIL PROTECTED]>...
> Manually killing a server process will cause a "connection reset" error
> at the client. If you don't kill the server process, do you still get
> the client error and, if so, is the server process still running
> afte
David Hoag writes:
>
> The processes are owned by my user id. Started when I initiate a cvs
> update(or commit). They linger until I manually 'kill' them.
Manually killing a server process will cause a "connection reset" error
at the client. If you don't kill the server process, do you still ge
>
> But you also said, "many people use this CVS server". Do the server
> processes you see come and go (which implies that they belong to other
> users) or do some of them stay around forever?
The processes are owned by my user id. Started when I initiate a cvs
update(or commit). They linger u
David Hoag writes:
>
> Like I said:
>
> "When I SSH to the CVS server I see many CVS SERVER processes on the
> box (via ps -ef )."
But you also said, "many people use this CVS server". Do the server
processes you see come and go (which implies that they belong to other
users) or do some of th
Larry, thanks for your patience.
Like I said:
"When I SSH to the CVS server I see many CVS SERVER processes on the
box (via ps -ef )."
So, clearly my server processes are not leaving core files (since they
are not dieing). The /tmp/cvs-serv* directories do exist, and they're
empty.
It appear
David Hoag writes:
>
> Im guessing its related to a slow internet connection (110kb - faster
> than dialup) or something about my provider. Any ideas where to look?
Like I said:
> > Look in the server's TempDir (usually /tmp) for leftover
> > cvs-serv* directories and core files -- if there are
information
> in one shot.
>
> > Read from remote host 192.168.0.1: Connection reset by peer
> > cvs [commit aborted]: end of file from server (consult above messages
> > if any)
>
> That indicates that the server is closing the connection. That could be
> because
More information:
When I SSH to the CVS server I see many CVS SERVER processes on the
box (via ps -ef ).
This problem appears to happen only from one set of IPs. While many
people use this CVS server, I'm the only one experiencing problems (
and from only 1 location ). I have no problems with d
With CVS 1.11, you can just do "cvs version" (that's a command, not an
option, so no -) to get both the client and server version information
in one shot.
> Read from remote host 192.168.0.1: Connection reset by peer
> cvs [commit aborted]: end of file from server (consult above
IL PROTECTED]:/space/cvsroot
-> Starting server: ssh 192.168.0.1 -l dhoag cvs server
-> Sending file `BrokerPropertyDetail.java' to server
-> Sending file `BrokerPropertySource.java' to server
Read from remote host 192.168.0.1: Connection reset by peer
cvs [commit aborted]:
Sachin writes:
>
> Thanks for the info. I have checked that I have enough of swap and tmp
> space free. Inspite of that it gives me an error. I have tried
> checking in a file size of max 60 MB. After that it cribs and starts
> giving the memory error.
> there is some limitation from cvs side its
Sachin wrote:
>
> hi,
> Thanks for the info. I have checked that I have enough of swap and tmp
> space free. Inspite of that it gives me an error. I have tried
> checking in a file size of max 60 MB. After that it cribs and starts
> giving the memory error.
> there is some limitation from cvs sid
20 system and CVS version is 1.11.1p. I am
> > getting the following error messages, cvs [commit aborted]: out of
> > memory; can not reallocate 95683558
> > TIA.
>
> First: Are you really sure you need to put that file under revision contr
> ol?
>What is it?
>
Sachin wrote:
>
> Hi,
> I am trying bytes to checkin a big file of 95MB into a repository. I
> am woking on a HP-UX 10.20 system and CVS version is 1.11.1p. I am
> getting the following error messages, cvs [commit aborted]: out of
> memory; can not reallocate 95683558
>
Hi,
I am trying bytes to checkin a big file of 95MB into a repository. I
am woking on a HP-UX 10.20 system and CVS version is 1.11.1p. I am
getting the following error messages, cvs [commit aborted]: out of
memory; can not reallocate 95683558
TIA
Tuesday, July 10, 2001 9:33 PM
Subject: Re: RTFM? [ was Re: "cvs [commit aborted]: cannot commit files as
'root'"]
> [ On Tuesday, July 10, 2001 at 16:40:04 (+0200), Pascal Bourguignon
wrote: ]
> > Subject: Re: RTFM? [ was Re: "cvs [commit aborted]: cannot commit f
[ On Tuesday, July 10, 2001 at 16:40:04 (+0200), Pascal Bourguignon wrote: ]
> Subject: Re: RTFM? [ was Re: "cvs [commit aborted]: cannot commit files as 'root'"]
>
> Well, you're not alone having difficulties with the CVS manual. Either
> a good number
[EMAIL PROTECTED] (Greg A. Woods) wrote:
>
> [ On Monday, July 9, 2001 at 20:22:56 (-0700), David Taylor wrote: ]
> > Subject: RTFM? [ was Re: "cvs [commit aborted]: cannot commit files as 'root'"]
> >
> > When someone who has long chanted "R
[ On Monday, July 9, 2001 at 20:22:56 (-0700), David Taylor wrote: ]
> Subject: RTFM? [ was Re: "cvs [commit aborted]: cannot commit files as 'root'"]
>
> When someone who has long chanted "RTFM!" as the panacea for countless ills
> can't find
"Greg A. Woods" wrote:
>
> However I don't think the CVS manual itself should go too far to being a
> lazy luser's guide to avoiding learning anything. Yes a separate
> beginners guide might be useful, as might more wide-ranging "how-to"
> documentation, but maybe that's not the business of the
s in
particular, but to a far-too-common attitude.
[EMAIL PROTECTED]
"Greg A. Woods" wrote:
> [ On Monday, July 9, 2001 at 11:40:28 (-0400), Larry Jones wrote: ]
> > Subject: Re: "cvs [commit aborted]: cannot commit files as 'root'"
> >
> >
- Original Message -
From: "Greg A. Woods" <[EMAIL PROTECTED]>
To: "CVS-II Discussion Mailing List" <[EMAIL PROTECTED]>
Sent: Monday, July 09, 2001 11:42 AM
Subject: Re: "cvs [commit aborted]: cannot commit files as 'root'"
>
[ On Monday, July 9, 2001 at 11:40:28 (-0400), Larry Jones wrote: ]
> Subject: Re: "cvs [commit aborted]: cannot commit files as 'root'"
>
> Greg A. Woods writes:
> >
> > It isn't even in the manual, as far as I can see. That's maybe the
lt;[EMAIL PROTECTED]>
Sent: Monday, July 09, 2001 10:40 AM
Subject: Re: "cvs [commit aborted]: cannot commit files as 'root'"
| Greg A. Woods writes:
| >
| > It isn't even in the manual, as far as I can see. That's maybe the
| > worst failing of the manual -
[ On Monday, July 9, 2001 at 09:21:58 (-0500), Daniel Beckham wrote: ]
> Subject: Re: "cvs [commit aborted]: cannot commit files as 'root'"
>
> On one side there are the people who will never read the manual, but will
> expect the mailing list, forums, et. al.
Greg A. Woods writes:
>
> It isn't even in the manual, as far as I can see. That's maybe the
> worst failing of the manual -- there's no (even partial) list of the
> error messages in one place with links to nodes containing their
> explanations.
Excuse me?
http://cvshome.org/docs/manual/cvs_2
[EMAIL PROTECTED] wrote:
>
> cowed by the thought of having Greg yell at them for days that they're
> unwilling to start, or if I'm told that no such patch will be accepted
> to CVS, then it will die here.
>
I generally ignore rants, especially from Mr. Greg Woods. Greg - you're
obviously
You know.. something I've noticed...
On one side there are the people who will never read the manual, but will
expect the mailing list, forums, et. al. to answer every little question
they have whether it's "I can't get my webserver to run cgi scripts" or "how
do I import a new project" or "I don
[ On Monday, July 9, 2001 at 01:03:36 (-0400), Lenny Foner wrote: ]
> Subject: "cvs [commit aborted]: cannot commit files as 'root'"
>
> And with that, I'm outta here. I'd be happy to suggest ways to
> implement this idea, and to discuss the engineering
[ On Monday, July 9, 2001 at 01:03:36 (-0400), Lenny Foner wrote: ]
> Subject: "cvs [commit aborted]: cannot commit files as 'root'"
>
> In that time, you've come across as basically a reactionary force,
> in the original meaning of that term---in other word
Greg. Greg, Greg, Greg.
I've been watching your traffic on info-cvs since about August 1996.
That's over 100 meg of traffic. Of course, not all of it is yours.
In that time, you've come across as basically a reactionary force,
in the original meaning of that term---in other words, just about a
[ On Sunday, July 8, 2001 at 19:27:07 (-0400), Lenny Foner wrote: ]
> Subject: "cvs [commit aborted]: cannot commit files as 'root'"
>
> No, it only says that you can't. It doesn't explain WHY, which was
> precisely the question that was asked.
Well
Date: Sun, 8 Jul 2001 18:28:50 -0400 (EDT)
From: [EMAIL PROTECTED] (Greg A. Woods)
[ On Sunday, July 8, 2001 at 16:00:55 (-0400), Lenny Foner wrote: ]
> Subject: "cvs [commit aborted]: cannot commit files as 'root'"
>
> You know, given how o
[ On Sunday, July 8, 2001 at 16:00:55 (-0400), Lenny Foner wrote: ]
> Subject: "cvs [commit aborted]: cannot commit files as 'root'"
>
> You know, given how often people ask this question, maybe some
> paragraph of your response here should be put INTO THE ERROR
&g
Matthew Von-Maszewski writes:
>
> su to root worked like a champ. Thanks for the work-around.
Perhaps I understated things a bit in my original response. There *are*
security concerns with committing as root -- be very sure you know what
you're doing. Even better, just don't do it.
-Larry Jo
su to root worked like a champ. Thanks for the work-around.
Matthew
-Original Message-
From: Larry Jones [mailto:[EMAIL PROTECTED]]
Sent: Sunday, July 08, 2001 3:27 PM
To: Matthew Von-Maszewski
Cc: [EMAIL PROTECTED]
Subject: Re: "cvs [commit aborted]: cannot commit files as
Date: Sun, 8 Jul 2001 15:26:59 -0400 (EDT)
From: [EMAIL PROTECTED] (Larry Jones)
Matthew Von-Maszewski writes:
>
> cvs [commit aborted]: cannot commit files as 'root'
[...]
> Is this an intended security feature ... or am I just being stupid
Matthew Von-Maszewski writes:
>
> cvs [commit aborted]: cannot commit files as 'root'
[...]
> Is this an intended security feature ... or am I just being stupid again?
It's an intended feature, but it has more to do with maintaining
accountability than security. Since
[ On Sunday, July 8, 2001 at 11:16:40 (-0400), Matthew Von-Maszewski wrote: ]
> Subject: "cvs [commit aborted]: cannot commit files as 'root'"
>
> Is this an intended security feature ... or am I just being
Anyone?
I get the following message attempting to make a commit locally on the CVS
server:
cvs [commit aborted]: cannot commit files as 'root'
$CVSROOT is properly set. All is fine if I switch to another user. File
permissions in the repository look good too.
Is this an intende
Jelle Boomstra writes:
>
> when im committing a _large_ tree in my initial checkin, i frequently get
> this error, Does this have something to do with my OS (HPUX 11) or is it a
> bug? Is this serious or can I just restart my commit?
>
> cvs [commit aborted]: received broken
Hi,
when im committing a _large_ tree in my initial checkin, i frequently get
this error, Does this have something to do with my OS (HPUX 11) or is it a
bug? Is this serious or can I just restart my commit?
cvs [commit aborted]: received broken pipe signal
Thanx
I think it was the smart ones that came up with the general practices.
Noel
[EMAIL PROTECTED] on 2000.04.03 11:44:28
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
cc: [EMAIL PROTECTED] (bcc: Noel L Yap)
Subject: Re: cvs [commit aborted]: cannot commit files as 'root'
on 4/3/0
On Mon, Apr 03, 2000 at 16:42 +0300, Crosby wrote:
>
> I'm a beginner user of CVS and I don't know to resolve this
> error.I've setup a CVS server (I use SuSE Linux 6.3) and I am
> always logged as root.
The software is trying to tell you something (and the handbook
did so, too -- if you would c
on 4/3/00 11:44 AM, Tracy Snell at [EMAIL PROTECTED] wrote:
> Generally accepted practices, such as not doing normal root as root, are
> generally accepted for a reason. No matter how smart you are.
s/root as root/tasks as root/
I need more sleep!
--
Tracy Snell Orlando Office
21s
on 4/3/00 12:40 PM, Crosby at [EMAIL PROTECTED] wrote:
> I use my Linux from a long time and most of time like a root . If you
> (mr. Donald) give commands which are dangerous for your system is your
> problem.
> I know what I'm doing when press Enter after a command.
Generally accepted practice
On Monday, April 3, Donald Sharp wrote:
>
> There is no right answer. cvs was designed to not allow the root user
> to do cvs commands. This has to do with the philosophy about why you
> shouldn't run as root unless you have to. It also goes into the level
> of trust that you are willing to le
On Monday, April 3, Crosby wrote:
> Dear friends ,
> I use my Linux from a long time and most of time like a root . If you
>(mr. Donald) give commands which are dangerous for your system is your problem.
>I know what I'm doing when press Enter after a command.
> For my qu
Crosby writes:
>
> I use my Linux from a long time and most of time like a root . If you
> (mr. Donald) give commands which are dangerous for your system is your problem.
> I know what I'm doing when press Enter after a command.
If you insist on being stupid (and it's your right to do so),
map
> > >
> > > On Mon, 03 Apr 2000, you wrote:
> > > > Don't run cvs as root.
> > > >
> > > > donald
> > > > On Mon, Apr 03, 2000 at 04:42:47PM +0300, Crosby wrote:
> > > > > Hello !
&g
#x27;m a beginner user of CVS and I don't know to resolve this error.I've
> > > > setup a CVS server (I use SuSE Linux 6.3) and I am always logged as root. I've
> > > > import a project but I can't commit the work. The error received is :
> > > >
> > > > cvs [commit aborted]: cannot commit files as 'root'
> > > >
> > > > What should I do ?
> > > >
> > > > Thanks !
> > > >
> > > > Crosby
> > > >
> > > >
> > Hello !
> > > I'm a beginner user of CVS and I don't know to resolve this error.I've
> > > setup a CVS server (I use SuSE Linux 6.3) and I am always logged as root. I've
> > > import a project but I can
; > import a project but I can't commit the work. The error received is :
> >
> > cvs [commit aborted]: cannot commit files as 'root'
> >
> > What should I do ?
> >
> > Thanks !
> >
> > Crosby
> >
> >
On Monday 3 April 2000, at 16 h 42, the keyboard of Crosby
<[EMAIL PROTECTED]> wrote:
> I'm a beginner user of CVS and I don't know to resolve this error.I've
> setup a CVS server (I use SuSE Linux 6.3) and I am always logged as root.
This is certainly one of the most awful errors an Unix use
I've
> import a project but I can't commit the work. The error received is :
>
> cvs [commit aborted]: cannot commit files as 'root'
>
> What should I do ?
>
> Thanks !
>
> Crosby
>
>
Hello !
I'm a beginner user of CVS and I don't know to resolve this error.I've
setup a CVS server (I use SuSE Linux 6.3) and I am always logged as root. I've
import a project but I can't commit the work. The error received is :
cvs [commit aborted]: can
Hello,
I'm trying to put key /etc files into CVS - that works ok.
I'm now trying to setup a job to periodically (daily) commit any changes
in /etc.
If I run it as root, I get the above error.
If I su to a cvs user, the commit stores the changed file to the
repository -but then fails to update
80 matches
Mail list logo
