|Summary:||/home/httpd, etc incompatible with automounted /home|
|Product:||[Retired] Red Hat Linux||Reporter:||baz|
|Component:||installer||Assignee:||Jay Turner <jturner>|
|Status:||CLOSED NOTABUG||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||1999-11-30 14:33:05 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description baz 1999-10-28 08:44:59 UTC
/home/httpd, etc are incompatible with an automounted /home for real users. This causes problems when trying to integrate RH systems into an existing enterprise network.
Comment 1 Bill Nottingham 1999-10-28 15:37:59 UTC
/home/samba is gone in the latest samba packages in Raw Hide...
Comment 2 Jay Turner 1999-10-29 17:42:59 UTC
Not sure whether you are seeing this problem during an installation or during a manual upgrade/installation of http, but either way, there is a solution. In the case of the manual installation, I am guessing that you are getting an error telling you that it cannot install the package. In which case you will want to make use of the "--excludepath <path>" argument for RPM. You can tell it to ignore the /home path when installing http, and then those files will not get installed and you will be able to install the package. In the case that you are seeing this during an install, then just change the location of the docroot in the httpd.conf file.
Comment 3 baz 1999-11-08 17:18:59 UTC
Nothing to do with install. /home/httpd (or any other software package) is simply wrong in a shared/automounted environment. Installation will fail since /home isn't writable. Given that /home/httpd is the same on all the machines on site, how do you distinguish between installations? How do you prevent the files in /home/httpd being accessed on other machines? How do you tell (any) automount that everything in /home should be automounted except /home/httpd? By default, the contents of /home/httpd are machine private - place them somewhere that doesn't clash with the implementation of an existing site infrastructure.
Comment 4 Jay Turner 1999-11-09 17:31:59 UTC
I am still not sure what you are aiming at here. If you have /home automounted in a production environment, then what are you doing with /home/httpd on the machines with apache installed? You appear to be saying that apache should not try to write stuff to /home/httpd, but that is the default location for apache files. If you want to change this, then you would want to use the "--excludepath" directive or the "--relocate" directive which will allow you to relocate the /home/httpd files to another location which is not automounted. The fact that you are automounting the /home directory implies that you have a machine storing the /home directories for all employees. If this is the case, and you are allowing the employees to host their own http sites on their machines, then you would want to change the document root in the apache config files so that it pointed to another location on the machines which is not automounted and which can be perimissioned off so that only those people with the appropriate access can get to it. Please explain to me what problems are you seeing in detail and we will work with you to solve them.