Mark
<What's the reason for the second command?>
I can't actually think of one now that you have pointed it out :)
I was in a rush and banged in commands that I found online without giving them
too much thought; which in retrospect probably wasn't the most sensible
approach.
I have now reversed out of the situation, but it just goes to show that you
shouldn't treat every solution you find as gospel.
Lesson learned :)
Stu
________________________________
From: Mark Rogers <m...@quarella.co.uk>
To: Peterborough LUG - No commercial posts <peterboro@mailman.lug.org.uk>
Sent: Thu, 24 March, 2011 18:06:52
Subject: Re: [Peterboro] Local ApacheVirtual Host Errors.
On 24 March 2011 12:34, Stuart Bird <e_tect...@yahoo.co.uk> wrote:
This is now solved - thanks.
>
I had the exact same problem a couple of days ago, shame I didn't see your
question until you'd solved it yourself as I recognised the problem immediately!
# sudo chmod -R a+rX /home/stu/www/
># sudo chmod a+rx /home/stu
>
What's the reason for the second command?
As it stands you've made all files in your home directory executable by anyone,
which is probably not what you wanted.
sudo chmod -R a+rX /home/stu/www
.. should have been enough. And for that matter, so should:
chmod -R a+rX /home/stu/www
.. as the files were presumably already owned by you so you shouldn't have
needed sudo to grant permissions to others.
Note I didn't include the trailing / - I think your first command probably
didn't give access to the www directory itself, just to files/directories below
it.
--
Mark Rogers // More Solutions Ltd (Peterborough Office) // 0844 251 1450
Registered in England (0456 0902) @ 13 Clarke Rd, Milton Keynes, MK1 1LG
_______________________________________________
Peterboro mailing list
Peterboro@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/peterboro
