From owner-freebsd-rc@FreeBSD.ORG Sun Dec 16 09:15:16 2012 Return-Path: Delivered-To: rc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A75743E1 for ; Sun, 16 Dec 2012 09:15:16 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 27F6D8FC12 for ; Sun, 16 Dec 2012 09:15:15 +0000 (UTC) Received: by mail-bk0-f54.google.com with SMTP id je9so2225262bkc.13 for ; Sun, 16 Dec 2012 01:15:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=d2d88tbQEULhikgO/hkNt7Xh+E5efHbwmIawIvjUhhc=; b=sSoedHDbx4ruOp8JgM3MYDqWosjWJbO4Dth3fIhD0sUzPS/mCGnZ5ObqQQUhbWo+o7 4hHmztzIRos1D/SO81in5/kJdlgQYADvuTfhEYhrfGB2gqnLPefDGP7Ij7Ud1T7w5oFF L+MU6OXLxFvWuOObn7smhFFuz3CSYCFCUz218W7JqoWPaae6RzlFyoFnbzHpNj6wUMjN g/Q/DQrQVppfcwdLGYE9JMlk00PlIOBdjWXupQpesPG6jmktmnXa/nb5V7x5h9k0uFbY Bqox+rqMAZs2fFqHGQTOlOL0vGJ1M3dsJRUZ1sqR+u6Cay/3qzStiqZQJjSJiW74qUWv DZUg== MIME-Version: 1.0 Received: by 10.204.143.147 with SMTP id v19mr4529515bku.32.1355649309240; Sun, 16 Dec 2012 01:15:09 -0800 (PST) Received: by 10.204.167.71 with HTTP; Sun, 16 Dec 2012 01:15:08 -0800 (PST) Received: by 10.204.167.71 with HTTP; Sun, 16 Dec 2012 01:15:08 -0800 (PST) In-Reply-To: <20121216044802.GX71906@kib.kiev.ua> References: <6A58ADA440454E5889DBA6D2D9C56180@multiplay.co.uk> <20121215091424.GS71906@kib.kiev.ua> <1F93E0D525B946B88405EC4203385E0A@multiplay.co.uk> <20121216044802.GX71906@kib.kiev.ua> Date: Sun, 16 Dec 2012 09:15:08 +0000 Message-ID: Subject: Re: Adding dependency on mountlate to mountd From: Chris Rees To: Kostik Belousov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-rc@freebsd.org" , Steven Hartland X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Dec 2012 09:15:16 -0000 On 16 Dec 2012 04:48, "Konstantin Belousov" wrote: > > On Sat, Dec 15, 2012 at 10:12:00PM +0000, Chris Rees wrote: > > On 15 December 2012 20:09, Steven Hartland wrote: > > > ---- Original Message ----- > > >> > > >> From: Chris Rees On 15 Dec 2012 09:14, "Konstantin Belousov" > > >> wrote: > > >> > It cannot be fine. It breaks local NFS mounts. > > >> > > >> Given that we can't have both, but we can have nullfs and thus solve this > > >> problem. > > >> Is there something that local NFS mounts can do that nullfs won't? > > > > > > > > > Using local NFS mounts seems a bit of strange thing to do, whats the > > > reason for the requirement for these? > > > > > > Wouldnt nullfs mounts replace this requirement and perform better? > No, because there are different use cases. What was useful for me was > the case of migrating services, when the client machine happens to be > the same as the export one. Ability to do loopback nfs mounts removes > the need for non-trivial reconfiguration. > > > > > > Here's an idea, how about in the mountlate script, we pass SIGHUP to > > mountd at the end (or simply restart it, but that'd be slower)? This > > would cover your use case and Kostik's example too. > > The mount(8) already sends SIGHUP to mountd, it is even noted in the > man. Sometimes it results in the quite puzzling behaviour, see e.g. > r172577, which in fact was blamed on a bug in our TCP stack. > > The only case which could not be covered yet is the unability to specify > export points in the exports(5) which only appear after some late > mounts are performed. I think that if you really concerned with this, a > flag to the mountd(8) might be added which allows the daemon to ignore > non-existing export directories. That's a great idea. Steven, would you accept that as a solution? Chris