bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: unrecognized response `ksh: cvs: not found' from cvs server


From: Larry Jones
Subject: Re: unrecognized response `ksh: cvs: not found' from cvs server
Date: Fri, 30 May 2003 21:31:32 -0400 (EDT)

Robert J. Feller writes:
>
> MIME-Version: 1.0
> Content-Type: multipart/mixed; boundary="===============624724047142176=="

Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!

> I'm having a strange problem that I've exhausted all possible tests on
> -- it may be a bug, so I'm hoping that this is the best place to post. 

It's not a bug, it's a system configuration problem.  This is probably
not the best place to post, but it may be good enough.  :-)

> cvs checkout -P lib (in directory C:\proj1) 
> cvs checkout: warning: unrecognized response `ksh: cvs:  not found' from
> cvs server 
[...]
> What is it about the "ape" account on Windows or HP-UX that makes it
> always work and the other accounts fail? 

When you run a command with rsh (which is what CVS is doing), the shell
you get on the remote machine is not an interactive shell, so it does
not process your .profile or equivalent (most shells don't even process
the system-wide profile).  Your problem is that CVS is not on the
default $PATH, so you get the "not found" error.  Some shells have
another startup file that they read even in non-interactive mode -- it
appears that the "ape" account has such a file that sets $PATH
correctly.  You'll have to consult your HP-UX documentation to find out
what to look for.  (You may also want to check whether "ape" is using a
different shell than the other accounts.)  You can either configure all
the rest of your accounts like "ape", figure out how to set the default
$PATH to include the CVS directory, or have everyone set $CVS_SERVER on
their client machines to include the full path to CVS on the server.

-Larry Jones

Some people just don't have inquisitive minds. -- Calvin




reply via email to

[Prev in Thread] Current Thread [Next in Thread]