From owner-freebsd-hackers Fri Feb 10 19:16:34 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id TAA21773 for hackers-outgoing; Fri, 10 Feb 1995 19:16:34 -0800 Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id TAA21767 for ; Fri, 10 Feb 1995 19:16:28 -0800 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA21637 (5.67a/IDA-1.5); Fri, 10 Feb 1995 21:06:54 -0600 Received: by bonkers.taronga.com (smail2.5p) id AA26423; 10 Feb 95 21:06:10 CST (Fri) Received: (from peter@localhost) by bonkers.taronga.com (8.6.8/8.6.6) id VAA26420; Fri, 10 Feb 1995 21:06:09 -0600 From: Peter da Silva Message-Id: <199502110306.VAA26420@bonkers.taronga.com> Subject: Re: MIT SHM X11 extensions? (fwd) To: terry@cs.weber.edu (Terry Lambert) Date: Fri, 10 Feb 1995 21:06:08 -0600 (CST) Cc: davidg@Root.COM, jmb@kryten.atinc.com, hackers@FreeBSD.org In-Reply-To: <9502110149.AA14264@cs.weber.edu> from "Terry Lambert" at Feb 10, 95 06:49:45 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1038 Sender: hackers-owner@FreeBSD.org Precedence: bulk > Mount /usr over NFS and run apps from it from the an NFS client. Paging from an executable over NFS is a problem in and of itself anyway, since NFS doesn't handle locking the executable in any way, and it doesn't even have hooks. Try opening a tmp file on a nfs mounted /tmp and use the normal "open and unlink using the open file to keep the link around" trick. I don't think the fact that NFS is fundamentally broken is a good design criterion. There's so much else that's broken on NFS anyway. Executables opened over NFS should be copied into swap. > I consider the sudden explosion of core files on the client to be an > even more suprising consequence, especially sonsidering that you can > largely ignore swap unless you actually run out. And if you suddenly copy all your running text segments to swap you may. > Realistically, you could watermark it and start randomly crashing things > at 90% swap utilization on the client instead of putting up "out of > swap messages. And you were worried about all those core files?