On Tue, Nov 01, 2005 at 03:40:47PM +0200, Giorgos Keramidas wrote: > On 2005-11-01 08:32, Cerion Armour-Brown <[EMAIL PROTECTED]> 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. Roland -- R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt
pgprcpk60uYng.pgp
Description: PGP signature
