Mail Archives: cygwin/2001/12/28/10:02:40
Thanks for the reply Peter. While your suggestions didn't fix the problem, they did get me thinking and digging back into things.
Ultimately turned out that the problem was that while the system PATH environment variable had "c:\cygwin" defined, it did not include path "c:\cygwin\bin". I was starting sshd from the c:\cygwin\bin directory, but I'll bet that when new sshd process was spawned for the incoming connection, it wasn't finding cgywin1.dll, and possibly other needed components, in the c:\cygwin\bin directory because it wasn't in the path. Once c:\cygwin\bin was in the path, everything worked swell.
Regards,
John
>>> Peter Buckley <peter DOT buckley AT cportcorp DOT com> 12/27/01 01:42PM >>>
> I am taking a wild guess- when you ssh in, it spawns a shell and then
> still does some ssh-ish tasks. Maybe it can't complete them from the
> command shell.
>
> Are you logging in or just firing off remote processes?
>
> It might be worth trying to set your shell to /bin/bash, ssh in and see
> if you can then start a command shell. Maybe-
>
> ssh machine "cd /cygdrive/c/path-to-batch-file; cmd /c mytest.bat; sleep 2"
>
> (the 'sleep x' might not be necessary with ssh, but it is with rsh if
> you want all the output from the last command)
>
> I don't have sshd running anywhere remotely, but I can rlogin to a
> machine running inetd, it starts a bash shell, and then I type "cmd" and
> it gives me a command shell.
>
> HTH (or at least spawns some discussion),
> Peter
>
> John Fishbeck wrote:
>
>> Hi all,
>>
>> I posted the message appended at the end of this one last week, and didn't receive a _single_ response to it. This leads me to believe that either 1) I have unwittingly committed some horrendous faux pax, despite the fact that I did attempt to research this problem before posting to this list, or 2) this is a bizarre problem which others have not encountered nor know what to do about.
>>
>> If (1) above, I sincerely apologize and ask forgiveness, and would urge some kind soul to take pity on me and direct me to the problem solution that I missed in my research. If (2), I guess I'm just going to have to abandon the Cygwin OpenSSH solution and figure out some other approach - perhaps MS telnet service (shudder...).
>>
>> Anybody out there gonna take pity on a poor IT schmuck in need of help?
>>
>> John Fishbeck
>> MSU Physical Plant Computer Systems
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -