public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: problem with fork() and temp dlls
Date: Thu, 28 Jun 2012 14:55:00 -0000	[thread overview]
Message-ID: <4FEC7030.7020702@cygwin.com> (raw)
In-Reply-To: <24473_1340874479_4FEC1EEF_24473_587_1_B03025C959FD1A4796D42DC68C9C0823046C64DC@wancyexmbx01.ancy.fr.sopra>

On 6/28/2012 5:08 AM, Lenci Damien wrote:
> Hello,
>
> I am currently trying to port Nagios on Cygwin and I'm having a issue (among others ^^) when trying to use modules.
> Here is how Nagios loads modules :
>
> - Create a temporary file using mkstemp()
> - Copy module into this temp file
> - Load module from temp file with dlopen()
> - Delete temp file (on startup, not when nagios process is terminated)
>
> Here is the problem message :
>
> 0 [main] nagios 3624 child_info_fork::abort: unable to map XXXXXXXX\var\nagios\spool\checkresults\nebmodE56bUw, Win32 error 126
>
> Sometimes return code(I think this is the return code) is 1 :
>
> 1 [main] nagios 2364 child_info_fork::abort: unable to map XXXXXXXX\var\nagios\spool\checkresults\nebmodE56bUw, Win32 error 126

Looks like fork problems to me.  Perhaps you need to rebase the DLLs you're
building?  See the link below for more info:

    <http://cygwin.com/faq-nochunks.html#faq.using.fixing-fork-failures>

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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:[~2012-06-28 14:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28  9:08 Lenci Damien
2012-06-28 14:55 ` Larry Hall (Cygwin) [this message]
2012-06-29  9:57 Lenci Damien
2012-06-29 10:16 ` marco atzeri
2012-06-29 12:08 Lenci Damien
2012-06-29 15:36 ` marco atzeri

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=4FEC7030.7020702@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.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).