Michael, You were right, changing the DEBIAN_PRIORITY=medium gave me the option to specifiy the server. Thanks for the help.
On Fri, Jan 26, 2007 at 09:21:09AM +0100, Michael Ablassmeier wrote: > hi Jeremiah, > > On Thu, Jan 25, 2007 at 11:26:47PM -0800, Jeremiah Mahler wrote: > > Upgrading this package will over write /etc/zabbix_agentd.conf > > causing any changes to be lost. Most notably the > > Server=myhost.localdomain is set to Server=localhost causing data > > to be lost until this line is fixed. > > uh, well. The Package is configured to set the Zabbix Server which was > specified during debconf configuration. So, if you set the server to > foobar while installing the package, and later on change this setting > from hand to foobarbaz, the package will re-set the server from the > debconf configuration on upgrade. > > I guess your debconf priority is set to high and therefore you were not > asked to set the server on installation. The Agent then defaults to > localhost, and sets this value to the Server directive on upgrade again. > > You can re-configure the package with: > > DEBIAN_PRIORITY=medium dpkg-reconfigure zabbix-agent > > and set the right server there, which will then be used on upgrades too. > Im not entirely sure how to prevent this in a sane way at the moment. > > Please note that this only happens with the Server= line in the > configuration files, all other settings are *not* overwritten. > > Some ugly way would be to read the configuration file on upgrade and > check if the debconf setting and the one from the file match, if not, > leave it alone. > > Im also not sure about the serverity, maybe RC due to data loss. > > bye, > - michael -- Jeremiah Mahler <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
