User talk:Fubar: Difference between revisions
No edit summary |
No edit summary |
||
Line 17: | Line 17: | ||
If you have SE Linux enforcing on, you need to do something like: | If you have SE Linux enforcing on, you need to do something like: | ||
chcon -R -u system_u -r object_r -t httpd_sys_content_t /var/www | <code>chcon -R -u system_u -r object_r -t httpd_sys_content_t /var/www</code> | ||
so apache can run cgi's and generally do useful things. | so apache can run cgi's and generally do useful things. |
Revision as of 18:03, 2 March 2007
CentOS notes
I just finished a limited install on a x86_64 CentOS 4.3 machine. There are some gotcha's worth knowing about. I only grabbed hg18.
Firstly, downloading the necessary parts of gbdb takes a very, very long time. There's a lot there. Secondly, I gave up after a day of trying to get everything working anywhere but at the root of the website. All sorts of hardcoded references to ../trash and such like. Once I gave up and reverted to /var/www/html as the root, everything seemed to work better... Thirdly, rsyncing the mysql directories directly works a treat. Just remember that the files become unavailable while they're being updated, but re-starting the rsync will work fine.
The following should work - they worked for me.
export MYSQLINC='/usr/include/mysql' export MYSQLLIBS='/usr/lib64/mysql/libmysqlclient.a -lz -lcrypto -lssl -lm -lnsl' export GLOBAL_CONFIG_FILE=/var/www/cgi-bin/hg.conf export HGCGI=/var/www/cgi-bin
If you have SE Linux enforcing on, you need to do something like:
chcon -R -u system_u -r object_r -t httpd_sys_content_t /var/www
so apache can run cgi's and generally do useful things.