Service configuration¶
The vidispine service user¶
The post-installation script in the packages will create the vidispine
user and group if they do not exist.
If you want to make sure that the vidispine
user has a specific UID and GID,
then create the vidispine
user and group manually before installing any
packages.
Service dependencies¶
If you’re running all components on the same server, then it can be beneficial to make sure that the transcoder and Solr is started before Vidispine. Note that this is only possible on systems running systemd.
$ vi /etc/systemd/system/vidispine.service.d/local.conf
[Unit]
Wants=transcoder.service solr.service
$ systemctl daemon-reload
$ systemctl enable vidispine
Setting JVM options¶
On Debian, edit the /etc/default/vidispine
file:
$ vi /etc/default/vidispine
JAVA_OPTS="-Xmx8192m -XX:MaxPermSize=512m"
Or on CentOS 6, the file /etc/sysconfig/vidispine
:
$ vi /etc/sysconfig/vidispine
JAVA_OPTS="-Xmx8192m -XX:MaxPermSize=512m"
On systems running systemd, create a file such as
/etc/systemd/system/vidispine.service.d/local.conf
and override the default
JAVA_OPTS:
$ vi /etc/systemd/system/vidispine.service.d/local.conf
[Service]
Environment="JAVA_OPTS=-Xmx8192m -XX:MaxPermSize=512m"