From: Ron Huber <rhuber@sd.inri.com>
To: cygwin@sourceware.cygnus.com
Subject: fork errors
Date: Thu, 06 Apr 2000 13:32:00 -0000 [thread overview]
Message-ID: <3.0.32.20000406132141.0097f2d0@carrera.sd.inri.com> (raw)
Hi,
I'm using sh to run scripts to compile and build C, C++, and
Java source code on a NT 4.0. In the last month or so, I have been
getting these fork errors and the build process aborts.
Rebooting and individually running the series of scripts works.
Any idea on the cause?
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-04-06 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-06 13:32 Ron Huber [this message]
2000-04-06 14:28 Ron Huber
2000-04-07 5:28 Earnie Boyd
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
2018-04-03 23:09 ` Tatsuro MATSUOKA
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
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=3.0.32.20000406132141.0097f2d0@carrera.sd.inri.com \
--to=rhuber@sd.inri.com \
--cc=cygwin@sourceware.cygnus.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).