Date: Fri, 19 Apr 2013 19:59:27 +0300 From: Alexander Yerenkow <yerenkow@gmail.com> To: Andriy Gapon <avg@freebsd.org> Cc: Craig Rodrigues <rodrigc@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: Cannot unmount nullfs in current Message-ID: <CAPJF9w=iSEVnXPdENket8N3T9MvCfTd7u-QkMUTHC7sjYUvaLQ@mail.gmail.com> In-Reply-To: <5170D3C5.1080705@FreeBSD.org> References: <CAG=rPVf7gqgz4G=56RuLjYB_mvUDSU8NJBx5t-hKTr9DSfVr-Q@mail.gmail.com> <5170D3C5.1080705@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPJF9w=iSEVnXPdENket8N3T9MvCfTd7u-QkMUTHC7sjYUvaLQ>