From owner-freebsd-current@FreeBSD.ORG  Fri Apr 19 19:11:04 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 3765BD23;
 Fri, 19 Apr 2013 19:11:04 +0000 (UTC)
 (envelope-from crodr001@gmail.com)
Received: from mail-la0-x232.google.com (mail-la0-x232.google.com
 [IPv6:2a00:1450:4010:c03::232])
 by mx1.freebsd.org (Postfix) with ESMTP id 8700417C6;
 Fri, 19 Apr 2013 19:11:03 +0000 (UTC)
Received: by mail-la0-f50.google.com with SMTP id el20so3873033lab.37
 for <multiple recipients>; Fri, 19 Apr 2013 12:11:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:x-received:sender:in-reply-to:references:date
 :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
 bh=pz/NfVkcOt+ZmgR56lxvkB2bkfr0HGgaRTAoCgZ4LiY=;
 b=scF5kVC/wsEAgoRJfjo01OJHN3xV8xqmEuiFznH6pY7p1uW4oG76dib3AtedWR0bnb
 4U/xrd7ekyBx64CA9y73H6TssQ20gwu+X3Vij157ST8gLyvAov5K6B8qlFJO5mb7eSxI
 5o055O1t+Hf+hlQmTy6I/fONmhVpvW0S8Ul26K4qpOdEmdlaPonqaOYWie6xUbQtqlj+
 aC82yXM1ZNkDKjWS8Q076gllMPzVu79lrZhJfV272O5yytqfZkA/2VROSqNpOBl71Fnr
 gpNzw247KL1v9MWmVq25dg1vpI+5437qe8OQwOWsT0+5W7Gl489HX65KmzR3nCqCgQvp
 4ilA==
MIME-Version: 1.0
X-Received: by 10.152.30.106 with SMTP id r10mr8779952lah.28.1366398662385;
 Fri, 19 Apr 2013 12:11:02 -0700 (PDT)
Sender: crodr001@gmail.com
Received: by 10.112.146.135 with HTTP; Fri, 19 Apr 2013 12:11:02 -0700 (PDT)
In-Reply-To: <1366378546.1231.4.camel@revolution.hippie.lan>
References: <CAG=rPVf7gqgz4G=56RuLjYB_mvUDSU8NJBx5t-hKTr9DSfVr-Q@mail.gmail.com>
 <CAG=rPVcwEGgU2QiFJASgkjnfznUKrqKAOG7nx5dDr9yO_fs69w@mail.gmail.com>
 <1366378546.1231.4.camel@revolution.hippie.lan>
Date: Fri, 19 Apr 2013 12:11:02 -0700
X-Google-Sender-Auth: xyYmymhHSAxNYA6cgX_NRAmKDsk
Message-ID: <CAG=rPVfxa2qxk0qTsXWtMbKG8S7UrKhLoMdEb5y1uLEzkxs_8g@mail.gmail.com>
Subject: Re: Cannot unmount nullfs in current
From: Craig Rodrigues <rodrigc@FreeBSD.org>
To: Ian Lepore <ian@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: freebsd-current Current <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2013 19:11:04 -0000

On Fri, Apr 19, 2013 at 6:35 AM, Ian Lepore <ian@freebsd.org> wrote:

>
> I worked around this kind of problem by putting a single entry
> in /usr/local/etc/gamin/gaminrc:
>
>     poll /*
>
>

That's one option.  I used a "hammer" approach, and after reading
http://people.gnome.org/~veillard/gamin/config.html,
I put this in my /usr/local/etc/gamin/gaminrc:

fsset nullfs none
fsset ufs none
fsset zfs none

I think that is supposed to turn off gamin for any nullfs, ufs, or zfs file
system. :)
It seems to work for me.

--
Craig