Re: FHS and /var/www
Ben Finney dijo [Sun, Jul 20, 2008 at 10:39:43AM +1000]:
> > Should we force all httpd:s to use /srv/www instead of /var/www, or
> > should an exception to the policy be added?
> I think there's no hardship if we support the FHS location, so an
> exception shouldn't be made.
> What do you mean by "force all [HTTP servers] to use /srv/www instead
> of /var/www"? Why do you think that's desirable?
> Conformance with the FHS would seem to require only that such files
> must be addressible under the '/srv/www' location. I don't see support
> for the "instead of /var/www" part of your question.
> We could deal with this as we did for '/usr/share/doc' vs '/usr/doc';
> that is, make '/srv/www/foo' the canonical location but allow a long
> transition period where '/var/www/foo' is permitted as a symlink to
Moving from /var/www to /srv/www gains nothing - We would still have
all webservers throwing files where they are not supposed to, to a
What I'm doing currently for Cherokee is to have the server's default
site at /usr/share/cherokee/default-site. At post-install, if /var/www
is empty, I create symlinks to the default site.
Of course, the fact is I _am_ using /var/www and should probably
change it somewhere else... But (of course, modulo whatever I learn
from this thread and refered sites) it should not have much
impact. The important thing is for webservers not to clobber whatever
the user has placed in his directory of choice - and of course,
provide an easy way to change the default Web root.
Gunnar Wolf - email@example.com - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF