Bugzilla – Bug 4290
Consider support for systemd in ThinLinc
Last modified: 2018-10-17 10:24:07
You need to
before you can comment on or make changes to this bug.
For better or worse (okay, mostly for worse), it seems that many distributions
are switching to systemd. This includes popular "community" distributions such
as openSuSE and Fedora, which although are not officially recommended and
tested by us, do technically meet our minimum requirements for ThinLinc.
While most services are still shipping SysVinit scripts for backwards
compatibility, these will eventually be phased out, and some already have been
- for example, there is no longer an init script for sshd on Fedora 17; the
service must be controlled using systemctl instead. Our installer will
therefore fail to complete with a running SSH server on such systems.
We should also take a look at implementing vsmserver, vsmagent and tlwebadm as
Perhaps also worth noting is that there is no longer an init script for the
iptables service in Fedora.
We've made some progress in supporting systemd (e.g. bug #4634), but we can
probably do better. For example, see bug #4765 which causes problems on systemd
In general, some parts of ThinLinc seem to assume that SysV init scripts are
beung used. We should add compatibility with systemd, and probably start
shipping our own systemd service definitions as well. Re-assigning for
Adding fuel to the flame war: our services as systemd unit files
They work just fine even with the SysV init scripts installed in parallel
(Fedora 24). Migrating from SysV to systemd requires a bit of thought, systemd
didn't recognize that the services were already running. We'd probably want to
stop and disable the SysV scripts before enabling the systemd services.
(In reply to comment #3)
Rebased onto SVN r32822 and moved all unit scripts to /usr/lib/systemd/user, as
suggested by "pkgconfig systemd --variable=systemduserunitdir" on RHEL 7 and
Having systemd service files would make it much easier for a system
administrator to add local configuration and/or setup to the services without
having to modify the shipped init files.
systemd.unit(5) has more info about how this can be done, especially Example 2,
Overriding vendor settings.
https://github.com/bjorn-fischer/fss-tools is an example use case for this. In
this scenario, the sysadmin wants to add "Delegate=cpu,cpuacct" to a systemd