From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3225 invoked by alias); 15 Jun 2019 18:28:01 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 3217 invoked by uid 89); 15 Jun 2019 18:28:00 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE,SPF_PASS autolearn=ham version=3.3.1 spammy=sleep, broke, HX-Spam-Relays-External:sk:!192.16, H*RU:sk:!192.16 X-HELO: scc-mailout-kit-01.scc.kit.edu Received: from scc-mailout-kit-01.scc.kit.edu (HELO scc-mailout-kit-01.scc.kit.edu) (129.13.231.81) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 15 Jun 2019 18:27:58 +0000 Received: from teco141pc.teco.kit.edu ([129.13.170.141] helo=teco141pc.teco.edu) by scc-mailout-kit-01.scc.kit.edu with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (envelope-from ) id 1hcDP8-0003Za-UR for cygwin@cygwin.com; Sat, 15 Jun 2019 20:27:56 +0200 Received: from i59f72e19.versanet.de ([89.247.46.25] helo=[192.168.178.83]) by teco141pc.teco.edu with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1hcDP8-0005r8-1o auth-from riedel for cygwin@cygwin.com; Sat, 15 Jun 2019 20:27:54 +0200 To: cygwin@cygwin.com From: Till Riedel Subject: Are there any changes to the access control to /proc//fd/1 in cygwin 3? Message-ID: Date: Sat, 15 Jun 2019 18:28:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2019-06/txt/msg00154.txt.bz2 Hi, I have been using a very handy sudo hack, that broke lately (I think) when updating cygwin: https://github.com/imachug/win-sudo The trick is to spawn an elevated process using powershell and hook up the calling file descripters. I now get "write error: Bad file descriptor" To reproduce call: powershell.exe Start-Process bash  \"-c\",\"\'echo \>\>/proc/$$/fd/1 hello world\;sleep 10\'\" IMHO this used to work in former versions (print out hello world on the calling shell). Strangely bash -c "echo >/proc/$$/fd/1 hello world" works. So my initial guess is that is has to do with the decoupling of Cygwin PIDs from Windows PIDs, but there were also changes in the proc file system... Thanks a lot in advance for any help/thoughts! BR Till -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple