public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: dboyd2@mmm.com (J. David Boyd)
To: cygwin@cygwin.com
Subject: Rebase, Peflags, and cygserver
Date: Fri, 27 Mar 2015 15:17:00 -0000	[thread overview]
Message-ID: <gjubpp7uy0nm.fsf@W0144758.usac.mmm.com> (raw)


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?

What I'm doing (with some success)is this:

1. get latest cygwin update
2. del /etc/rebase*
3. rebaseall -v
4. peflagsall -v
5. don't restart cygserver (This means my bash shell window starts a little
slower, but I can live with that.)

I usually have to do this 2 to 3 times before I can get emacs to start without
vfork errors.

Any ideas how I can improve on this? I would like to have cygserver running.

Also, I often run Cygwin Setup (to get something I've missed, like wget..., or
check for updates) while emacs is running.  Should I shut it down first?


Dave in Hudson, FL


--
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

             reply	other threads:[~2015-03-27 14:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 15:17 J. David Boyd [this message]
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
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=gjubpp7uy0nm.fsf@W0144758.usac.mmm.com \
    --to=dboyd2@mmm.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).