similar to: Large file support, mkstemp, and off_t

On Wed, 22 Mar 2023, Allen Webb wrote: > We are trying to enable large file support for everything built for > ARM on ChromeOS and openssh uses mkstemp which has a 64-bit version > for compatibility with open64. When looking into enabling the large > file support flags, I noticed: > > `void start_progress_meter(const char *, off_t, off_t *);` > > in progressmeter.h

I miss the stars when doing scp. My suggestion for progressmeter.c makes scp to display different fields on different terminal widths. Maybe this is useful for you. Once in "start_progress_meter()" the outlook of the progressline is calculated. In "draw_progress_meter()" sprintf() instead of snprintf() together with some strlen()'s can be used, because the buffersize has

Hello All, Attached is a patch against the portable openssh sources found at openssh at anoncvs.at.openbsd.org:/cvs. The majority of the size of the patch comes from changes to the build system to supply the required format specifications if they are not provided by the OS. These patches remove the following warnings found during a 64-bit compile: hostfile.c: In function

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

http://bugzilla.mindrot.org/show_bug.cgi?id=842 ------- Comment #2 from djm at mindrot.org 2005-11-06 03:51 ------- Is this still relevant? What compile warnings do you see? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

Hi, I used scp in some background process for transferring large files which took some hours. For this I needed a less fancy output, preferable parseble by a script, so I could regularly see how far the transfer was The adaptions I made to progressmeter.c and .h are underneath my mail as a patch Some sample output how it looks now: :~/src/openssh-5.3p1$ ./scp -l 60000 test.bin hans at

Hi, Martijn sent the following patch to me in private and agreed that i post it here. In any other program in OpenBSD base, i'd probably agree with the basic approach. Regarding OpenSSH, however, i worry whether wcwidth(3) can be used. While wcwidth(3) is POSIX, it is not ISO C. Does OpenSSH target platforms that don't provide wcwidth(3)? If so, do you think the problem can be solved

This is a small patch to progressmeter.c that provides peak throughput information. It adds a new field on the progress bar line that displays the 1sec throughput for the connection. At the end of the transfer it spits out the peak throughput seen. I found it useful in some testing situations and maybe someone else might find it handy. --- ../openssh-4.7p1.logging_features/progressmeter.c

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..

http://bugzilla.mindrot.org/show_bug.cgi?id=842 Summary: type fixes for progressmeter Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sftp AssignedTo: openssh-bugs at mindrot.org ReportedBy: dtucker at zip.com.au

http://bugzilla.mindrot.org/show_bug.cgi?id=842 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #1287| |ok? Flag| | --- Comment #4 from Damien Miller <djm at mindrot.org>

On 07/10/2014 06:43 PM, Peter De Schrijver wrote: > On Thu, Jul 10, 2014 at 09:34:34AM +0200, Alexandre Courbot wrote: >> This series adds support for reclocking on GK20A. The first two patches touch >> the clock subsystem to allow GK20A to operate, by making the presence of the >> thermal and voltage devices optional, and allowing pstates to be provided >> directly

https://bugzilla.samba.org/show_bug.cgi?id=1536 ------- Additional Comments From wayned@samba.org 2004-07-30 13:30 ------- Created an attachment (id=589) --> (https://bugzilla.samba.org/attachment.cgi?id=589&action=view) Add checks for open64 and mkstemp64 to configure If the user's system has open64() but not mkstemp64(), we avoid using mkstemp(). -- Configure bugmail:

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()

Hi all, I'm running rsync version 2.6.3 protocol version 28 on Solaris 8 and am having a problem. We have some scripts that wrap around rsync and generate a list of files to transfer from the sending system (regardless of whether that directory exists on the receiver). I was expecting rsync to fail when transferring files with a path that doesn't exist on the receiver (in fact

http://bugzilla.mindrot.org/show_bug.cgi?id=1192 Summary: warning: comparison between signed and unsigned Product: Portable OpenSSH Version: 4.3p2 Platform: amd64 URL: http://www.openbsd.org/cgi- bin/cvsweb/src/usr.bin/ssh/scp.c.diff?r1=1.121&r2=1.122& f=h OS/Version: All

Hi Ben, On 07/11/2014 10:07 AM, Ben Skeggs wrote: > On Thu, Jul 10, 2014 at 5:34 PM, Alexandre Courbot <acourbot at nvidia.com> wrote: >> This series adds support for reclocking on GK20A. The first two patches touch >> the clock subsystem to allow GK20A to operate, by making the presence of the >> thermal and voltage devices optional, and allowing pstates to be provided

It's checked in, it seems to work, it didn't bloat the system significantly, but it makes life a lot easier... I just released klibc-0.124 with the 64-bit off_t and statfs64 changes. The API shouldn't have changed, but the ABI is now 64 bits in (hopefully) all the right places. It's probably buggy... beat me up or (better) send a patch... -hpa

I can't make R on a Solaris 9 box. Does anyone have any suggestions? Thanks in advance. <3>-> make `Makedeps' is up to date. `libbz2.a' is up to date. `Makedeps' is up to date. `libpcre.a' is up to date. `Makedeps' is up to date. `libz.a' is up to date. ../../../src/include/libintl.h is unchanged ../../../include/libintl.h is unchanged `localecharset.h'

Hi, Arvind Sudarsanam: I know some of Open64. Above all, Open64 is designed for a high performance compiler. It is now supported by AMD, HP, ICT Chinese Academy of Science, etc. and has been ported to X86, Itanium, Loongson CPU etc. And to your questions 1, Open64 already have some main optimization phases, Inline for aggressive inline opt. LNO for loop opt, WOPT for machine independent opt(