From owner-freebsd-hackers Sat Apr 8 7:31:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from news1.newsindex.com (news1.newsindex.com [209.166.166.118]) by hub.freebsd.org (Postfix) with ESMTP id 61B7A37B54C for ; Sat, 8 Apr 2000 07:31:56 -0700 (PDT) (envelope-from speck@news1.newsindex.com) Received: from localhost (speck@localhost) by news1.newsindex.com (8.8.5/8.8.5) with SMTP id KAA29721 for ; Sat, 8 Apr 2000 10:48:57 -0400 (EDT) Date: Sat, 8 Apr 2000 10:48:56 -0400 (EDT) From: Sean Peck To: freebsd-hackers@freebsd.org Subject: FreeBSD 3.3 fork/Exec bug? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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? Sean Sean Peck News Index -- The original News Only Search Engine. http://www.newsindex.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message