> > -rw------- 1 apache apache 1955 Jul 3 16:04 index.html
> >
> > is still served to the browser, even though it is not world
readable...
>
> If you don't want that file to be served, make it inaccessible to the
> apache user, either by:
>
> a) changing the ownership of the file which chown
this is what I ended up doing... I have a user account on this system
which is my primary user acct (not wanting to log in as root all the
time). So i chown'd the web directory and the files within it to be owned
by that primary user account. The problem now is that 1. that user account
doesn't have access to /var/www/vhosts/, only root does. 2. Any new files
created in the web directories are automatically owned by apache.
(is it obvious yet that I'm pretty much a beginner at system
administration?)
So will adding the primary user acct to the apache group solve the problem
of not being able to make edits in the web directories? And then, will new
files created under that account be owned by that account, or will they
automatically be owned by apache user/group?
> Message: 2
> From: "Bob Staaf" <[EMAIL PROTECTED]>
>
> What are you trying to do? The example below although not world
readable is
> readable by the owner of the file which is apache. Are you trying to
set up
> a private website? If so look at the .htaccess file. If you do a
No, not a private website. I just want to be able to "activate" and
"deactivate" specific directories based on whether or not I want them to
be visible vie the web. for example, if I have the index.html files in the
example above, and then if I have an index1.html which I'm using to test a
new layout or something... I don't want anyone to be able to load that
file if they happen to know the filename. This is just one example, but in
general I want to be able to turn files on and off at my choosing... Thx.
m.
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
