On Fri, Sep 30, 2005 at 09:22:30AM -0400, Carl Hartung wrote:
On Friday 30 September 2005 07:05, poeml@cmdline.net wrote: <snip>
I found the problem. The default Apache2 installation on 10.0 RC1 omitted the section, below, from /etc/apache2/default-server.conf. When I inserted it and restarted Apache2, my ~/public_html directory became available.
In hindsight, the above description is not very accurate. The system in question started as a Beta 1 "fresh install" that was updated via YaST2 to Betas 2, 3, 4 and finally to RC1. This means the default-server.conf file I was inspecting could have been written incorrectly or mangled at any time during that process. A better description would have included this update/upgrade path. I apologize if my hastily written words have caused you any hair-pulling... :-)
Well, I personally know that the file has not been touched since quite a while. I am the one who packages it. The timestamp of the last modification is 2004-03-18 17:41 It does include the /etc/apache2/mod_userdir.conf configuration. So if your local copy doesn't contain it, there must be something else at fault. I can not think of anything in the build/packaging process which would remove arbitrary configuration from the file. Also, there is nothing special happening during the beta phase or the update process which could induce such a change.
It is impossible that the section was missing.
Under the circumstances, "impossible" is still a little too strong... I didn't dream the problem up and someone else reported the same thing a few days later. I suspect we probably followed the same update path and procedure.
Unless and until another explanation surfaces, I've written this one off as an anomaly induced by the beta process, itself.
Well, I don't have an explanation either ;) Peter -- the big machine that goes "ping" imitated the tasty machine that goes "ping"