X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9B9003858C2B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1682013887; bh=kbvgFLMg5HGH0zyutJbXlAxdbrY65w9/GQUeI59KVAI=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=a3WOrduku83QsKMoP30/ZXt5koKw9nSmrtfmNsxBNkevpHiklh+hiFt6WCkc7VG1m fUTLy4Wry5zpbJGwdMrmtygcMJb661B1ek8aDdXmDLvQ9uF+imAfrdBVBfd3Mby4LB xT7oa7OWgFeA32OIXfCg5i1vHzE8bCurUpVy1jMw= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 407393858C83 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-Spam-Language: en X-Spam-Relay-Country: X-Spam-DCC: B=MGTINTERNET; R=smtp1.atof.net 1170; Body=1 Fuz1=1 Fuz2=1 X-Spam-RBL: X-Spam-PYZOR: Reported 0 times. Date: Thu, 20 Apr 2023 14:04:01 -0400 To: Bruno Haible , cygwin AT cygwin DOT com Subject: Re: posix_spawn facility Message-ID: References: <1752276 DOT 7aRn1RRit1 AT nimes> <1853259 DOT CQOukoFCf9 AT nimes> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "gs-cygwin.com--- via Cygwin" Reply-To: gs-cygwin DOT com AT gluelogic DOT com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On Thu, Apr 20, 2023 at 04:40:52PM +0200, Corinna Vinschen via Cygwin wrote: > On Apr 20 16:21, Corinna Vinschen via Cygwin wrote: > > On Apr 20 12:18, Bruno Haible via Cygwin wrote: > > > The "inheritable handles" is a data structure that allows for the > > > arbitrary reshuffling of file descriptors required by posix_spawn > > > (the addopen, adddup2, addclose actions), i.e. which does the book- > > > keeping which HANDLE must in the end be open in the parent and which > > > must in the end be open in the child, and at which position. > > > > Hmm. Your code uses lpReserved2 for that, but the functionality is > > one implemented in MSVCRT. For obvious reasons, Cygwin executables > > are not linked against msvcrt.dll and we're using lpReserved2 for our > > own purposes. > > Oh, btw., did you know that there's a newer mechanism for defining > specific inheritable handles to CreateProcess, which is implemented > in kernel32.dll, so it does not depend on MSVCRT? > > There's a STARTUPINFOEX structure which allows to specify the > additional handles. See > > https://learn.microsoft.com/en-us/windows/win32/api/winbase/ns-winbase-startupinfoexa > > and the PROC_THREAD_ATTRIBUTE_HANDLE_LIST argument described in > > https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-updateprocthreadattribute An example using these to run CGI programs in lighttpd on Windows using native _WIN32 code can be seen on my dev branch (intended for lighttpd 1.4.70). https://git.lighttpd.net/lighttpd/lighttpd1.4/src/branch/personal/gstrauss/master/src/fdevent_win32.c#L539 (lighttpd is BSD-3-Clause) The aim is to securely manage which handles are inherited by child CGI processes. Elsewhere, lighttpd clears HANDLE_FLAG_INHERIT on handles lighttpd creates, and uses WSA_FLAG_NO_HANDLE_INHERIT in calls to WSASocket() func family. Also in that file, I have an (expensive) socketpair() implementation, since lighttpd uses sockets instead of pipes to connect to CGI programs, so that events can be received using WSAPoll() or select(). To get things working in native _WIN32 lighttpd, which has a test framework that runs under Cygwin, I had to detect and perform some path translation between native Windows and Cygwin paths. While my solution is specific to lighttpd's use, I hope that this may give you some ideas. Cheers, Glenn -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple