running subversion as non-root
keramida at ceid.upatras.gr
Tue Nov 1 09:14:47 PST 2005
On 2005-11-01 18:04, Roland Smith <rsmith at xs4all.nl> wrote:
>On Tue, Nov 01, 2005 at 03:40:47PM +0200, Giorgos Keramidas wrote:
>>On 2005-11-01 08:32, Cerion Armour-Brown <cerion at terpsichore.ws> wrote:
>>>On Tue, 1 Nov 2005 15:25:57 +0200, Giorgos Keramidas wrote
>>>> If you used the standard Ports stuff to install these and they
>>>> have these broken permissions, it may be a side-effect of a
>>>> broken umask setting for the root user.
>>>> What do you see if you log in as 'root' and issue:
>>>> # umask
>>>> Is this 0022 or something similar, or not? If not, what value
>>>> does it print?
>>> ahh, that's interesting: mine is 0027
>> Ugh! That's a bit Evil(TM). It means all the files root creates get
>> their 'other' permissions zeroed out unconditionally, so this explains
>> why your libraries can only be used by people in the 'wheel' group.
>> > I guess I should set that to 0022, and reinstall everything... (groan)
>> Very likely. Sorry for the bad news :-/
> You could also have find search for files with bad permissions, and
> correct them with chmod. something like
> find /usr/local/lib -type f -perm 750 -name "*.so*|xargs chmod 755
> (try the find part separately first)
> Something analogous can be done to bad binaries in /usr/local/bin.
That will probably work. But it may still end up leaving stuff with the
wrong set of permissions, i.e. for binaries that were really meant not
to have execute permission by 'other' users.
The safest path is to reinstall all ports in a clean /usr/local, if this
doesn't cause an unacceptable amount of downtime ;)
More information about the freebsd-questions