From owner-freebsd-hackers Wed Feb 1 19:31:06 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id TAA11250 for hackers-outgoing; Wed, 1 Feb 1995 19:31:06 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id TAA11242; Wed, 1 Feb 1995 19:31:00 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.9/8.6.9) with SMTP id TAA10337; Wed, 1 Feb 1995 19:30:55 -0800 To: jdc@crab.xinside.com cc: jkh@FreeBSD.org (Jordan K. Hubbard), wollman@halloran-eldar.lcs.mit.edu, hackers@freefall.cdrom.com Subject: Re: Am I dreaming? In-reply-to: Your message of "Sat, 28 Jan 95 02:29:29 GMT." <199501280929.CAA16417@crab.xinside.com> Date: Wed, 01 Feb 1995 19:30:54 -0800 Message-ID: <10336.791695854@time.cdrom.com> From: "Jordan K. Hubbard" Sender: hackers-owner@FreeBSD.org Precedence: bulk > The automount daemon circumvents the same problem appearing for NFS. > Life goes on while the automounter tracks down and mounts the > required resource... It's been a while since I ran a network large > enough to justify automounting, but I don't remember any system > delays while the node was found and mounted. Would it be useful to > consider what & how the automounter achieves its' effects? Note that Actually, it sort of would since I've always *wondered* how it did that! :-) Anybody know off the top of their heads? Jordan