Thanks for the quick response. I didn't have enough time to test the package but one of the zabbix developers
has posted an example of the zabbix.conf.php file.

It seems that Debian configuration file is quite different from the current one that zabbix generates:

====================
<?php

global $DB;

$DB["TYPE"]        = "MYSQL";
$DB["SERVER"]        = "127.0.0.1";
$DB["PORT"]        = "0";
$DB["DATABASE"]        = "dbname";
$DB["USER"]        = "user";
$DB["PASSWORD"]        = "pass";
$ZBX_SERVER        = "127.0.0.1";
$ZBX_SERVER_PORT    = "10051";


$IMAGE_FORMAT_DEFAULT    = IMAGE_FORMAT_PNG;
?>
====================

According to this, it seems that some vars are renamed (like DB_*) and IMAGE_FORMAT_DEFAULT is also not included (like ZBX_* reported in this bug). However, Zabbix is still working (I would bet because in source code I've seen some double-checking about existence of $DB[var]).

Is that possible that we can follow the same standard file as Zabbix mainstream to avoid future issues? Is there any reason to follow (for instance) DB_TYPE instead of DB["TYPE"]? Can this be implemented?

   Miguel.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to