From owner-freebsd-hackers Sat Apr 8 8:21: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 163A937B7B2 for ; Sat, 8 Apr 2000 08:21:00 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e38FlBc26231; Sat, 8 Apr 2000 08:47:11 -0700 (PDT) Date: Sat, 8 Apr 2000 08:47:11 -0700 From: Alfred Perlstein To: Sean Peck Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD 3.3 fork/Exec bug? Message-ID: <20000408084711.W4381@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from speck@news1.newsindex.com on Sat, Apr 08, 2000 at 10:48:56AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Sean Peck [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