anyconnect 4.8 not working on openSUSE Leap 15.1

[m_krieger]

Hi,

when installing anyconnect 4.8 on openSUSE LEAP 15.1, the installation fails with

install: cannot create regular file '/lib/systemd/system/vpnagentd.service': No such file or directory

As a result, there is no systemd startscript for the vpnagentd.

The root of the problem is, that anyconnect setup uses a fixed location for the systemd service files (SYSTEMD_CONF_DIR="/lib/systemd/system") and openSUE LEAP 15.x has a differing systemd path (/usr/lib/systemd/system)

# systemctl --no-pager --property=UnitPath show | tr ' ' '\n'

UnitPath=/run/systemd/transient
/etc/systemd/system
/run/systemd/system
/run/systemd/generator
/usr/lib/systemd/system
/run/systemd/generator.late

Is there a generic way to install the anyconnect 4.8 from headend deployment package without editing the package  on the users machine if the distro uses a non-default systemd UnitPath?

Cheers,

Markus

[ronaldo.df]

Hi,
You may create a soft link: ln -s /usr/lib/systemd/system /lib/systemd
Regards

[JH.Smith.2905 · Accepted solution]

with tumbleweed:

ln -s /usr/lib/systemd /lib/systemd

Maybe in Leap too.

Perhaps one directory too much in your symlink:

ln -s /usr/lib/systemd/system /lib/systemd

[m_krieger]

Hi,

we already proposed that as a quick & dirty workaround. However, this doesn't scale

well with users perception. And there could be other distros out there also using their own

systemd setup / paths...

I don't know wether systemd or a LSB compliant linux requires the use of /lib/systemd/system, but it would be prudent, if the installer would check where the respecitve system has set it's systemd path set to...

I've just checked the client 4.8.03036 and the installer still doesn't check wether systemd is using different paths...

Cheers,

Markus