From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: cygwin@cygwin.com
Subject: Re: Rebase, Peflags, and cygserver
Date: Fri, 27 Mar 2015 15:48:00 -0000 [thread overview]
Message-ID: <CAK-n8j4U_+C1e4vzXS8gKVq8D9iicCVpf28SqmB6XomO4P2RsQ@mail.gmail.com> (raw)
In-Reply-To: <gjubpp7uy0nm.fsf@W0144758.usac.mmm.com>
On Fri, Mar 27, 2015 at 8:29 AM, J. David Boyd wrote:
> I keep having problems with vforks. Sometime everything is fine for days,
> then I start emacs, and get vfork errors.
>
> So I rebaseall, and peflagsall. Emacs works great. Oops, forgot to restart
> cygserver. Restart, bam, vfork errors. Or, no vfork error.
>
> It all seems so inconsistent and random. Is there some methodology I am
> missing to ensure no vforks?
I have had the same problems on and off. I'm essentially following
the steps you documented, except I do this before:
- exit all Cygwin processes. For me, this is usually just the X server
- run 'ash' from a Window Command Prompt
- rebaseall from the ash prompt.
It's been good for the last week or so. I'm afraid to reboot the computer.
- Jim
--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
--
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:[~2015-03-27 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 15:17 J. David Boyd
2015-03-27 15:27 ` Marco Atzeri
2015-03-27 19:05 ` J. David Boyd
2015-03-27 20:28 ` Marco Atzeri
2015-03-27 15:45 ` Rockefeller, Harry
2015-03-27 15:48 ` Jim Reisert AD1C [this message]
2015-03-27 20:46 ` Achim Gratz
2015-03-28 0:52 ` Ken Brown
2015-03-30 18:07 ` Rockefeller, Harry
2015-03-30 20:35 ` Marco Atzeri
2015-04-06 5:03 ` Jim Reisert AD1C
2015-04-06 16:27 ` Ken Brown
2015-04-11 9:04 ` Achim Gratz
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=CAK-n8j4U_+C1e4vzXS8gKVq8D9iicCVpf28SqmB6XomO4P2RsQ@mail.gmail.com \
--to=jjreisert@alum.mit.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).