Date: Wed, 27 Apr 2016 20:17:06 +0900 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> To: freebsd-current@freebsd.org Subject: Re: RFC on a published change to FreeBSD 11 kqueue file ops. Message-ID: <20160427201706.4799798253dec4fb805f9298@dec.sakura.ne.jp> In-Reply-To: <d8be7f2b-10cb-5803-c970-199a80f351b7@freebsd.org> References: <d8be7f2b-10cb-5803-c970-199a80f351b7@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
One (two?) question(s). Any mechanism for monitoring file alternation (modify/create/rename/...) should NOT avoid unmounting filesystem. With this aspect, are these patches conforming? If not, there should be some mechanisms to stop monitoring per device / share basis. Are there some? *Imagine removable medias and network shares. Before I found some pages stating gvfs-trash is evil and began running script to stop it if running, I must shutdown my computer only for removing mounted SD card. It's not acceptable behavior for base system. On Wed, 27 Apr 2016 11:32:05 +0800 Julian Elischer <julian@freebsd.org> wrote: > the following change is sitting out at github, to add kqueue support > for more file operations: > > https://github.com/dmatveev/libinotify-kqueue/blob/master/patches > > does anyone have reasons why we shouldn't import this change. > > libinotify is now a port and could use these. > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Tomoaki AOKI junchoon@dec.sakura.ne.jp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160427201706.4799798253dec4fb805f9298>