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 are started before Vidispine.
Create a systemd unit.d directory and override the service dependencies in a drop-in file:
$ vi /etc/systemd/system/vidispine.service.d/local.conf
[Unit]
Wants=transcoder.service solr.service
$ systemctl daemon-reload
$ systemctl enable vidispine
Setting JVM options¶
Create a systemd drop-in file and override the default JAVA_OPTS:
$ vi /etc/systemd/system/vidispine.service.d/local.conf
[Service]
Environment="JAVA_OPTS=-Xmx8192m -XX:MaxPermSize=512m"