similar to: BUG: SFTP (openssh-3.8p1) upload doubles "Uploading..." comment

we have implemented this function for 3.1p1, and have been using it in production sense may 2002. The patch has been ported to 3.7.1p2, we have been using it in 3.7.1p2 for awhile, if anyone is interested, here it is. This is the same patch David Bradford talked about on 2002-06-05 Regards, Greg Hayes diff -u -r openssh-3.7.1p2/sftp-client.c openssh-3.7.1p2_sftp/sftp-client.c ---

The included patch for openssh 3.0.2p1 implements overlapping read requests for the sftp client. It should be able to handle weird cases such as shriking files and reordered responses. This is only the first shot, and I'd be happy for any comments. I plan to implement something similar for the write path if this works out well. The maximum number of outstanding requests is quite high at

Sftp fails to correctly preserve permissions when fetching a file. It adds write permission for the owner (presumably so it can write the file). Sftp also fails to preserve the uid/gid. Added code so that if is running as root, uid and gid are preserved. patch is based on Openssh 3.4p1. *** sftp-client.c@@\main\1 Tue Oct 1 17:26:20 2002 --- sftp-client.c Tue Nov 5 10:22:52 2002

This patch is against OpenSSH 3.7.1p2 sources. It adds recursive (directory) downloading and uploading. Criticism/suggestions welcome. I would imagine the time official support is added, recursive operations will be handled on a per-command basis as a flag as opposed to a global toggle command (such as get -r)? diff -ru openssh-3.7.1p2/sftp-int.c openssh-3.7.1p2-patched/sftp-int.c ---

Again, this has been lightly tested. I think there still are a few glitchs. 1. stole progressmeter() from scp.c - clean up and simplified a little to remove the 'flag' status. It now understands how to initialize itself and how to terminate itself. Along with a malloced status bar instead of the original fix width bar. 2. removed all initialization code from scp.c for progressmeter()

This is the LAST version I plan on doing.. If I hear no feed back good or bad. Then I'll assume I've wasted my time on a feature that people whine about but don't care to try. This is against 3.0.2pX so it should be VERY easy for anyone to test. - Ben diff -ur openssh-3.0.2p1/misc.c openssh/misc.c --- openssh-3.0.2p1/misc.c Tue Jul 3 23:46:58 2001 +++ openssh/misc.c Wed Feb 6

I think my first send was eaten by elm.. Yuck I hate this programm.. Anyawys, first the disclaimer: This is barely tests, I submit this to the general population, but I will not submit this for review of rest of the OpenSSH team. Mainly because it is horrible at best. dealing with alarm() in a sane way is not fun. It does not compile clean, but works. IF anyone cares to clean it up..

Folks, I've noticed poor performance using sftp. If anyone has any advice on how to improve performance, I'd like to hear it. Test simply involved transferring a single 143MB MP3 file using defaults for all the program configs. The opensshd 3.0.2p1 server is used in all tests. Software: openssh suite 3.0.2p1 psftp (putty sftp client) latest dev snapshot pscp (putty scp client) latest

I saw several questions regarding 'resume transfer' support in sftp come up, in the archives, but no real satisfying answer. I had a particular itch myself, so I scratched it with a quick hack. Patch attached, since it's not really big. To explain, I need to use ssh (scp or sftp) to transfer files to and from a Windows box. No other method is available. And the Windows machine has no

On Tue, 13 May 2025, Graziano Stefani (Nokia) via openssh-unix-dev wrote: > Hi, > > With reference to the latest version of the portable OpenSSH, in > file sftp-client.c, it looks to me there may be a bug in function > sftp_upload. > > My understanding is that, when variable "len" is equal to 0, no more > SSH_FXP_WRITE messages are sent out and you start draining

Hi, List! I have a problem with rsync. I was trying to synchronize directory trees on 2 servers and got following error: multiplexing overflow 101:7104843 [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(809) Complete rsync's output: > /usr/local/bin/rsync -avzp user@host:remote_path local_path receiving file list ... done ./ DelphiStudio7.rar

I've finally took the time to figure the last few bugs (that I know of). This patch will be submit to be included in a few weeks. This patch should be generic enough for portable without too much hassle. This patch mimics OpenBSD's ftp behavior. I'm not sure like that (e.g. it doesn't put / at the end of directories by default), but that is more a question for the community

Hi. Whenever I notice a typo someplace, I fix it in a local "typo tree". Attached is 2 patches from that tree, one against OpenBSD and the other against Portable. Is it worth fixing these? -Daz. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience

I found some time in the past week to work on a simple test app that would hopefully help to answer a few questions that came up recently: 1. Can a single-process generator+receiver work well? (Looks good so far, but I haven't run any multi-processor timing tests yet.) 2. How easy is it to use librsync? (Pretty easy.) 3. How small would a transfer-only tool be? (It's currently

>From a quick look at the source code, it looks like onComplete is only called when the whole thing is done - in the case of Updater, right after the update, in the case of PeriodicalUpdater, right after it has been stopped. It looks like you need to pass your callback method as an ''insertion'' method in the options. This takes two parameters, the first will probably be the

https://bugzilla.mindrot.org/show_bug.cgi?id=2021 --- Comment #10 from Loganaden Velvindron <loganaden at gmail.com> --- ping :-) ? -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug.

The only call that PeriodicalUpdater will make periodically to you is the insertion call. I think of onComplete as being ''I''ve done everything I was going to do'', which for Updater is right after it''s done a single update, but for PeriodicalUpdater, it''s after it''s finished all of its updates, so you''ll only get it once for any call

Hello all, I know it''s a Prototype question, but I hope someone can tell me what I''m doing wrong (I hope Prototype gets documented soon ;-( Problem: using a onComplete callback with Ajax.PeriodicalUpdater (using scriptaculous 1.5 with Prototype 1.4) Works: function fooBar() { Element.hide(''foobar''); } new

The rms ("Regression Modeling Strategies") package has undergone a massive update. The entire list of updates is at the bottom of this note. CRAN has the update for linux and will soon have it for Windows and Mac - check http://cran.r-project.org/web/packages/rms/ for availability. This rms update relies on a major update of the Hmisc package. The most user-visible changes are:

Somehow I missed this.. this file is no longer in use by taskomatic. Signed-off-by: Ian Main <imain at redhat.com> --- src/task-omatic/utils.rb | 221 ---------------------------------------------- 1 files changed, 0 insertions(+), 221 deletions(-) delete mode 100644 src/task-omatic/utils.rb diff --git a/src/task-omatic/utils.rb b/src/task-omatic/utils.rb deleted file mode 100644 index