A number of the configuration files which manage the daemons used by lava-server and the lava-slave daemon for lava-dispatcher are being updated in 2016.9. This has implications for those who install the upgrade, especially if this is normally done by automation.
Configuration file '/etc/init.d/lava-slave' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** lava-slave (Y/I/N/O/D/Z) [default=N] ? y Installing new version of config file /etc/init.d/lava-slave ...
dpkg will check the checksums of the init files against the current and previous packages and halt installation with the above prompt in case of doubt. Admins may need to install the update manually (directly on the command line).
The recommendation is to accept the package maintainer's version but all admins may want to check the difference between the two.
Changes in this release include fixing the log rotate handling of lava-master using reload and a rewrite of the lava-server CLI script to drop the use of entrypoints which changes the syntax of the daemon options.
The most common reason for init files to be modified is to change the loglevel. This can be done in /etc/default/lava-server:
# Additional options that are passed to the Daemon. DAEMON_OPTS="loglevel=debug"