From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: cygrunsrv + sshd + rsync = 20 times too slow -- throttled?
Date: Sat, 4 Sep 2021 10:45:48 -0600 [thread overview]
Message-ID: <9863275d-ced3-d7e4-5a14-ba7037c39b40@SystematicSw.ab.ca> (raw)
In-Reply-To: <703C9847-7BD9-4D93-9A85-FD967423C24D@house.org>
On 2021-09-03 14:59, Chris Roehrig wrote:
> On Fri Sep 3 2021, at 12:55 PM, Corinna Vinschen wrote:
>> On Sep 2 12:03, Chris Roehrig wrote:
>>> On Thu Sep 2 2021, at 8:25 AM, Ken Brown via Cygwin wrote:
>>>> On 9/1/2021 5:11 PM, Chris Roehrig wrote:
>>>>> I rebuild procps 3.3.17.29-2480 from source and it appears to
>>>>> work, so maybe the stock procps package is incompatible with
>>>>> the current master branch.
>>>> Maybe, but it could also be a Cygwin bug. I'll do a bisection
>>>> of the Cygwin sources to see if I can track it down.
>>> I did some more tests and it still doesn't completely work:
>>> procps -ef # works
>>> procps -eo user,stime,tty,time,args # works
>>> procps -eo pid # fails with that same mmap() error
>>> I also rebuilt it all using cygport and it gives the same error
>>> (pscommand.exe with no args).
>> Since you're building Cygwin by yourself anyway, can you do me a
>> favor and try this:
>> $ git revert 2f05de4dbf9c
>> and see if that fixes your issue?
> I got procps working I think (both with and without the revert). I
> think the problem might just be that I wasn't also copying the
> rebuilt /bin/cygprocps-8.dll to match the /bin/procps.exe. There's
> some tricky renaming that make install does, so I did 'make install
> DESTDIR=/tmp/install' and copied just those two files. I'm guessing
> it would all work on a properly fully installed build.
If you are building packages in the same way as scallywag with:
$ cygport PKG.cygport download all check
then to install all binary packages for dogfooding:
$ for tar in PKG-VER-1.ARCH/dist/PKG/**/*PKG*-VER.tar.*z*
do
tar -x -C / -f $tar # * -C / installs usr/... under /usr/
done
for example, I just did:
$ for tar in \
dash-0.5.11.5-1.x86_64/dist/dash/**/*dash*-0.5.11.5-1.tar.*z*
do
tar -x -C / -f $tar
done
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2021-09-04 16:45 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 19:49 Chris Roehrig
2021-08-24 23:43 ` Mark Geisert
2021-08-25 0:35 ` Chris Roehrig
2021-08-25 2:12 ` Chris Roehrig
2021-08-25 2:02 ` NightStrike
2021-08-25 3:20 ` Mark Geisert
2021-08-25 17:24 ` Chris Roehrig
2021-08-25 11:18 ` Takashi Yano
2021-08-25 17:31 ` Chris Roehrig
2021-08-25 17:52 ` Ken Brown
2021-08-25 18:18 ` Chris Roehrig
2021-08-25 18:51 ` Chris Roehrig
2021-08-26 15:44 ` Ken Brown
2021-08-25 20:33 ` Mario Emmenlauer
2021-08-26 15:47 ` Ken Brown
2021-08-25 21:29 ` Takashi Yano
2021-08-26 15:56 ` Ken Brown
2021-08-26 22:18 ` Ken Brown
2021-08-27 11:24 ` Takashi Yano
2021-08-27 16:00 ` Ken Brown
2021-08-27 17:21 ` Takashi Yano
2021-08-28 2:00 ` Takashi Yano
2021-08-28 3:03 ` Takashi Yano
2021-08-28 8:43 ` Corinna Vinschen
2021-08-28 9:41 ` Takashi Yano
2021-08-28 11:58 ` Corinna Vinschen
2021-08-28 15:43 ` Takashi Yano
2021-08-28 20:55 ` Ken Brown
2021-08-29 8:41 ` Takashi Yano
2021-08-29 22:42 ` Ken Brown
2021-08-29 10:27 ` Corinna Vinschen
2021-08-29 9:07 ` Takashi Yano
2021-08-29 15:57 ` Ken Brown
2021-08-29 19:24 ` Chris Roehrig
2021-08-29 22:24 ` Ken Brown
2021-08-30 23:58 ` Chris Roehrig
2021-08-31 19:05 ` Ken Brown
2021-08-31 19:53 ` Chris Roehrig
2021-08-31 20:23 ` Chris Roehrig
2021-08-31 21:29 ` Brian Inglis
2021-09-01 21:11 ` Chris Roehrig
2021-09-02 15:25 ` Ken Brown
2021-09-02 19:03 ` Chris Roehrig
2021-09-03 17:26 ` Ken Brown
2021-09-03 19:55 ` Corinna Vinschen
2021-09-03 20:59 ` Chris Roehrig
2021-09-04 8:32 ` Achim Gratz
2021-09-04 16:45 ` Brian Inglis [this message]
2021-09-05 8:18 ` Achim Gratz
2021-09-05 15:11 ` Brian Inglis
2021-09-06 10:42 ` Achim Gratz
2021-09-04 22:37 ` mmap failure [was: cygrunsrv + sshd + rsync = 20 times too slow -- throttled?] Ken Brown
2021-09-04 22:54 ` Ken Brown
2021-09-04 22:58 ` Ken Brown
2021-09-05 0:04 ` Ken Brown
2021-09-05 13:24 ` Ken Brown
2021-09-06 15:32 ` Corinna Vinschen
2021-09-06 17:12 ` Ken Brown
2021-09-06 17:38 ` Ken Brown
2021-09-06 17:43 ` Eliot Moss
2021-09-06 17:59 ` Corinna Vinschen
2021-09-06 18:07 ` Corinna Vinschen
2021-09-06 18:40 ` Ken Brown
2021-09-06 20:52 ` Peter Dons Tychsen
2021-09-06 20:54 ` Peter Dons Tychsen
2021-09-06 21:24 ` Ken Brown
2021-09-06 21:31 ` Ken Brown
2021-09-07 3:34 ` Brian Inglis
2021-09-07 16:28 ` Ken Brown
2021-09-07 21:52 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-09-07 22:44 ` Ken Brown
2021-09-08 6:14 ` Sam Edge
2021-09-08 8:18 ` Corinna Vinschen
2021-09-07 21:41 ` Peter Dons Tychsen
2021-09-04 23:18 ` Brian Inglis
2021-08-29 19:37 ` cygrunsrv + sshd + rsync = 20 times too slow -- throttled? Takashi Yano
2021-08-29 21:09 ` Ken Brown
2021-08-29 21:04 ` Ken Brown
2021-08-30 0:13 ` Takashi Yano
2021-08-30 0:22 ` Takashi Yano
2021-08-30 2:15 ` Ken Brown
2021-08-30 8:02 ` Takashi Yano
2021-08-28 15:17 ` Ken Brown
2021-09-16 22:00 ` Keith Christian
2021-09-16 22:48 ` Ken Brown
2021-09-16 22:58 ` Keith Christian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9863275d-ced3-d7e4-5a14-ba7037c39b40@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).