This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Replacing fork/exec with spawn question
- From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr at ncbi dot nlm dot nih dot gov>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Sun, 25 Nov 2012 19:51:04 +0000
- Subject: RE: Replacing fork/exec with spawn question
- References: <5561519E-4216-47A7-A020-EF2EA8E45A56@cloudwerx.com>
>In particular, the code I'm looking to patch does a typical fork/exec and uses 2 pipes to communicate bi-directionally parent to child. The
>pipes are throwing me off as to if cygwin spawn is usable.
I had no problems using fork/exec on Cygwin, even though it is mentioned to be inefficient in the documentation. If the spawn rate
of your child processes is not high, it should work just well...
--
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