From owner-freebsd-stable Wed May 30 2:36:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wit379119.student.utwente.nl (wit379119.student.utwente.nl [130.89.232.129]) by hub.freebsd.org (Postfix) with ESMTP id 1155637B423 for ; Wed, 30 May 2001 02:36:26 -0700 (PDT) (envelope-from niek@wit379119.student.utwente.nl) Received: by wit379119.student.utwente.nl (Postfix, from userid 1000) id 545D65D44; Wed, 30 May 2001 10:35:58 +0200 (CEST) Date: Wed, 30 May 2001 10:35:58 +0200 From: Niek Bergboer To: freebsd-stable@freebsd.org Subject: Re: smbfs: disconnected servers Message-ID: <20010530103558.A31220@wit379119.student.utwente.nl> Reply-To: niek@bergboer.net References: <20010528142059.A703@kirk.sector14.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010528142059.A703@kirk.sector14.net>; from dgl@visi.com on Mon, May 28, 2001 at 02:20:59PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, On Mon, May 28, 2001 at 02:20:59PM -0400, Doug Lee wrote: > I just cvsuped to 4.3-STABLE (from 4.2-STABLE) and did make > buildworld, make buildkernel, make installkernel, and make > installworld. During the buildkernel, I realized I wanted to make > some changes to my kernel config file; so I did, then aborted and > started over the buildkernel. No errors. Now that some changes to smbfs have been MFC'ed, there still is an open issue concerning smbfs: I'm using FreeBSD (4.3-STABLE for that matter) on a large campus network of over 2000 computers that are personal systems of students themselves. If I use mount_smbfs to mount a share on these systems, this works perfectly. However, the problems begin when somebody whose share I mounted decides to switch off his computer: I (obviously) cannot read from the mountpoint anymore, but there also is _no way_ of forcefully unmounting the share anymore. One might say that this is logical since there is no way to communicate a decent "logoff" packet to the (now switched off) server. However, I'm left with a dead mountpoint that doesn't respond to anyting anymore and cannot be unmounted. How difficult (and desirable) would it be to implement either one of the following two options in smbfs: 1. The ability to reconnect to a server: suppose a server switches off, and switches on again the following day. 2. The ability to forcefully unmount the share on my local machine, to such an extent that if the server cannot be contacten within a specified amount of time, that the entry is bluntly deleted from the kernel's internal list of mounted filesystems (or something along those lines). Any ideas (and yes, it might have been better to put this on -hackers, but feel free to reply to -hackers). Niek -- Conscience doth make cowards of us all. -- Shakespeare To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message