public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: cygwin@cygwin.com
Subject: How does one discover a ghost path to non-exitent server
Date: Sun, 27 Nov 2022 19:37:58 -0500	[thread overview]
Message-ID: <87r0xnc3rt.fsf@local.lan> (raw)

I'm sorry my first post here is probably something that was thrashed
out here long ago.

I'm not finding the answers on goggle, even the hits that were from
this newsgroup.

I'm sure there has been plenty of pounding over time about not being
able to get a sshd server working on win 10

Running latest cygwin on win 10 I go thru the steps that begin with
  ssh-host-config -y 

I'm told at the end the server wasn't installed because there already
is one.

Neither "cygrunsrv -S" nor "net start"  know anything about it.

In an old post from this groups I found mention of there being a problem
where previous attempts to install sshd server may have left the path
but not the server.

Not really sure what the heck that might mean. Something like a cygwin
install of ssh and sshd server scouts around somewhere and finds a
path but no server and says OK, good to go.  You have the server.

It sounds kind of silly on the surface but I guess it is, in fact, a
real problem.

Cutting to the chase, can anyone tell me what can be done about such a
problem?  How can one find and erase a path that has no sshd at the
end.

Maybe I'm just misunderstanding things a bit.


             reply	other threads:[~2022-11-28  0:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28  0:37 Harry Putnam [this message]
2022-11-28  9:16 ` Andrey Repin
2022-11-29 23:54   ` Harry Putnam

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=87r0xnc3rt.fsf@local.lan \
    --to=reader@newsguy.com \
    --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).