You can use OTRS with PostgreSQL or MySQL, or even with Oracle if you need to. Of course you can use OTRS with a database that is on some central location in your setup. Max kernel policy version: 28 Preparation: installation of a database I chose Permissive here, rather than disabled, because otherwise you might loose the security context on files and would you want to enable SELinux on some later point you’d need to re-label files which is difficult. Type setenforce Permissive to set the current SELinux status to ‘permissive’.
This will make sure after a reboot selinux will not be enabled. You can check the status of SELinux with the sestatus command: ~]# sestatusĮdit the file /etc/selinux/config and set SELINUX=permissive. If you’re an advanced system administrator, you’d be able to create a profile for OTRS. This means that you’ll have problems if you don’t turn it off. OTRS does not ship with a profile for SELinux. This is why I would recommend CentOS version 7 over version 6 at this point in time. This means you better take a distribution that will receive security upgrades for a long time. Setting up your production server or migrating from one is something you don’t want to do every day.
Please note that there are some differences between CentOS 6 and CentOS 7: it now ships with systemd and with firewalld so the instructions to install OTRS are pretty different. The procedure will be very similar for Red Hat Enterprise Linux (RHEL) version 7 as this is binary compatible. In this post I’m going to walk you through installing OTRS 4 on CentOS 7.
0 kommentar(er)
