On Mon, Jan 21, 2008 at 03:07:11PM +0300, Alexander V. Lukyanov wrote: > On Sat, Jan 19, 2008 at 02:58:11AM +0000, Charlie Allom wrote: > > lftp [EMAIL PROTECTED]:~> rm TEST.wav > > ---- path on wire is `TEST.wav' > > ---> sending a packet, length=17, type=13(REMOVE), id=7 > > <--- got a packet, length=33, type=101(STATUS), id=7 > > rm: Access failed: File not found (TEST.wav) > > > debug2: Sending SSH2_FXP_REMOVE "/Usr/ciuser01/TEST.wav" > > The difference is that plain sftp sends complete path, while lftp sends > home-relative path. AFAIK sftp protocol should treat paths without a > leading slash as home-relative, probably this particular sftp server > violates the rule. So I have to add a setting to always include full path > on the wire.
this works. thanks lftp [EMAIL PROTECTED]:~> rm TEST.wav ---- Running connect program (ssh -a -x -s -l ciuser01 -p 991 x.x.x.x sftp) ---> sending a packet, length=5, type=1(INIT), id=0 <--- GlobalSCAPE Secure FTP [EMAIL PROTECTED]'s password: XXXX <--- got a packet, length=5, type=2(VERSION), id=0 ---- protocol version set to 3 ---- path on wire is `TEST.wav' ---> sending a packet, length=17, type=13(REMOVE), id=1 <--- got a packet, length=33, type=101(STATUS), id=1 rm: Access failed: File not found (TEST.wav) lftp [EMAIL PROTECTED]:~> set sftp:use-full-path yes lftp [EMAIL PROTECTED]:~> rm TEST.wav ---- path on wire is `/Usr/ciuser01/TEST.wav' ---> sending a packet, length=31, type=13(REMOVE), id=2 <--- got a packet, length=21, type=101(STATUS), id=2 rm ok, `TEST.wav' removed lftp [EMAIL PROTECTED]:~> -- http://devblog.playlouder.com/
