Hi, I'm just starting to look at OTRS on the CentOS platform. As is quite usual for a package that does not have any/many core devs using it on Redhat-flavours of linux (I assume), I have found that the otrs-provided spec file does not do things quite right for the Redhat-platform. Fortunately, there is an OTRS RPM in the epel repository which has a more suitable layout. I have successfully used this to rebuild the 2.30rc1 RPM. Unfortunately, it is not quite right - specifically, it needs some work on defining which files should me marked "%config(noreplace)" so they are not zapped when the RPM is upgraded. So, I'm looking for some feedback from the otrs team as to which files should be considered "configuration" files and not replaced when the RPM is upgraded. Can anyone give me some guidance in this? Thanks, R.
Robin,
The file /Kernel/Config.pm holds all custom user config parameters.
HTH.
Harry Cruz
Brazil
On Mon, Jul 28, 2008 at 9:55 AM, Robin Bowes
Hi,
I'm just starting to look at OTRS on the CentOS platform. As is quite usual for a package that does not have any/many core devs using it on Redhat-flavours of linux (I assume), I have found that the otrs-provided spec file does not do things quite right for the Redhat-platform.
Fortunately, there is an OTRS RPM in the epel repository which has a more suitable layout. I have successfully used this to rebuild the 2.30rc1 RPM.
Unfortunately, it is not quite right - specifically, it needs some work on defining which files should me marked "%config(noreplace)" so they are not zapped when the RPM is upgraded.
So, I'm looking for some feedback from the otrs team as to which files should be considered "configuration" files and not replaced when the RPM is upgraded.
Can anyone give me some guidance in this?
Thanks,
R.
_______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support or consulting for your OTRS system? => http://www.otrs.com/
Harry Cruz wrote:
Robin,
The file /Kernel/Config.pm holds all custom user config parameters.
HTH.
Harry, It's a little more complicated than that. It's not just the stuff that's configurable through the web interface, but also other elements that a sysadmin might customise. For example, I've modified the postmaster_mailbox cron file, so I don't want that over-writing. I'm currently working on using a combination of: 1. the otrs spec file 2. the EPEL spec file 3. the SetPermissions.sh script Hopefully, I should come up with something usable. R.
Robin Bowes wrote:
I'm just starting to look at OTRS on the CentOS platform. As is quite usual for a package that does not have any/many core devs using it on Redhat-flavours of linux (I assume), I have found that the otrs-provided spec file does not do things quite right for the Redhat-platform.
Fortunately, there is an OTRS RPM in the epel repository which has a more suitable layout. I have successfully used this to rebuild the 2.30rc1 RPM.
Unfortunately, it is not quite right - specifically, it needs some work on defining which files should me marked "%config(noreplace)" so they are not zapped when the RPM is upgraded.
So, I'm looking for some feedback from the otrs team as to which files should be considered "configuration" files and not replaced when the RPM is upgraded.
Can anyone give me some guidance in this?
Sounds like a question for the dev list: http://lists.otrs.org/cgi-bin/listinfo/dev We're using the RPM provided by OTRS on CentOS and that one works fine for us, also regarding configuration files. Nils Breunese.
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. Thanks, R.
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.
participants (3)
-
Harry Cruz -
Nils Breunese (Lemonbit) -
Robin Bowes