On Wed, 26 Feb 2003 17:42:43 -0800 (PST)
Alvin Oga <[EMAIL PROTECTED]> wrote:
> On Thu, 27 Feb 2003, Robert Storey wrote:
>
> > Considering all the subdirectories in /home, it would probably be better to do
> > this:
> >
> > chmod -R 700 /home/*
>
> after you learn from your mistakes ... and have everybody mad at you...
> how do you recover ???
> - think you're in for a long list of mistakes ... :-)
> if the above chmod -R was a serious command to execute
>
> find /home -type d -exec chmod 700 {} \;
> find /home -type f -exec chmod 600 {} \;
> find /home -type l -exec chmod 777 {} \;
> -- i think you need to fix your symlinsk too
Dear All,
OK, thoroughly chastised. I deserve 40 lashes, plus the "Sysadmin Blunder of the Week"
trophy. But I'm probably the only English-speaking Linux user within 100 miles of
where I live, and I learn only from reading books (and getting flamed on mailing
lists) - so have mercy.
Thanks Alvin, your clever use of the find command works.
Now, one bash question I've been meaning to ask for a long time...
I keep seeing this...
{} \;
...on the end of lines in bash scripts. I don't have a good bash book, and I don't
know what this means, and obviously "man {} \;" isn't going to help. Can anyone reveal
for thick-headed "programmers" like me what that does?
After I receive an answer, I'll go join a convent and do three years of penance.
- Robert
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
