Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Hmmm: when I use :local:, cvs up -p responds fine. It fails using :pserver: and :fork: with the following: rsh:~/tester>cvs up -p test =================================================================== Checking out test RCS: /home/cvs/tester/test,v VERS: 1.1 *************** cvs [update aborted]: end of file from server (consult above messages if any) With sserver, I get rsh:~/tester>cvs up -p test =================================================================== Checking out test RCS: /home/cvs/tester/test,v VERS: 1.1 *************** Read data failed (5): error:00000000:lib(0):func(0):reason(0)cvs [update aborted]: reading from server: error -1 "Tony Hoyle" <tmh at nodomain.org> wrote in message news:d0hjun$ob1$1 at paris.nodomain.org... > Mark Levedahl wrote: >> Using cvsnt 2.5.01.1898 client on Windows against Linux version (built >> from 1898 sources), cvs up -p <filename> aborts with: >> >> cvs [update aborted]: end of file from server (consult above messages if >> any) >> >> when used against any file I add to the repository using the new server. >> This command works fine against files added by earlier versions of the >> server. I notice no such issues when using a Windows server either. >> > Works fine here. cvs.cvsnt.org is a Linux server, so it gets a fair bit > of testing normally. > > Can you find out what your linux machine is complaining about? (Just > access it in local mode - should have the same effect). > > Tony