From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: Cygwin 2.6.0 Fork issue
Date: Fri, 30 Dec 2016 19:25:00 -0000 [thread overview]
Message-ID: <83a7f28d-3ad3-8f37-5a4c-2416d0121a0c@cs.umass.edu> (raw)
In-Reply-To: <CAPCR6Q0yynpzrBGbCfpDu=59NGU_v1hdCPOkNCPJOgk9pj6S7A@mail.gmail.com>
Looking at what you sent I see at least two suspicious
things:
1) SEVERAL orphaned Cygwin installations. This indicates
you may have multiple installation of Cygwin in different
places, and this can certainly lead to trouble.
2) A number of files missing from certain packages, which
(at a glance) all seemed to be under /opt or /sbin. Did
you happen to delete those hierarchies? Or is there some
reason they could not be created?
I am not quite as expert at figuring out this sort of
problem as some others on the list, so I might be barking
up the wrong tree, but these seem worthy of investigation.
One way to fix things is to remove *all* Cygwin installations
(see the installation mentioned in the cygcheck output) and
reinstall Cygwin from scratch, paying attention if any files
could not be created (the /opt and /sbin concern). There
may be simpler fixes. And of course this does not rule out
BLODA (badly behaving other programs that interfere with
Cygwin's mechanisms - often anti-virus and similar tools).
Regards - Eliot Moss
--
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:[~2016-12-30 19:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 5:37 Rashi Singhal
2016-12-08 7:17 ` Brian Inglis
2016-12-16 9:28 ` Rashi Singhal
2016-12-30 8:25 ` Rashi Singhal
2016-12-30 19:25 ` Eliot Moss [this message]
2017-01-03 8:53 Rashi Singhal
2017-01-05 4:04 ` Rashi Singhal
2017-01-05 10:17 ` Mark Geisert
2017-01-06 2:58 ` Rashi Singhal
2017-01-03 11:17 Mark Geisert
[not found] <586F5B5F.1070407@maxrnd.com>
2017-01-06 9:05 ` Mark Geisert
2017-01-06 20:34 ` René Berber
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=83a7f28d-3ad3-8f37-5a4c-2416d0121a0c@cs.umass.edu \
--to=moss@cs.umass.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).