public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Rebase, Peflags, and cygserver
Date: Fri, 27 Mar 2015 20:28:00 -0000	[thread overview]
Message-ID: <5515B6BF.6000302@gmail.com> (raw)
In-Reply-To: <gjub619m4al2.fsf@W0144758.usac.mmm.com>

On 3/27/2015 6:24 PM, J. David Boyd wrote:
> Marco Atzeri writes:
>
>> On 3/27/2015 3:29 PM, 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?
>>>
>>> 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?
>>
>> yes.
>> Never update with cygwin processes running
>>
>>> Dave in Hudson, FL
>>
>> could you start with
>>> Problem reports:       http://cygwin.com/problems.html
>>
>> specially this point:
>>
>> "Run cygcheck -s -v -r > cygcheck.out and include that file as an
>> attachment in your report. Please do not compress or otherwise encode
>> the output. Just attach it as a straight text file so that it can be
>> easily viewed"
>>
>> so we can look on your setup ?
>>
>> I am not seeing a lot of fork issues, on my system.
>> Eventually you have some BLODA interfering.
>>
>> Regards
>> Marco
>>
>>
>>
>> Regards
>> Marco
>
>
> It's quite long, but here you go...

It is for this reason that it should be attached to the mail
as allegate. Not in line with the text.

> Found: C:\tools\cygwin\usr\local\bin\bash
> Found: C:\tools\cygwin\bin\bash.exe
> Warning: C:\tools\cygwin\usr\local\bin\bash hides C:\tools\cygwin\bin\bash.exe
>   -> C:\tools\cygwin\bin\bash

why do you need a different bash in /usr/loca/bin ?


> Missing directory: /usr/share/emacs/24.4/lisp/org/ from package emacs
> Missing file: /usr/share/emacs/24.4/lisp/org/ob-asymptote.elc from package emacs
[cut]
> Missing file: /usr/share/info/org.info.gz from package emacs
> emacs                                 24.4-3                     Incomplete
> Missing directory: /usr/share/emacs/24.4/lisp/org/ from package emacs-el
[cut]
> Missing file: /usr/share/emacs/24.4/lisp/org/ox.el.gz from package emacs-el
> emacs-el                              24.4-3                     Incomplete


Are you sure that emacs is fully working ?
It seems a large chunk is missing. I suggest to re-install.

Regards
Marco



--
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 20:00 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 [this message]
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=5515B6BF.6000302@gmail.com \
    --to=marco.atzeri@gmail.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).