That's only some what reasonable. One would expect a perl API to work always(but it doesn't)... However the same is not true of kernel APIs, the opposite is vary much the case.
You don't call open() and then turn right around and operate on the new file handle, no you don't even do this usually in perl. The same could be true of files in proc and actually using stuff in proc is a vary bad API to begin with and perl should migrate to using another API for this. With open you test the return code and based on that you 'trust' the file handle is iether usable or not usable. The same is true of proc, you need to at the vary least see if this is a file that's executable, a simple test. I believe that every application using proc should be modified to not depend on the API, as it CAN be changed at any time. It's not supposed to be used by applications, that's why /sys was written. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1030519 Title: /proc/self/exe is not necessarily correct on overlayfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1030519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
