Please stabilize.
amd64: This appears fairly complex. emerged with most fundamental use flags set, setup with a db effective; zabbix server and agentd services both successfully start. Passes. Beyond that needs apache knowhow; will persevere a little more.
small issue: * Add these lines in the /etc/services : * * zabbix-agent 10050/tcp Zabbix Agent * zabbix-agent 10050/udp Zabbix Agent * zabbix-trapper 10051/tcp Zabbix Trapper * zabbix-trapper 10051/udp Zabbix Trapper * chmod: cannot access `//etc/zabbix/zabbix_*': No such file or directory When you'll fix, please add 'die' where is needed. Ty.
I think you mean these ones. testuser@archtester /mnt/images/qemu $ cd testuser@archtester ~ $ ls /etc/zabbix zabbix_agent.conf zabbix_agentd.conf zabbix_server.conf zabbix_trapper.conf If ever I can get apcahe figured out shall test the rest
next; Finally got apache sorted. Brought up the php frontend. Page 3 stonewalls with a listing of invalid php config settings that are never satisfied with required changes to the php.ini file(s). in /etc/php/*. The package passes stable emerge benchmarks, but good luck to anyone wanting to configure and use it for its intended purpose.
well, finally got thru the zabbix frontend, and it looks great once you get thru the maze. One minor point re use flags. zabbix depends on php 5. Not knowing php at all, I blindly loaded up a stack of use flags in php. Apparently the use flag sharedext has some exp users puzzled why it is present in php, it blocks php database support, so need be stipulated to be unset in php as a dep package.
x86 stable
amd64 done. Thanks Agostino and Ian
Looks like this bug was resolved months ago and already obsolete by newer stable versions (1.8.10 now). Marking resolved - obsolete.
