Hello,
since the crash, every cvs operation I do hangs at the end. [Concurrent Versions System (CVS) 1.11.1p1 (client/server)] For example:
tba:/usr/local/src/wine/ $ cvs status configure.ac =================================================================== File: configure.ac Status: Up-to-date
Working revision: 1.151 Repository revision: 1.151 /home/wine/wine/configure.ac,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none)
<wait for a very long time, then get bored and press ^C> cvs [status aborted]: received interrupt signal
The same for an update, too. It seems to do a perfect job, though. cvs is sleeping in tcp_data_wait indefinitely. I have no idea what can cause this. Any advice?
Feri.
Ferenc Wagner wferi@tba.elte.hu writes:
Hello,
since the crash, every cvs operation I do hangs at the end. [Concurrent Versions System (CVS) 1.11.1p1 (client/server)]
...
<wait for a very long time, then get bored and press ^C> cvs [status aborted]: received interrupt signal
The same for an update, too. It seems to do a perfect job, though. cvs is sleeping in tcp_data_wait indefinitely. I have no idea what can cause this. Any advice?
I had this problem also, but only when using ':ext:'. After an update to the newest version ov CVS (1.11.5) the problem was solved.
Michael
If this continues to be a problem let me know. We are in the process of rebuilding/upgrading the server after the crash. If you notice problems please point them out.
On Fri, 2003-04-25 at 14:34, Michael Günnewig wrote:
Ferenc Wagner wferi@tba.elte.hu writes:
Hello,
since the crash, every cvs operation I do hangs at the end. [Concurrent Versions System (CVS) 1.11.1p1 (client/server)]
...
<wait for a very long time, then get bored and press ^C> cvs [status aborted]: received interrupt signal
The same for an update, too. It seems to do a perfect job, though. cvs is sleeping in tcp_data_wait indefinitely. I have no idea what can cause this. Any advice?
I had this problem also, but only when using ':ext:'. After an update to the newest version ov CVS (1.11.5) the problem was solved.
Michael
Try altering the compression level used with -z, iirc there is a bug in CVS (some versions) where it'll have the symptoms you describe when using compression
On Fri, 2003-04-25 at 19:40, Ferenc Wagner wrote:
Hello,
since the crash, every cvs operation I do hangs at the end. [Concurrent Versions System (CVS) 1.11.1p1 (client/server)] For example:
tba:/usr/local/src/wine/ $ cvs status configure.ac
File: configure.ac Status: Up-to-date
Working revision: 1.151 Repository revision: 1.151 /home/wine/wine/configure.ac,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none)
<wait for a very long time, then get bored and press ^C> cvs [status aborted]: received interrupt signal
The same for an update, too. It seems to do a perfect job, though. cvs is sleeping in tcp_data_wait indefinitely. I have no idea what can cause this. Any advice?
Feri.
Mike Hearn mike@theoretic.com writes:
Try altering the compression level used with -z, iirc there is a bug in CVS (some versions) where it'll have the symptoms you describe when using compression
Thanks for the suggestion. Basically, it hangs for every values of -z except 0. Seems like my client has trouble with the new server when compression is enabled. I will upgrade some time or other. Feri.