Ahh ... I didn't know about the version command. As already pointed out by me in my original post, CVSROOT environment variable is set. $ echo $CVSROOT somecvsserver.com:/CVSROOT $ cd ~/dev/someproj $ cvs version cvs version: No CVSROOT specified! Please use the `-d' option cvs [version aborted]: or set the CVSROOT environment variable. $ cd neerajprojects $ cvs -t version -> main loop with CVSROOT=:ext:nmahajan@ somecvsserver.com:/CVSROOT Client: Concurrent Versions System (CVS) 1.11.22 (client/server) -> Starting server: rsh -l nmahajan somecvsserver.com cvs server Root /CVSROOT Valid-responses ok error Valid-requests Checked-in New-entry Checksum Copy-file Updated Created Update-existing Merged Patched Rcs-diff Mode Mod-time Removed Remove-entry Set-static-directory Clear-static-directory Set-sticky Clear-sticky Template Notified Module-expansion Wrapper-rcsOption M Mbinary E F MT valid-requests rcmdsh: fork failed: Resource temporarily unavailable
============== This command doesn't exit after this, neither does it print anything else .. so I killed it after waiting for 5 mins ... ============== I also have cvs version 1.11.17 installed in different root (using chroot). The cvs update fails for both versions of cvs i.e. 1.11.17 as well as 1.11.22 .. If I use 1.11.17 version to do cvs version then this is what I see .. $ echo $CVSROOT somecvsserver.com:/CVSROOT $ cd ~/dev/someproj $ cvs version cvs version: No CVSROOT specified! Please use the `-d' option cvs [version aborted]: or set the CVSROOT environment variable. $ cd neerajprojects $ cvs -t version -> main loop with CVSROOT=:ext:nmahajan@ somecvsserver.com:/CVSROOT Client: Concurrent Versions System (CVS) 1.11.17-FreeBSD (client/server) -> Starting server: ssh -l nmahajan somecvsserver.com cvs server Server: Concurrent Versions System (CVS) '1.11.17'-FreeBSD (client/server) -> Lock_Cleanup() -> Lock_Cleanup() ============== Unlike the newer version, this cvs version exits after printing this ============== -----Original Message----- From: Larry Jones [mailto:[EMAIL PROTECTED] Sent: Monday, April 07, 2008 12:17 PM To: Neeraj Mahajan Cc: [email protected] Subject: Re: cvs update fails, Neeraj Mahajan writes: > > $ cvs -version That's the same as ``cvs -v -e -r -s -i -o -n'' -- "version" is a subcommand like update or import, not an option. > === -t didn't give much ===> > > $ cvs -nft update neerajprojects/project1 > cvs update: No CVSROOT specified! Please use the `-d' option > cvs [update aborted]: or set the CVSROOT environment variable. > -> Lock_Cleanup() CVS always needs some default CVSROOT setting. You either need to run it in a directory that contains a CVS/Root file or, like the above message says, you need to specify a default CVSROOT on the command line using the -d global option or you need to set the $CVSROOT environment variable. Update will look at the CVS/Root file in each directory being updated to get the correct CVSROOT for that directory, but it still needs a default setting as well. -Larry Jones I'm getting disillusioned with these New Years. -- Calvin
