Robin Bowes wrote:
Nils Breunese (Lemonbit) wrote:
Sounds like a question for the dev list: http://lists.otrs.org/cgi-bin/listinfo/dev
OK, will repost on there.
We're using the RPM provided by OTRS on CentOS and that one works fine for us, also regarding configuration files.
I prefer the file locations with the EPEL RPM. I just need to sort out the config files.
Actually, looking at how the otrs spec file works, it uses the SetPermissions script to sort out the permissions. However, I don't like the permissions this script creates. For example, the otrs root is chowned to the apache user, so any apache process can write to any otrs file. IMHO, the otrs files should be owned by root, and be readable to the apache process. Any exceptions should be made expliclty, e.g. Kernel/Config.pm needs to be writeable by the apache user. I'll study this some more and come up with a solution... R.