This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: path problems when logged in through ssh

On Mon, Dec 17, 2001 at 12:43:37PM -0800, David Rothenberger wrote:
> I had a similar problem with ssh.  In my case, I couldn't even log in
> through ssh because the spawned child process could not find the cygwin
> DLL.  The problem was that my system PATH value was longer than 512
> characters.
> The sshd daemon is supposed to copy its environment for the child
> process.  Through debugging, I determined the child process did get a
> copy of the daemon's environment -- except for PATH, which was set to
> some useless default like /usr/sbin:/c/WINNT that didn't include the
> cygwin directory.
> I looked at the sshd sources and noticed a limit on the environment
> value sizes of 512 in the code that copies the environment.  Since
> shortening my system PATH value was not an option, I solved the problem
> by overriding the PATH value for the sshd daemon's environment.  I did
> this by editing the registry for my sshd service, but you can also do it
> by recreating the sshd service with cygrunsrv and specifying the PATH
> value as part of the service's environment.

Just to claify here.  You're not talking about OpenSSH but of,
right?  There's no limit of the length of environment variables in
OpenSSH nor is PATH truncated to some default value in thr Cygwin version.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                      
Red Hat, Inc.

Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]