Georgiy Treyvus wrote: > On 9/25/12 3:00 AM, GNU bug Tracking System wrote: >> Your bug report >> >> #12494: 0 exit status even when chmod fails ... > Wait. Before you folks put the final nail in the coffin I have three > points/questions:
Thanks for replying. That shows that while it was a foregone conclusion to those of us who have dealt with this sort of issue before, it wasn't clear to everyone reading. Thanks to Eric's explanation, you should now see why we cannot afford to work around such brokenness: neither in chmod(1) nor via a chmod(2) wrapper.
