Are there any changes to the access control to /proc/<PID>/fd/1 in cygwin 3?
Sat Jun 15 18:28:00 GMT 2019
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
Thanks a lot in advance for any help/thoughts!
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin