From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <cygwin@cygwin.com>
Subject: preventing setup from forking
Date: Mon, 17 May 2021 15:59:03 -0400 [thread overview]
Message-ID: <000001d74b57$17671af0$463550d0$@pdinc.us> (raw)
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.
e.g. ssh oss-cygwin-server-2019-node -l 'jenkins$' -t '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'
Any thoughts?
This is forcing me to run it interactively, as there is something that is causing it to hang, with no output.
-Jason
next reply other threads:[~2021-05-17 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 19:59 Jason Pyeron [this message]
2021-05-17 20:40 ` Jon Turney
2021-05-17 21:12 ` Jason Pyeron
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='000001d74b57$17671af0$463550d0$@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).