He pointed out that yesterdays blog on SELinux Labeling did not provide a solution to the /myapache problem.
The solution is to label /myapache and all its children with a label httpd can read.
You can figure this out by using:
- Set files with the httpd_sys_content_t type, if you want to treat the
files as httpd sys content.
icy[^/]*/html(/.*)?, /usr/share/drupal.*, /var/lib/trac(/.*)?,
# ls -lZd /var/www/html
drwxr-xr-x. root root system_u:object_r:httpd_sys_content_t:s0 /var/www/html
You could simply put the labels in place using chcon.
chcon -R -t httpd_sys_content_t /myapache
The best solution is to tell SELinux about the label change.
# semanage fcontext -a -t httpd_sys_content_t '/myapache(/.*)?'
# restorecon -R -v /myapache
Note: If you wanted to allow httpd to write to the directory you would use the httpd_sys_rw_content_t type.