Date: Sat, 8 Apr 2000 08:47:11 -0700 From: Alfred Perlstein <bright@wintelcom.net> To: Sean Peck <speck@news1.newsindex.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD 3.3 fork/Exec bug? Message-ID: <20000408084711.W4381@fw.wintelcom.net> In-Reply-To: <Pine.BSI.3.95.1000408104536.29565B-100000@news1.newsindex.com>; from speck@news1.newsindex.com on Sat, Apr 08, 2000 at 10:48:56AM -0400 References: <Pine.BSI.3.95.1000408104536.29565B-100000@news1.newsindex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Sean Peck <speck@news1.newsindex.com> [000408 07:58] wrote: > > I am having a bizarre problem with a system on FreeBSD. > > The system consists of a server who forks its clients. > When the clients are forked, they try to connect to the server and get > information. Unfortunately when they fork off (fork/execlp), they say > they connected to > server and recieved nothing, yet the server does not register the > connection or request for info. If I run the client independently (not > via fork/execlp) everything works just fine. > > This code is deployed and operational on BSDi without a problem, so I > assume that this is OS related, does anyone know anything about, or can > help me with this? Without some example code to demostrate the problem there's not much we can do to address this. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000408084711.W4381>