On Sep 5, 12:12 pm, "Robert J. Carr" <[EMAIL PROTECTED]> wrote: > Hey Graham- > > Thanks so much for the response. Here are some notes: > > > Probably because you restarted Apache using: > > > sudo /usr/sbin/apachectl start > > > or similar, instead of: > > > sudo -H /usr/sbin/apachectl start > > Neither, I always use /etc/init.d/httpd start|stop and always as root > (not sudo). Anything enlightening with this new information?
But how do you become root? Which command, whether it be apachectl or init.d script is not the issue here. > > problems at times because things might appear to work, but when box > > reboots and Apache started as root, without those parts of the user > > environment application may fail. > > That's exactly why I always use /etc/init.d because that's what is > used when the system starts. As I said, it will not make a difference, if you were to go: sudo /etc/init.d/httpd start you would have exactly the same problem. So we get back to how you become root. If the way you become root means that proper root shell distinct from user is created there is no way that it can inherit identity of original user in environment in some way. So, you may not use 'sudo', but if you use 'su' without '-l' flag same issues may arise. Depending on system used there may possibly be other ways of becoming root. Whatever is used, it must perform a full login or have the same effect. As to your SELinux configuration problems, maybe you can learn something from: http://www.packtpub.com/article/selinux-secured-web-hosting-python-based-web-applications Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
