From: Achim Gratz <Stromeko@NexGo.DE>
To: cygwin@cygwin.com
Subject: Re: Windows Server 2012R2 64bit and 32bit Cygwin sshd
Date: Tue, 02 Sep 2014 11:52:00 -0000 [thread overview]
Message-ID: <loom.20140902T134545-288@post.gmane.org> (raw)
In-Reply-To: <8761hphfps.fsf@Rainer.invalid>
Achim Gratz <Stromeko <at> nexgo.de> writes:
> - Windows Server 2012R2 64bit running on hardware
> - domain member
> - Cygwin 32bit (latest snapshot from 2014-08-31 w/ AD integration)
>
> can anybody confirm they have gotten sshd successfully running? As far
> as I can debug this, the sshd I have installed goes through all the
> motions of checking and setting up the environment, but any process it
> then spawns to actually run my command or shell immediately exits.
The server I was testing this on had to be re-installed for reasons
unrelated to Cygwin, so I've had a fresh start. The issue remains the same
however: I have successfully set up an sshd for both a productive 64bit
Cygwin and a separate 64bit build environment and can use them both in
parallel. The 32bit build environment works just fine in an RDP session,
but I can't make the 32bit sshd actually start programs. As before, it
validates the user logging in successfully and then fails to start the
program requested. The failure is the same for a local account and a domain
account and regardless of whether I try to log in from the outside or via
localhost.
Regards,
Achim.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-09-02 11:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 17:26 Achim Gratz
2014-08-19 13:37 ` Achim Gratz
2014-08-19 17:02 ` Corinna Vinschen
2014-08-19 17:21 ` Achim Gratz
2014-08-19 19:09 ` Corinna Vinschen
2014-08-19 19:21 ` Achim Gratz
2014-09-02 11:52 ` Achim Gratz [this message]
2014-09-02 14:07 ` Corinna Vinschen
2014-09-02 15:16 ` Achim Gratz
2014-09-02 15:38 ` Corinna Vinschen
2014-09-02 17:32 ` Achim Gratz
2014-09-03 7:17 ` Achim Gratz
2014-09-03 13:03 ` Achim Gratz
2014-09-03 13:37 ` Corinna Vinschen
2014-09-04 11:24 ` Achim Gratz
2014-09-04 12:28 ` Corinna Vinschen
2014-09-04 14:12 ` Achim Gratz
2014-09-04 14:59 ` Achim Gratz
2014-09-05 11:16 ` Corinna Vinschen
2014-09-05 11:56 ` Corinna Vinschen
2014-09-05 18:17 ` Achim Gratz
2014-09-03 13:26 ` Corinna Vinschen
2014-09-02 16:25 ` Achim Gratz
2014-09-02 19:14 ` Corinna Vinschen
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=loom.20140902T134545-288@post.gmane.org \
--to=stromeko@nexgo.de \
--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).