|
From: | Assaf Gordon |
Subject: | Re: [bug-gawk] gawk - 'inplace' feature ignores file's access flags (read-only) |
Date: | Wed, 10 Jun 2015 10:39:37 -0400 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 |
Hello, On 06/10/2015 10:28 AM, Johannes Meixner wrote:
On Jun 10 08:35 Andrew J. Schorr wrote (excerpt):On Wed, Jun 10, 2015 at 01:08:43PM +0200, Janis Papanagnou wrote:The 'inplace' feature ignores access flags of files; if the file is write protected it will nonetheless be overwritten.
<...>
Regardless how it is actually implemented, I think it is a valid question what one could normaly expect from an 'inplace' feature when on the one hand the user has run a tool to replace the file's content but on the other hand the file permissions are contradicting.
Somewhat related: An interesting and useful overview of how to replace a file inplace written by Pádraig Brady: http://www.pixelbeat.org/docs/unix_file_replacement.html while it deals with shell commands to replace a file, but the lessons might be useful here too.
[Prev in Thread] | Current Thread | [Next in Thread] |