X-Recipient:	archive-cygwin AT delorie DOT com
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=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=CogEY2rpG
	UyX78h/LE7e6y1JSLQ=; b=i78s9u9Lmub4SAF0TMVrH9b9ElC6m7CAUz3Z9NeUS
	/hqEqMQZpCMEpYbun9/zV4Gva3WHIPnbZo7/iVrfcIAj7Vv8VCk5HcBUkb+Qdj+/
	O/EvhxP+L3GvsNkpjUpkU2iSRonGR+OanNBoYcv50ru06NXla6Lk7i6DKFRFcorB
	S8=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
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
To:	cygwin AT cygwin DOT com
From:	Till Riedel <riedel AT teco DOT 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

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

- Raw text -