This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: ssh localhost date # "ls -lu" => remote command not being read
Solving this issue is important to us. We have a tool
that triggers a remote job via an ssh client. If this
general approach works:
ssh remotehostname "job arg1 arg2.."
I think our tool will work.
On Mon 12/26/05 16:31 CST Tom Rodman wrote:
--snip
> my mistake, I just re-ran the failing test case, and put
> the logs on a web server:
>
> for DOS cmd.exe window log see:
>
> http://yz4.org/cygwin/051226/failingtestcase.txt
>
> for the resulting sshd log files see:
>
> http://yz4.org/cygwin/051226/sshd_strace
> http://yz4.org/cygwin/051226/sshd_test.log
Does the strace log hint at a solution? Is there any other
test I might try that would help you debug this?
--
I'm not convinced the remote command is being invoked.
Here is an informal test I ran on my home PC on 12/27 after 10pm:
$ uname -a
CYGWIN_NT-5.0 argon 1.5.19s(0.149/4/2) 20051227 16:45:51 i686 unknown unknown Cygwin
$ ls -lu /bin/echo #last access time
-rwxrwxrwx 1 Administrator Users 18944 Dec 27 04:05 /bin/echo*
$ ssh localhost -l adm_tsr '/bin/echo hi'
adm_tsr@localhost's password:
$ : nothing echoed - the problem!
$ ls -lu /bin/echo # next line shows /bin/echo was not read in ssh session
-rwxrwxrwx 1 Administrator Users 18944 Dec 27 04:05 /bin/echo*
$ /bin/echo xx #force read now
xx
$ ls -lu /bin/echo
-rwxrwxrwx 1 Administrator Users 18944 Dec 27 22:51 /bin/echo*
$
So the ssh session silently dies before the remote '/bin/echo'
command runs?
--
thanks,
Tom
--
BTW, I just re-ran the test, and found ssh exits w/status 0.
--
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/