Hello!

I didn't have to research systemd dependent software before, but I was implementing Zabbix monitoring system on our office network and noticed their new agent2 requires systemd.

I don't need agent2 on Slackware right now, I'm using it as Zabbix server and it is virtual machine anyway, but probably I'll need it at some point. I was looking at agent2 because it has build-in solution for hdd/ssd SMART monitoring, and who knows, maybe Zabbix will drop support for agent1 in the future.

So the question for now is in general. Is it possible to run systemd required services on Slackware? Any workaround would be ok too, just need to know if it's possible to work with such software if necessary, before I choose software and OS for office monitoring system.

Thanks in advance!

While Slackware includes a few systemd services in /usr/lib/systemd (I assume not used by default but as shipped by upstream), the issue could more likely be the lack of libsystemd. Just a guess as I did not dig into agent2 to check.

I hope these links will help you...
https://gitlab.alpinelinux.org/alpin...-/issues/13368

https://pkgs.alpinelinux.org/package...ity/x86/zabbix

https://git.alpinelinux.org/aports/t...abbix?h=master

2 members found this post helpful.

Did you find a good solution? Looking to create slackbuilds package for agent2, but did not yet investigate in more details.

Have you tried to use dlackware ? Bart was working on getting Slackware with systemd but I dont have idea if he is still on it.
See here: https://github.com/Dlackware/systemd

I think the question here is not that much about systemd itself, more about how to run the specific service.
Upstream packages rely on systemd.
I uploaded a simple version of it to slackbuilds, please check and let me know if that works for you.

Let me just understand, service files are run by systemd daemon isnt it ? They are called by the service, but then you should have the daemon to enable it or run it.
Or do I get whole that SysD thingy wrong ?

The application runs in the foreground... or background, but doesn't daemonize. So systemd handles that.
If you just start it normally, it runs as root, as it also doesn't switch user. systemd unit is also configured to run it with correct user.
AFAIK those are the main problems with it.
But rc script with this seems to do the trick:

su -s /bin/sh -c "/usr/sbin/zabbix_agent2 >> /var/log/zabbix/zabbix_agent2.log 2>&1 &" zabbixagent

1 members found this post helpful.

I suggest looking at "setpriv" as a better way to run a process as another user, e.g.,
Another solution would be using a proper process supervisor to run the zabbix_agent2 daemon. Slackware ships "daemon" by default, which features uid/gid changing and stdout/stderr forwarding to syslog.