Re: [Nolug] The default to -rw-rw-r-- permissions debacle

"T.E.Stirewalt" <TomS@ComputerBrain.net> writes:

Several things. It's REALLY hard to follow your architectures. You're
apparently sharing a fsystem via NFS _AND_ Samba. Since Samba's
working, lets just continue on the linux side.

Login as your user. type 'umask'. what does it say? If it doesn't
say '0002' something in the user's startup files is changing
the umask. there are several possible culprits. .bashrc, .bash_profile,
and .profile. Search them all for umask settings.

Now type 'umask 002'
then 'touch test'
then 'ls -l test'
What does it say?

(you'll see that it works)

> I tried setting umask in home/morgan/.bashrc to 002 (it was 022) but
> it slowed my system terribly (clock lost four hours between 11pm last night
> and 6am this morning!) and programs slow and jerky; AND it did not solve
> the -rw-r--r-- situation upon file Create/Save.

The slowing of your system had nothing whatsoever to do with your
changing the umask. Some background process kicked off out of cron
most likely. My guess would be an update of the locate database as it
indexes all the filesystems on the box.

>
> I do an orderly shutdown and restart computer after every change. I make
> changes one at a time.

completely unnecesary. Logout and log back in is all that is needed.

You're group setup is quite convoluted. Just make one group. make all
the files group owned by that new group and make all your users a member
of that group.

Advice: you really need step back and study some basic linux system
adminstration.

-- 
Scott Harney<scotth@scottharney.com>
"...and one script to rule them all."
___________________
Nolug mailing list
nolug@nolug.org