On Wed, 12 Mar 2014 23:52:31 +0100 David Heidelberger <david.heidelberger@xxxxxxx> wrote: > Neil, what you think? Should I try someway simplify this as Al proposed? No, Al is just letting off steam. He hates the *notify interfaces (not without reason) and wishes people would avoid them where-ever possible. However rpc_pipefs does implement these interfaces, and doesn't implement 'poll' on directories, so changing nfs-utils to use poll wouldn't help. I really don't think there is any need to do anything. It works and there is not expectation that it will every stop working, and no evidence that there is any problem with how it works. So best to leave it alone. NeilBrown > > Dne 2014-03-10 02:45, Al Viro napsal: > > On Mon, Mar 10, 2014 at 11:56:59AM +1100, NeilBrown wrote: > > > >> > I still don't understand WTF does rpc.imapd *want* either of those, TBH. > >> > >> The rpc_pipefs filesysem which is mounted on /var/lib/nfs/rpc_pipefs > >> creates > >> new channels for talking to userspace by making new pipes appear in > >> some > >> directory. Any client needs to arrange some notification for these > >> new pipes > >> appearing so that it can open them and hold a conversation over them. > >> This calls for dnotify (in gssd and idmapd) or inotify (in blkmapd). > > > > ... or just adding ->poll() to the directory in question and using the > > normal syscalls instead of all that weird crap. > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html
Attachment:
signature.asc
Description: PGP signature
