DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:message-id:date:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=FUC
	Pk/Ao2wDrVoL4e0927GA3Vh8dbG5cVswCBg66wYV4JIHRGEvPfvR2fNlIPjaPJBP
	08kk7B0U868R0AAfaUCtr7zYOQNpFi740Ee/R1vc5TLELfQBl4PcdGccEWSDJHpy
	71AVVV/72uPS+M9tZPJoDM+RXU4pwZU+0AEo1I+s=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: Till Riedel <riedel@teco.edu>
Subject: Are there any changes to the access control to /proc/<PID>/fd/1 in cygwin 3?
Message-ID: <a0527553-ef09-60dd-5019-7278c5f12835@teco.edu>
Date: Sat, 15 Jun 2019 20:27:52 +0200
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

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