From: Stephen Carrier <carrier@berkeley.edu>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: cygwin@cygwin.com
Subject: Re: Issue with seteuid and openssh
Date: Thu, 26 May 2022 16:43:07 -0700 [thread overview]
Message-ID: <20220526234307.GB13111@iguana.crashland.org> (raw)
In-Reply-To: <877d694i25.fsf@Rainer.invalid>
On Wed, May 25, 2022 at 07:51:14PM +0200, Achim Gratz wrote:
> Check the dependencies on both the cygserver and sshd service
> definitions. You must start them after the network is up (make them
> both depend on tcp_ip and sshd depend on cygserver) or they won't work
> correctly. On domain machines that sometimes still isn't quite enough,
> so I've set them to "delayed start" in those instances and that seems to
> have fixed it.
In the 2019 occurence of a similar problem, cygserver wasn't being used,
so I would be interested and happy to hear if running it and waiting for
it are enough to fix this.
--Stephen
next prev parent reply other threads:[~2022-05-26 23:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 22:15 Dale Lobb
2022-05-25 17:51 ` Achim Gratz
2022-05-26 23:43 ` Stephen Carrier [this message]
2022-07-14 1:47 ` EXTERNAL SENDER: " Dale Lobb
2022-05-26 23:39 ` Stephen Carrier
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=20220526234307.GB13111@iguana.crashland.org \
--to=carrier@berkeley.edu \
--cc=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).