Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Josh ChaitinPollak wrote: > > On Dec 29, 2005, at 4:30 PM, Tom Metro wrote: > >> David Kramer wrote: >>> I ran into one bit of trouble already where the commands worked fine >>> on the >>> CLI, but running it through apache gave strange results, and I >>> finally figured >>> out the build working directory had to be somewhere under the >>> DocumentRoot >>> (prolly an selinux thing. Gawd I hate selinux.). Moved the build >>> dir, and >>> got past that problem. >> >> If it was an selinux thing, shouldn't you also be able to solve that >> by setting the right security context on the original directory? > > You could try temporarily disabling selinux with "setenforce 0" I think. That sounds worth a try. Thanks all for your suggestions so far. I'm away for the weekend, but the first things I want to try when I get back are that, and changing the shell for apache so I can log in as apache.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |