Re: tramp (2.0.19); end of file during parsing on OS/390 host.

[Kai Großjohann]

Klaus-Georg Adams <address@hidden> writes:

> Wenn doing a
> C-x C-f /rsh:ihsapfc:~/
> where ihsapfc is an OS/390 machine, I eventually get the message
> End of file during parsing
> in the minibuffer.
>
> The *tramp/rsh ihsapfc* buffer is empty.
>
> -----------*debug tramp/rsh ihsapfc*------------------
> [...]
> $ test -e /net/sapmnt.home1/d034879/ 2>/dev/null; echo tramp_exit_status $? 
> tramp_exit_status 0
> # file attributes with perl: /rsh:ihsapfc:/net/sapmnt.home1/d034879/
> $ tramp_file_attributes /net/sapmnt.home1/d034879/
> -----------*debug tramp/rsh ihsapfc*------------------

Please use Tramp to open a connection like the above.  Then switch to
the *tramp/foo* buffer, erase it, and then do

M-: (process-send-string "tramp_file_attributes /net/sapmnt.home1/d034879/\n") 
RET

Also do the same but with "/" as file name.  What do you see?

(Seeing "/////" on a line by themselves is normal, that's the strange
shell prompt that Tramp uses.)

I think that Tramp found a Perl on the remote system but that this
Perl cannot execute the Perl code in tramp_file_attributes.  Maybe
you can give some information about the Perl it finds?  Type:

M-: (tramp-get-remote-perl nil "rsh" nil "ihsapfc") RET

kai
-- 
~/.signature is: umop 3p!sdn    (Frank Nobis)