From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <cygwin@cygwin.com>
Subject: RE: preventing setup from forking
Date: Mon, 17 May 2021 17:12:51 -0400 [thread overview]
Message-ID: <003d01d74b61$65d99c30$318cd490$@pdinc.us> (raw)
In-Reply-To: <91834264-88de-d523-749e-5759ee3ac1d4@dronecode.org.uk>
> -----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!
next prev parent reply other threads:[~2021-05-17 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 19:59 Jason Pyeron
2021-05-17 20:40 ` Jon Turney
2021-05-17 21:12 ` Jason Pyeron [this message]
2021-05-18 9:13 ` Marco Atzeri
2021-05-18 20:39 ` Adam Dinwoodie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='003d01d74b61$65d99c30$318cd490$@pdinc.us' \
--to=jpyeron@pdinc.us \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).