From owner-freebsd-current Wed Oct 14 06:31:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23599 for freebsd-current-outgoing; Wed, 14 Oct 1998 06:31:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23593 for ; Wed, 14 Oct 1998 06:31:22 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id JAA12813; Wed, 14 Oct 1998 09:30:34 -0400 (EDT) Date: Wed, 14 Oct 1998 09:30:34 -0400 (EDT) Message-Id: <199810141330.JAA12813@highwind.com> From: HighWind Software Information To: lists@tar.com CC: current@FreeBSD.ORG In-reply-to: <199810141315.IAA02149@ns.tar.com> (lists@tar.com) Subject: Re: Recent 3.0's are Depressing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not quite clear about what you're saying. Are you saying that your app, statically linked with a pre Sep 1 libc_r works ok on a pre Sep 1 3.0-current, but that this same statically linked app does not work on newer 3.0-current systems? Yes. That is exactly what I am saying. If so, I'd agree that recent changes to libc_r are probably not the cause of the change in behavior. Are you still doing lots of forks and execs? Yes. We are. However, we do close our file descriptors after the fork and before the exec. Could this be a aout vs ELF thing? Our binary is aout. I'm thinking about doing a fresh install of the latest 3.0 and rebuilding. I assume the latest stuff will make us produce ELF binaries. Right? -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message