This is the mail archive of the
cygwin
mailing list for the Cygwin project.
sshd, plink, bash and path problems
- From: Tim Shadel <timshadel at pobox dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 05 May 2004 18:56:51 -0700
- Subject: sshd, plink, bash and path problems
I'm not subscribed to the list. Kindly CC: me in any threads that
result from this email. Thanks.
Here's my setup:
Client: Win2K box with Putty/Plink
Server: Win2K professional with cygwin/sshd (actually copssh, but it's
just a minimal cygwin install)
I can login just fine. I can use public key authentication fine.
Here's what I'd like to do:
plink -batch -2 -i C:\path\to\my\key\mykey.PPK -l tims 159.87.127.66
mkdir -p /var/some/dir/that/does/not/exist
Nothing happens. Here's something else I tried to see what's going on:
plink -batch -2 -i C:\path\to\my\key\mykey.PPK -l tims 159.87.127.66
echo $PATH
/cygdrive/c/j2sdk...
Basically my entire Windows path prints out -- NOT my cygwin path. I
saw another post on this in a different context
(http://www.cygwin.com/ml/cygwin/2003-07/msg01700.html), and I can see
that it's a matter of commands getting executed when the login process
happens. So then I tried this:
plink -batch -2 -i C:\path\to\my\key\mykey.PPK -l tims 159.87.127.66
source /etc/profile; echo $PATH
/bin:/cygdrive/c/WINNT/system32:/cygdrive/c/WINNT
And got the output I expected. BUT, the plink command is being issued
by a program that I can't modify (apache's maven deploy plugin), so I
wondered two things:
1. What's different between plink <host> <command> and plink <host>
(which displays a prompt) that causes the magical "login" process to
occur. Is this a plink thing? a bash thing? a cygwin-version-of-either
thing?
2. Is there a file (.rc something-or-other perhaps?) that I can create
that will make the "source /etc/profile" call once plink connects, so I
can have the right path when <command> happens?
Any help with this would be most appreciated.
Thanks,
Tim Shadel
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/