A forgotten detail or two: On Mon, Oct 03, 2005 at 07:18:34PM -0400, Doug Lee wrote: > I run a CVS 1.11.17 serveron FreeBSD and a CVS 1.11.17 client under > various Windows versions. I use Cygwin ssh for the transport. > > On a Win98 machine, commands execute but hang after completing their > work. Example: `cvs status proj.c' will print all it should but not > return to a prompt until I type Ctrl+C. This is consistent across all > commands. Typing Ctrl+C is not my favorite thing to do to CVS. :-) > > `cvs -t ...' shows the hang always occurs in (or after) > Lock_Cleanup(). There are no lock files I can see hanging around on > the server, and CVS commands from other places (local and remote, ssh > and non-ssh) work fine. The Win98 machine's Cygwin ssh client appears > to work also, including returning to its caller when terminating. I > tested this both with an interactive ssh shell and by running `ls' > using the same syntax shown by `cvs -t' (namely, `cvs <addr> ls').
A successful `cvs -t ...' run (from another machine) ends with this: S-> Lock_Cleanup() -> Lock_Cleanup() -> Lock_Cleanup() An unsuccessful (Win98 machine) run ends with this: S-> Lock_Cleanup() (long pause, then I type Ctrl+C) CVS.EXE [status aborted]: received interrupt signal -> Lock_Cleanup() Killed by signal 2. > Any ideas? -- Doug Lee [EMAIL PROTECTED] http://www.dlee.org BART Group [EMAIL PROTECTED] http://www.bartsite.com "Determine that the thing can and shall be done, and then...find the way." - Abraham Lincoln _______________________________________________ Info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
