www.delorie.com/archives/browse.cgi | search |
From: | dj AT delorie DOT com (DJ Delorie) |
Subject: | Re: Odd fork behavior- W95/b16 |
23 Oct 1996 08:54:11 -0700 : | |
Sender: | daemon AT cygnus DOT com |
Approved: | cygnus DOT gnu-win32 AT cygnus DOT com |
Distribution: | cygnus |
Message-ID: | <199610231243.IAA24783.cygnus.gnu-win32@delorie.com> |
Original-To: | sos AT prospect DOT com DOT ru |
Original-CC: | gnu-win32 AT cygnus DOT com, moskewcz AT princeton DOT edu, noer AT cygnus DOT com |
In-reply-to: | <01BBC0CB.45A13EF0@d12.z194-58-227.relcom.ru> (message from |
Sergey Okhapkin on Wed, 23 Oct 1996 10: 16:34 +0300) | |
Original-Sender: | owner-gnu-win32 AT cygnus DOT com |
> Start your program with full qualified path > (/home/local/etc/httpd/src/httpd). There is a small bug in cygwin code - > fork tries to run program, specified in argv[0], and, if program changed > current directory before fork, fork() fails. For example, in I discovered that, in some cases, you must provide the drive letter also: d:\www\httpd *My* problem with fork() is that (with apache, at least), when it calls fork() to spawn the first child, fork() uses 100% of the CPU and never returns. - For help on using this list, send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |