From owner-freebsd-current Sun Nov 14 6:26:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 6855014CFB; Sun, 14 Nov 1999 06:26:33 -0800 (PST) (envelope-from mb@imp.ch) Received: from mephisto.imp.ch (mb@mephisto.imp.ch [157.161.1.22]) by mail.imp.ch (8.9.3/8.9.3) with ESMTP id PAA01575; Sun, 14 Nov 1999 15:26:24 +0100 (MET) Received: from localhost (mb@localhost) by mephisto.imp.ch (8.9.3/8.9.3) with ESMTP id PAA18125; Sun, 14 Nov 1999 15:26:17 +0100 (MEZ) Date: Sun, 14 Nov 1999 15:26:16 +0100 From: Martin Blapp To: current@freebsd.org Cc: hackers@freebsd.org Subject: Call for objections Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi everbody, I had a concept to solve some bad implemented NFS part: The client unmount notification of the NFS server. There seems to be different understanding if the programm rpc.umntall should be started at shutdown, startup or both. Can you please vote for or against these three possibilitys ? Someone also had the idea to use a counter 'n' for trying only 'n' times to send a unmount request to the server and then to delete the entry. If we start rpc.umntall at startup-time as the RFC 1813 proposes, we have to save/store all nfs mounts in a list. This may also be some point to discuss. To get an idea you'll have to read the following URL's. my announcement: ---------------- http://docs.FreeBSD.org/cgi/getmsg.cgi?fetch=243597+0+archive/1999/freebsd-hackers/19991114.freebsd-hackers the patches/programm itself: ---------------------------- http://www.attic.ch/patches/rpc.umntall/ this PR: -------- http://www.freebsd.org/cgi/query-pr.cgi?pr=14709 Thank you very much Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message