X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 458B03857C75 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=pdinc.us Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=jpyeron AT pdinc DOT us DKIM-Filter: OpenDKIM Filter v2.11.0 mail2.pdinc.us 14HLCfoM028286 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pdinc.us; s=default; t=1621285961; bh=dh5xb9oybH74hWMAWpL/BlIMw1KjNrFHNoJwys4el8k=; h=From:To:References:In-Reply-To:Subject:Date:From; b=Mqp1TKf1GVoyCUoI3UEhymF6fIlm1IuD6tLYNvOJFv/xTJocbq5tMhL0SbHAIodm7 GoKEWDZZvPzkDmx5mkqgWa4HA8qULmgbeqyfpJRsu4OJk3q2G1IC41GPBaVBevZRhq /jRCMxZwHxx4Q0vUvOu2aMTWfIKCe8DHA0nX017xManAIa1zvpyzPIBNMSx0ks/jkv RFA3GfjXvC4Pboob8iLmP+maF1kgp7XjJzlsmWYxpvudkjBH9agF1iM89CzUJNWXX3 P43QV8IPqNGfFPhaL2OvdXqn4Q7TPobCMyaFA/lgYOyRgH9kcrKXf3IwyqUESN2UOC oebgiHChu0SqA== From: "Jason Pyeron" To: References: <000001d74b57$17671af0$463550d0$@pdinc.us> <91834264-88de-d523-749e-5759ee3ac1d4 AT dronecode DOT org DOT uk> In-Reply-To: <91834264-88de-d523-749e-5759ee3ac1d4@dronecode.org.uk> Subject: RE: preventing setup from forking Date: Mon, 17 May 2021 17:12:51 -0400 Message-ID: <003d01d74b61$65d99c30$318cd490$@pdinc.us> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQJOm++Ki4AyMQbmVEScJPyU15Hb2QHxry8Dqen2/1A= Content-Language: en-us X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_INFOUSMEBIZ, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Cygwin" > -----Original Message----- > From: Jon Turney > Sent: Monday, May 17, 2021 4:41 PM > > On 17/05/2021 20:59, Jason Pyeron wrote: > > When I run > > > > c:\inst\setup-x86_64.exe -q -f -R c:\cygwin64 -l c:\inst -P libgcrypt- > devel,asciidoc,cygport,gcc-g++,libpoppler-cpp-devel,libpcre-devel,dejagnu,texlive- > collection-latex > > > > or > > > > c:\inst\setup-x86_64.exe -qvW -f -R c:\cygwin64 -l c:\inst -P libgcrypt- > devel,asciidoc,cygport,gcc-g++,libpoppler-cpp-devel,libpcre-devel,dejagnu,texlive- > collection-latex > > > > the prompt returns immediately. This is causing problems when it is run from a (windows) > ssh session. > > --wait should be doing what you want. -W is the same, no impact. > > I recently discovered that if the invoking shell is PowerShell, then > because setup is a GUI application, PowerShell doesn't wait, so maybe > that's what's happening here... > Fits my observations. https://superuser.com/questions/908664/have-the-command-prompt-launch-an-application-like-notepad-and-block-until-it-is helps. start /b /wait c:\inst\setup-x86_64.exe -q -f -R c:\cygwin64 -l c:\inst -P libgcrypt-devel,asciidoc,cygport,gcc-g++,libpoppler-cpp-devel,libpcre-devel,dejagnu,texlive-collection-latex from cmd.exe use start /b /wait /B Start application without creating a new window. The application has ^C handling ignored. Unless the application enables ^C processing, ^Break is the only way to interrupt the application. /WAIT Start application and wait for it to terminate. My real issue was the user was not an admin - doh! -- 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