Install FLM

The template contains the service configuration options that allow you to control the FLM service via Linux systemctl commands. It contains the basic commands to use the service; you may want to adapt the template to suit your needs. For more information on working with systemd, see the systemd documentation.

An example of the systemd template, flm.service, is shown in the sample.

 Installed in the global system ..
#
# /lib/systemd/system/flm.service
# systemctl daemon-reload
# systemctl stop flm.service
# systemctl start flm.service
# systemctl status flm.service
#
# Installed in user space
#
# Comment User and Group entries in Service
#
# ~/.config/systemd/user/flm.service
#
# systemctl --user daemon-reload
# systemctl --user stop flm.service
# systemctl --user start flm.service
# systemctl --user status flm.service
#
# If selinux is enabled, the following commands may be
# needed:
#
# semanage fcontext -a -t bin_t ${FLMDIR}/bin/flmprg
# restorecon -R -v ${FLMDIR}/bin/flmprg

[Unit]
Description=FourJs License Manager 7.00.01-202511201357
After=network.target nss-lookup.target
Documentation=https://4js.com/online_documentation/fjs-flm-manual-html

[Service]
Type=exec
Environment="FLMDIR=#!FLMDIR!#"
ExecSearchPath=#!FLMDIR!#/bin
ExecStartPre=flmprg -a env
ExecStart=flmprg -D
ExecReload=flmprg --service-restart
ExecStop=flmprg --service-stop
KillMode=mixed
Restart=on-abort
SuccessExitStatus=SIGTERM 0
PrivateTmp=true
User=fourjs
Group=fourjs

[Install]
WantedBy=multi-user.target

Where:

• Examples of the systemctl commands you can use to manage the service are included in the comments at the top of the file.
• The configuration items are in the [Unit], [Service], and [Install] sections.
• The ExecSearchPath parameter specifies the path to the FLM for the service. It affects where systemd looks for the commands specified in ExecStart, ExecStop, and so one. This parameter was introduced in systemd version 250. If your version of systemd is earlier (run systemctl --version), you will need to include the complete path to the flmprg commands in the Exec* parameters.
• The User= and Group= directives in the [Service] section let you specify which user and group should run the FLM process. These options are supported only for services installed in the global system directory (for example, /lib/systemd/system/flm.service) and managed with systemctl. They are not supported for services installed in user space (for example, ~/.config/systemd/user/flm.service) and managed with systemctl --user.

There are different ways of using the template depending on your requirements. You can either set the service as a global service or as a user service. For this example we set it as a global system service:

• Copy the FLMDIR/systemd/flm.service service file to the /lib/systemd/system directory.
• Reload the systemd configuration:

  $ systemctl daemon-reload

• Now you should be able to start, stop, and check the FLM service status.

  $ systemctl start flm.service
  $ systemctl stop flm.service
  $ systemctl status flm.service

• To configure the service to start automatically on boot, you need to enable it:

  $ systemctl enable flm.service

• To check the service logs, run:

  $ journalctl -u flm.service

If Security-Enhanced Linux (SELinux) is enabled and enforcing on your Linux system, ensure the service unit and its executable files have the correct SELinux context. Incorrect contexts can prevent the service from starting. These commands are also included as comments in the systemd service template file provided:

1. Restore default SELinux context:

   restorecon -Rv ${FLMDIR}/bin/flmprg

2. Manage custom contexts if needed:

   semanage fcontext -a -t bin_t ${FLMDIR}/bin/flmprg

Other useful checks:

1. Check SELinux status:

   getenforce

2. Review logs for SELinux denials:

   journalctl -xe

For more details, see the SELinux documentation or use man selinux