Re: path problems when logged in through ssh

2001-12-18 Thread David Rothenberger
Just to clarify a bit, the problem I had was with the sftp-server process, not getting an interactive session with sshd. I coiuld get interactive sessions without problems. It was when I started sftp that I got the DLL not found error. Corinna Vinschen wrote: > > On Tue, Dec 18, 2001 at 08:49:

Re: path problems when logged in through ssh

2001-12-18 Thread Corinna Vinschen
On Tue, Dec 18, 2001 at 08:49:18AM -0800, David Rothenberger wrote: > I thought there was a limit because the char[] array for the > environment value in copyEnvironment() was 512. (This is from > memory, so I may be a little off here.) No, you're not off. I just looked into the child_set_env()

Re: path problems when logged in through ssh

2001-12-18 Thread David Rothenberger
Corinna Vinschen wrote: > > 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

Re: path problems when logged in through ssh

2001-12-18 Thread Corinna Vinschen
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.

Re: path problems when logged in through ssh

2001-12-17 Thread David Rothenberger
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.

Re: path problems when logged in through ssh

2001-12-17 Thread Larry Hall (RFK Partners, Inc)
Most folk set their path in /etc/profile or ~/.profile. I believe that Cygwin setup will produce a /etc/profile that does this (perhaps I'm wrong now - I haven't checked this recently). So the answer is at least a variant of what you found - you weren't setting the path in the environment for w

Re: path problems when logged in through ssh

2001-12-17 Thread Peter Buckley
What is your system path? It looks rather unusual. Maybe there is a problem with it. HTH, Peter C. Porter Bassett wrote: > Like I said in my original post, d:/cygwin/bin *IS* in my system path, > but when I try to run something through ssh, it doesn't use the sytem > path. > > I did find the

Re: path problems when logged in through ssh

2001-12-17 Thread C. Porter Bassett
Like I said in my original post, d:/cygwin/bin *IS* in my system path, but when I try to run something through ssh, it doesn't use the sytem path. I did find the solution, which is to put /bin in my .bashrc. I did not have it there because it was never needed before. For some reason, now it is

Re: path problems when logged in through ssh

2001-12-17 Thread Peter Buckley
It sounds like D:\cygwin\bin is not in your system path. The location of the cygwin1.dll needs to be in your system path to run sshd as a service. HTH, Peter Larry Hall (RFK Partners, Inc) wrote: > At 04:01 PM 12/15/2001, C. Porter Bassett wrote: > >>When I ssh into my machine and try to run

Re: path problems when logged in through ssh

2001-12-17 Thread Larry Hall (RFK Partners, Inc)
At 04:01 PM 12/15/2001, C. Porter Bassett wrote: >When I ssh into my machine and try to run things installed in >/usr/local/bin or /usr/sbin, windows pops up an error message saying "The >dynamic link library cygwin1.dll could not be found in the specified path >d:\cygwin\usr\local\bin;.;C:\WINNT\

path problems when logged in through ssh

2001-12-15 Thread C. Porter Bassett
When I ssh into my machine and try to run things installed in /usr/local/bin or /usr/sbin, windows pops up an error message saying "The dynamic link library cygwin1.dll could not be found in the specified path d:\cygwin\usr\local\bin;.;C:\WINNT\system32;C:\WINNTsystem;C\WINNT;." or if it is for a