| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1330459264.72081.YahooMailNeo@web112013.mail.gq1.yahoo.com> Date: Tue, 28 Feb 2012 12:01:04 -0800 (PST) From: Ron Chen <ron_chen_123@...oo.com> To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: inotify & NFS error I know that it is not possible (read: not technically feasible) for the inotify interface to support for NFS or other shared filesystems. However, I think it is at least useful to tell the application developer that the file is on NFS and thus return of some sort (via errno), and thus when inotify_add_watch(2) is passed with a pathname on NFS, some sort of error will return. I am one of the maintainers of Open Grid Scheduler (the official open-source Sun Grid Engine). I think having a reliable way of determining whether inotify gets events would greatly benefit applications that are commonly run in clustered environments (like Open Grid Scheduler, Grid Engine, and other HPC job schedulers). Most applications can switch back to polling when inotify is absent, but if the applications themselves do not know, then they can in the worst case sit there waiting forever. -Ron -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists