public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Simon Matthews <simon.d.matthews@gmail.com>
To: cygwin@cygwin.com
Subject: Re: fork errors
Date: Wed, 04 Apr 2018 05:28:00 -0000	[thread overview]
Message-ID: <CAEUYfyPSxpW7+aDSmXs6+R53+3LuFrckfSkjthC92PrZyoZS6g@mail.gmail.com> (raw)
In-Reply-To: <CAEUYfyOfVNy1QRgowCOEny+qS+yA-OQ1MN8-MKESi_B8DL=djw@mail.gmail.com>

To clarify, I don't see the fork errors in the Son-Of-Grid Engine
(SOGE) process. Separately, we have a script that connects to the box
via ssh under cygwin and runs a lot of Make,  bash and perl scripts
and calls Windows executables. It's these scripts that are giving the
fork errors. The intent is to replace the ssh, Make and scripts with a
simpler set of scripts and processes controlled via the Gridengine.

Simon


On Tue, Apr 3, 2018 at 8:06 PM, Simon Matthews
<simon.d.matthews@gmail.com> wrote:
> Jurgen,
>
> No anti-virus at all on this machine.
>
> The daemon is Son-of-Grid Engine execd.
>
> It waits for instructions to run scripts from the qmaster.
>
> Simon
>
> On Tue, Apr 3, 2018 at 2:12 PM, Jürgen Wagner <juergen@wagner.is> wrote:
>> Simon,
>>   chances are this has nothing to do with rebasing but rather with the
>> anti-virus product on your system.
>> Do you happen to use Comodo CIS? Without proper configuration, Cygwin
>> will show such fork fails in some situations.
>>
>> Cheers,
>> --J.
>>
>> On 03/04/2018 17:20, Simon Matthews wrote:
>>>> I have been seeing a large number of error messages like this:
>>>> 2 [main] bash 8652 fork: child -1 - forked process 7532 died
>>>> unexpectedly, retry 0, exit code 0xC0000005, errno 11
>>>> 2 [main] bash 8652 fork: child -1 - forked process 7532 died
>>>> unexpectedly, retry 0, exit code 0xC0000005, errno 11
>>>>
>>>> [...]
>>
>>

--
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:[~2018-04-04  5:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-03 15:20 Simon Matthews
2018-04-03 20:40 ` Marco Atzeri
2018-04-03 21:12   ` Jürgen Wagner
2018-04-04  3:06     ` Simon Matthews
2018-04-04  5:28       ` Simon Matthews [this message]
2018-04-03 23:09 ` Tatsuro MATSUOKA
  -- strict thread matches above, loose matches on Subject: below --
2023-09-06 18:51 Fork errors Dale Lobb
2023-09-06 21:00 ` Jose Isaias Cabrera
2023-09-06 21:03   ` Jose Isaias Cabrera
2023-09-06 23:32 ` Mark Geisert
2023-09-07 15:20   ` Bill Stewart
2023-09-08  5:02     ` Mark Geisert
2000-04-07  5:28 fork errors Earnie Boyd
2000-04-06 14:28 Ron Huber
2000-04-06 13:32 Ron Huber

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=CAEUYfyPSxpW7+aDSmXs6+R53+3LuFrckfSkjthC92PrZyoZS6g@mail.gmail.com \
    --to=simon.d.matthews@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).