20 Sep
2017
20 Sep
'17
12:03 a.m.
On Tue, Sep 19, 2017, at 10:42, Larry McVoy wrote:
slib.c:1653 (bk-7.3): open failed: permission denied
which is way way way more useful than just permission denied.
Well. It's less useful in one way - it doesn't say what file it was
trying to open. You could pass the filename *instead* of "open failed",
but that still omits the issue I had pointed out: what were you trying
to open the file for (at the very least, were you trying to read, write,
or exec it). Ideally the function would have a format and arguments.
Another thing that's unfortunately not easy to solve is whether an error
accessing a file was due to a problem (permissions/nonexistence) with
the file itself, or one of the directories along the way. This
information isn't provided by the OS, either, so at best you can detect
an error and then check every component yourself.