Re: Executable files in CVS - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Executable files in CVS
Date
Msg-id 2339.1069646819@sss.pgh.pa.us
Whole thread Raw
In response to Re: Executable files in CVS  ("Marc G. Fournier" <scrappy@postgresql.org>)
Responses Re: Executable files in CVS  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
"Marc G. Fournier" <scrappy@postgresql.org> writes:
> On Sun, 23 Nov 2003, Tom Lane wrote:
>> Sure, but couldn't we automatically turn off the write bits?

> Just curious, but what do the write bits harm?

They're just extra protection against making a dumb mistake; the old
belt-AND-suspenders theory.

If we were to turn off group write permission on the CVS directories,
then the protection would be a lot stronger, but it would also prevent
manual fixes of the sort Bruce just made (or manual removal of stale
CVS lock files, as I can recall having to do several times).  So I'm not
in favor of that.  But "no write on the CVS data files" seems like a
good compromise policy.

Besides, it's a tad odd to see files that are marked group writable but
not owner writable.  You've got to agree there's not much sense in that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: Executable files in CVS
Next
From: Christopher Kings-Lynne
Date:
Subject: ALTER SEQUENCE enchancement