Re: cygrunsrv + sshd + rsync = 20 times too slow -- throttled?

On 8/28/2021 11:43 AM, Takashi Yano via Cygwin wrote: On Sat, 28 Aug 2021 13:58:08 +0200 Corinna Vinschen wrote: On Aug 28 18:41, Takashi Yano via Cygwin wrote: On Sat, 28 Aug 2021 10:43:27 +0200 Corinna Vinschen wrote: On Aug 28 02:21, Takashi Yano via Cygwin wrote: On Fri, 27 Aug 2021

Re: updatedb broken as of findutils 4.8.0-1 due to bigram.exe no longer being provided

On 8/28/2021 9:15 AM, Dan Harkless wrote: [...] Sorry for the Webmail-mangled spacing in that last message. Trying again here: Howdy.  Quick bug to report that I was surprised not to be able to find prior discussion of.  My nightly updatedb job stopped working after 2021-08-03, but I'd been

updatedb broken as of findutils 4.8.0-1 due to bigram.exe no longer being provided

Howdy.  Quick bug to report that I was surprised not to be able to find prior discussion of.  My nightly updatedb job stopped working after 2021-08-03, but I'd been too busy to do much troubleshooting until today. Looks like it's because in findutils 4.8.0-1, the bigram.exe program is no longer

Re: cygrunsrv + sshd + rsync = 20 times too slow -- throttled?

On Sat, 28 Aug 2021 13:58:08 +0200 Corinna Vinschen wrote: > On Aug 28 18:41, Takashi Yano via Cygwin wrote: > > On Sat, 28 Aug 2021 10:43:27 +0200 > > Corinna Vinschen wrote: > > > On Aug 28 02:21, Takashi Yano via Cygwin wrote: > > > > On Fri, 27 Aug 2021 12:00:50 -0400 > > > > Ken Brown wrote:

Re: cygrunsrv + sshd + rsync = 20 times too slow -- throttled?

On 8/28/2021 4:43 AM, Corinna Vinschen via Cygwin wrote: On Aug 28 02:21, Takashi Yano via Cygwin wrote: On Fri, 27 Aug 2021 12:00:50 -0400 Ken Brown wrote: Two years ago I thought I needed nt_create to avoid problems when calling set_pipe_non_blocking. Are you saying that's not an issue? Is

Re: cygrunsrv + sshd + rsync = 20 times too slow -- throttled?

On Aug 28 18:41, Takashi Yano via Cygwin wrote: > On Sat, 28 Aug 2021 10:43:27 +0200 > Corinna Vinschen wrote: > > On Aug 28 02:21, Takashi Yano via Cygwin wrote: > > > On Fri, 27 Aug 2021 12:00:50 -0400 > > > Ken Brown wrote: > > > > Two years ago I thought I needed nt_create to avoid problems

Re: Is it possible to 'cygport upload' with same p-v-r?

Mark Geisert writes: > I'd like to re-spin the latest version of cygutils, that is, upload > newer files with the same release number (1.4.16-5). Is this > possible, or do we now always change the release# when uploading? Re-spin == re-release, so you need to increase the release number. Test

Re: Is it possible to 'cygport upload' with same p-v-r?

On Sat, 28 Aug 2021 at 09:09, Mark Geisert wrote: > > HI all,B > I'd like to re-spin the latest version of cygutils, that is, upload newer > files with the same release number (1.4.16-5). Is this possible, or do we > now always change the release# when uploading? > Thanks, I'm pretty sure this

Re: cygrunsrv + sshd + rsync = 20 times too slow -- throttled?

On Sat, 28 Aug 2021 10:43:27 +0200 Corinna Vinschen wrote: > On Aug 28 02:21, Takashi Yano via Cygwin wrote: > > On Fri, 27 Aug 2021 12:00:50 -0400 > > Ken Brown wrote: > > > Two years ago I thought I needed nt_create to avoid problems when calling > > > set_pipe_non_blocking. Are you saying

Re: cygrunsrv + sshd + rsync = 20 times too slow -- throttled?

On Aug 28 02:21, Takashi Yano via Cygwin wrote: > On Fri, 27 Aug 2021 12:00:50 -0400 > Ken Brown wrote: > > Two years ago I thought I needed nt_create to avoid problems when calling > > set_pipe_non_blocking. Are you saying that's not an issue? Is > > set_pipe_non_blocking unnecessary? Is

Is it possible to 'cygport upload' with same p-v-r?

HI all,B I'd like to re-spin the latest version of cygutils, that is, upload newer files with the same release number (1.4.16-5). Is this possible, or do we now always change the release# when uploading? Thanks, ..mark