In response to your original email, if lftp backgrounds, the crude way of stopping it is "killall lftp".
If you'd rather lftp didn't background in the first place, I recommend adding "set cmd:move-background no" to ~/.lftp/rc You seem to indicate the traffic continues even if the lftp process has been killed? First of all, I think "ps -ef | grep fxp" isn't the best command. You should be grepping for lftp, not fxp (you won't necessarily always have "fxp" in your lftp commands) . Even if you manage to kill lftp, I'm not sure that you can stop the transfer from your computer because the two servers independently negotiate the tcp transfer. But I'm not too familiar with the details of fxp. If lftp changes to "[Receiving data->Sending data]" it probably means one or both of the servers don't allow fxp. lftp must then route the traffic through you're connection to make it work. Talk to the server admins to get fxp enabled. 2010/2/16 José Romildo Malaquias <[email protected]>:seems to be finished, the traffic continues and "ps -ef | grep fxp" does > On Tue, Feb 16, 2010 at 12:15:37PM -0200, José Romildo Malaquias wrote: >> Hello. >> >> I have started using lftp a few days ago. I am using it to transfer some >> files from one ftp server to another ftp server using the fxp protocol, >> with a command like the following in a terminal: >> >> $ lftp -c "mirror --verbose=3 --log=fxp.log -c >> ftp://user1:pass...@host1:port1/path1/file >> ftp://user2:pass...@host2:port2/path2/"; > > I have another question in this context: > > Why sometimes lftp changes to "[Receiving data->Sending data]". Clearly it > stopped doing fxp, as traffic is going through my local computer. > > It is not enough to stop the command with control+c, as even after lftp > seems to be finished, the traffic continues and "ps -ef | grep fxp" does > not show a lftp process. > > So what is the best way of interrupting the ftp traffic in my local > computer in this case? > > Romildo >
