@Jeff, I looked at the lkml thread and it appears that the questioner wanted a use case to understand the reason for the change. This appears reasonable so long as two issues can be addressed:
1. Are these all the points of interest for atime or are there other input drivers not used by condor but in the same class? 2. The question was directed to the use model. How is this used? Do they stat the fd or ??? Is polling of this information going on? If it is "polling" what is the interval an if not, how do you handle the event? What are the alternatives and why are they worse? These are the questions that would have to be answered to get the patch upstream. Extra lines of code, even just a few lines, for a small use case that gets executed by everybody will have a harder time getting accepted. Ubuntu, for the same reasons, would have the same criteria which is why we almost always only accept patches via upstream. -- enable atime on input devices https://bugs.launchpad.net/bugs/391318 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
