From owner-freebsd-current@FreeBSD.ORG  Fri Apr 19 17:58:47 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id ED0BCDA0;
 Fri, 19 Apr 2013 17:58:47 +0000 (UTC)
 (envelope-from yerenkow@gmail.com)
Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com
 [209.85.220.45]) by mx1.freebsd.org (Postfix) with ESMTP id C2174B8B;
 Fri, 19 Apr 2013 17:58:47 +0000 (UTC)
Received: by mail-pa0-f45.google.com with SMTP id kl13so2409570pab.32
 for <multiple recipients>; Fri, 19 Apr 2013 10:58:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:x-received:in-reply-to:references:date:message-id
 :subject:from:to:cc:content-type;
 bh=L5MGv5O4pZ2j2f/MYhlBaZpNlfr/nP1SZTUMuRo4oHs=;
 b=N3/6hYpU9zAiwN/akrZskWoJCDBdXVXub6/oyf9KA6k5EPpygfTEUVEwZW9urY6r+m
 TbbjPGfGNKtLiVIOdlFY7t43cXKfGUIBgVB4Aau6UrxpwVmPAIYvYTidjNN9BSAvL3fO
 YLW8lYAKXi1amq8QFlsiSwU4fK0oulkdfZzJZ7B739bHdA2c1YtsYbXFXhP6y0RBL/QC
 aPqeyB6Ciht805BAIpAglOEnnxeyN8i+UO13CIawOdDJHV3PW2o4VLbiUqc4oX8tstD/
 a474ICgk1cGhxRewIoyQZixIxkq6WgwmTuDfoS9mskU5Bv+bV9OGNZjLIKacn0ei9dh0
 lOQw==
MIME-Version: 1.0
X-Received: by 10.68.184.100 with SMTP id et4mr14824314pbc.48.1366390768074;
 Fri, 19 Apr 2013 09:59:28 -0700 (PDT)
Received: by 10.68.230.233 with HTTP; Fri, 19 Apr 2013 09:59:27 -0700 (PDT)
Received: by 10.68.230.233 with HTTP; Fri, 19 Apr 2013 09:59:27 -0700 (PDT)
In-Reply-To: <5170D3C5.1080705@FreeBSD.org>
References: <CAG=rPVf7gqgz4G=56RuLjYB_mvUDSU8NJBx5t-hKTr9DSfVr-Q@mail.gmail.com>
 <5170D3C5.1080705@FreeBSD.org>
Date: Fri, 19 Apr 2013 19:59:27 +0300
Message-ID: <CAPJF9w=iSEVnXPdENket8N3T9MvCfTd7u-QkMUTHC7sjYUvaLQ@mail.gmail.com>
Subject: Re: Cannot unmount nullfs in current
From: Alexander Yerenkow <yerenkow@gmail.com>
To: Andriy Gapon <avg@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: Craig Rodrigues <rodrigc@freebsd.org>,
 freebsd-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 17:58:48 -0000

Can we pretend an user-friendly-os and spam to syslog corresponding
blocking file and process whenever umount going to fail ? :)

Like, make this to be default ( or with some key at least ) behavior of
umount.

Regards, Alexander Yerenkow