Seen that too during 3.0.5/3.2.1 tests.

The inetd zabbix_agent(.conf) has been removed upstream with the
release of 3.0, but is still processed within pkg/PLIST-main.

CC'ed to robert@.

Index: pkg/PLIST-main
===================================================================
RCS file: /cvs/ports/net/zabbix/pkg/PLIST-main,v
retrieving revision 1.11
diff -u -p -r1.11 PLIST-main
--- pkg/PLIST-main      7 Jul 2016 18:47:33 -0000       1.11
+++ pkg/PLIST-main      27 Nov 2016 10:12:11 -0000
@@ -14,11 +14,6 @@
 @bin sbin/zabbix_agentd
 share/examples/zabbix/
 @sample ${SYSCONFDIR}/zabbix/
-@mode 640
-@group _zabbix
-@sample ${SYSCONFDIR}/zabbix/zabbix_agent.conf
-@mode
-@group
 share/examples/zabbix/zabbix_agentd.conf
 @mode 640
 @group _zabbix



On Sun, Nov 27, 2016 at 09:21:05AM +0100, Harald Dunkel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> Hi folks,
> 
> zabbix_agent.conf in zabbix-agent-3.0.3 (amd64) appears to be
> broken: After the upgrade from 5.9 to 6.0 I found a shared object
> instead of a config file in /etc.
> 
> # file /etc/zabbix/zabbix_agent.conf
> /etc/zabbix/zabbix_agent.conf: ELF 64-bit LSB shared object, x86-64, version 1
> # file /etc/zabbix/zabbix_agentd.conf
> /etc/zabbix/zabbix_agentd.conf: ASCII English text
> 
> The "real" config file is zabbix_agentd.conf, but its still
> weird. Can anybody reproduce?
> 
> 
> Regards
> Harri
> -----BEGIN PGP SIGNATURE-----
> 
> iQEzBAEBCAAdFiEEH2V614LbR/u1O+a1Cp4qnmbTgcsFAlg6l2sACgkQCp4qnmbT
> gcv1Zgf/akXy9Iq4As+GrGLCv8mCYjVeELP3pBEb7A8g2JcWObBjEMxlzhlnyTwr
> AsvVtnpkpouaGEBrBBlWZ3oKe/rJIQbOu0jgR3FbaJhYBo4CT5/VIdABItDWSPC/
> uKT2eitUDeFpWJ2RpgvwwsF1N+WNq2GD14Y5Iza6DaB/xeP78CQaSCpK85ofAlHa
> /CeYicD4E52DAr1zVU6culPztWTG25da/DdtTynJ/DvSWNcKqIH7qO9TpdzdZaok
> H9YvuJwO3l+wSCay9jr+sdfQyHfubjMLrahUJN/KfrxWMakz0t5XgCRc4xxqlZuE
> zN6+1q3SrQ+gbTTHogygwieZr/QD+Q==
> =pAvO
> -----END PGP SIGNATURE-----
> 

-- 
Mark Patruck ( mark at wrapped.cx )
GPG key 0xF2865E51 / 187F F6D3 EE04 1DCE 1C74  F644 0D3C F66F F286 5E51

http://www.wrapped.cx

Reply via email to