From: "Boylan, Ross" <Ross.Boylan@ucsf.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Programs become a no-op
Date: Wed, 02 May 2018 20:13:00 -0000 [thread overview]
Message-ID: <BY2PR05MB195750049C900ABAF6D78C1A87800@BY2PR05MB1957.namprd05.prod.outlook.com> (raw)
In-Reply-To: <BY2PR05MB19571396AED3AB6AD820D4BA87800@BY2PR05MB1957.namprd05.prod.outlook.com>
I've tried
ssh -V
ssh --help
ssh -v somene@somewhere
and in all cases nothing happens except that I get a new command prompt. They used to work fine.
I tried reinstalling ssh and libssh2_1. No help.
I think the problem is more general:
man ssh
man -V
man --help
man man
also all get nothing.
On the other hand, grep, find and date (date might be a shell builtin) all seem to be working fine.
I just updated; it's been at least a week since earlier updates, and it's probably longer than that since I used ssh.
Running under Windows 7, 64 bit (cygwin is 64 bit too). I have local admin rights, used for the install, but did not request them when running cygwin. Symantec EndPoint Protection, though the logs don't seem to show it blocking or quarantining anything.
Any ideas?
Thanks.
Ross Boylan
--
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 parent reply other threads:[~2018-05-02 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BY2PR05MB19571396AED3AB6AD820D4BA87800@BY2PR05MB1957.namprd05.prod.outlook.com>
2018-05-02 20:13 ` Boylan, Ross [this message]
2018-05-02 21:14 ` Marco Atzeri
2018-05-02 21:15 ` David Rothenberger
2018-05-03 13:35 ` Brian Inglis
2018-05-15 19:04 ` Programs become a no-op [SOLVED] Boylan, Ross
2018-05-02 23:44 Programs become a no-op Kaz Kylheku
2018-05-02 23:55 ` David Rothenberger
2018-05-03 5:48 ` Brian Inglis
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=BY2PR05MB195750049C900ABAF6D78C1A87800@BY2PR05MB1957.namprd05.prod.outlook.com \
--to=ross.boylan@ucsf.edu \
--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).