From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from conssluserg-03.nifty.com (conssluserg-03.nifty.com [210.131.2.82]) by sourceware.org (Postfix) with ESMTPS id 1FEEE3858D34 for ; Sat, 18 Sep 2021 11:36:59 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1FEEE3858D34 Authentication-Results: sourceware.org; dmarc=fail (p=none dis=none) header.from=nifty.ne.jp Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=nifty.ne.jp Received: from Express5800-S70 (z221123.dynamic.ppp.asahi-net.or.jp [110.4.221.123]) (authenticated) by conssluserg-03.nifty.com with ESMTP id 18IBZgVq018943; Sat, 18 Sep 2021 20:35:42 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-03.nifty.com 18IBZgVq018943 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.ne.jp; s=dec2015msa; t=1631964942; bh=JyYPPuRuiExLMYzZlE9z9IWU03R7r2VoZ4Tx+UPDF2k=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=WkyKyXiAI9dasUWMzHcrPEl7KOcmJ1m/e8NXHDr8xaMbJ5IgkdYXaL1vfwJv6bSVc zZcBsg0zNsSmP+JOA/xmtfnEYYFlfxGRllbJvmZeS19gpX0bFwgWuYRT0hC7sVGxxu bNlO0AuisF43kq/rC//zAp8n61qodasoPKWh32eqoWeIVfC4MIJ6sPA5sSyH1EFHcS r6Y7Wd4a3zSVfRi6uRyfU5Pz+HBrHC6S2X4cY95XCDN9ufOF1uckG8KMHI4t4AG6tT MittgRtT0XWEOSOlqodWBtzG2UrQ9KTVIcbpWsvFfGkoAYn4T0lwFcPaSdm16CVnbZ bk+EKEBSV3tyg== X-Nifty-SrcIP: [110.4.221.123] Date: Sat, 18 Sep 2021 20:35:43 +0900 From: Takashi Yano To: cygwin-developers@cygwin.com Cc: Jon Turney Subject: Re: cygrunsrv + sshd + rsync = 20 times too slow -- throttled? Message-Id: <20210918203543.ed639fe3cfb4bd024b403612@nifty.ne.jp> In-Reply-To: <97b9f3f7-ee41-1f4a-00db-7944fb94f032@cornell.edu> References: <20210915205433.014102a9c1204687135e1417@nifty.ne.jp> <4d9e4a0d-1fb0-5fe6-5e09-27ffde8f3174@cornell.edu> <0d5488da-3238-09be-5713-2f20e374ca21@cornell.edu> <20210917050108.0427cacf58fc473c63013386@nifty.ne.jp> <20210917173130.7e62602a5ef1bb5ae952d3bb@nifty.ne.jp> <7ec3a773-a75e-23ce-e827-850443b7d832@cornell.edu> <20210918012300.3c62456e1d2091d3086d1e69@nifty.ne.jp> <20210918024358.a9c2d43d539903c360ce6d6f@nifty.ne.jp> <20210918103012.11eedd27fb81fef4ca1375f4@nifty.ne.jp> <6fb2a102-22c1-12f6-2749-39a640e6b718@cornell.edu> <1199de76-b51c-bb39-2bd0-8618e729e98a@cornell.edu> <20210918170332.2ff48fdcbfd2398614a5666f@nifty.ne.jp> <97b9f3f7-ee41-1f4a-00db-7944fb94f032@cornell.edu> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin-developers@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin core component developers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Sep 2021 11:37:03 -0000 On Sat, 18 Sep 2021 07:12:56 -0400 Ken Brown wrote: > > It seems that SIGPIPE is handled differently. I guess > > SIGPIPE is handled by SIG_IGN if the terminal started > > from xwin-xdg-menu, otherwize, it is handled by SIG_DFL. > > Yes, I remember now that the same issue came up a couple years ago: > > https://cygwin.com/pipermail/cygwin/2019-August/242060.html > > > Ah, the following patch for xwin-xdg-menu may be the > > right thing. > > > > --- execute.c.orig 2021-06-23 23:59:37.000000000 +0900 > > +++ execute.c 2021-09-18 16:53:52.144248600 +0900 > > @@ -76,6 +76,7 @@ > > { > > struct rlimit rl; > > unsigned int fd; > > + int sig; > > > > /* dup write end of pipes onto stderr and stdout */ > > close(STDOUT_FILENO); > > @@ -89,6 +90,10 @@ > > for (fd = STDERR_FILENO + 1; fd < rl.rlim_cur; fd++) > > close(fd); > > > > + /* Set all signal handlers to SIG_DFL. */ > > + for (sig = 1; sig < NSIG; sig++) > > + signal(sig, SIG_DFL); > > + > > /* Disassociate any TTYs */ > > setsid(); > > This may be unnecessarily drastic, given the analysis in my message cited above. It seems resetting handler only for SIGPIPE is enough according to the message you posted two years ago. Thanks. -- Takashi Yano