Ryan Armstrong

Apologies for this. I rarely get time to work with Zabbix any more :( Pull requests are welcome in the build project: https://github.com/cavaliercoder/libzbxpgsql-build I'll gladly upload packages if someone can...

I'd like to keep this open in case I get a chance to publish v4 packages. Also worth noting that Zabbix have had issues with breaking changes to the module...

I'm considering packaging an semodule, `zabbix_module_pgsql.pp` that includes all the required `allow` statements for libzbxpgsql to run correctly on an Enforcing machine. I'm not sure of best practice for installing/uninstalling...

The rlimit issue may provide some insight into how best to request this feature. For reference: - [Zabbix issue](https://support.zabbix.com/browse/ZBX-10542) - [Patch request](http://oss.tresys.com/pipermail/refpolicy/2017-May/009635.html) - [Accepted patch](https://github.com/TresysTechnology/refpolicy-contrib/commit/9fbf1b94fa4e9f6936ea7100f606ac572ed7af95) - [RHEL issue](https://bugzilla.redhat.com/show_bug.cgi?id=1393332) - [Fedora...

All the build sources are here: https://github.com/cavaliercoder/libzbxpgsql-build I hope is what you are looking for?

Issue also appears in RPM packages. Yum does not automatically resolve the lib dependency.

This can be a little tricky, but essentially you should triplicate the template and set different connection strings for each copy.

The process is unfortunately quite complicated for packaging and testing on so many versions of PostgreSQL/Zabbix/Linux. I am actively working on a new release now, including support for Zabbix 4...

Yes, I have this issue too. That file's name was changed at some. You're welcome to to update the name in your build (I think `libzbxpgsql.conf`)

Possibly 😬I'll try get a moment to fix this for you. Sorry for the pain!!!