commit dd0581dfa3086135bdd3b91c762137bf953f256b Author: Alon Bar-Lev <alonbl> Date: Mon Oct 22 16:16:04 2012 +0200 packaging: add a method to reconfigure without init.d parameter systemd does not support additional service commands[1], while there can be argue if this is good or bad this is the fact. CURRENT IMPLEMENTATION Current bootstrap implementation uses hybrid approach while trying to pass "reconfigure" to init.d, and when fails, access the init.d script directly. This is highly none expected behavior. NEW IMPLEMENTATION Add /var/lib/vdsm/reconfigure file, if exists perform reconfiguration. This will work with any init.d system without issues. The service will be reconfigure at next start. ** We cannot remove the code from the current vdsm-bootstrap, so it able to reconfigure previous versions of vdsm. [1] http://www.freedesktop.org/wiki/Software/systemd/Incompatibilities Change-Id: Id4a8d5939fbefc6d3857d8083dfcf2180b9ba110 Signed-off-by: Alon Bar-Lev <alonbl> Reviewed-on: http://gerrit.ovirt.org/8725 Reviewed-by: Zhou Zheng Sheng <zhshzhou.ibm.com> Reviewed-by: Juan Hernandez <juan.hernandez> Reviewed-by: Adam Litke <agl.com> Reviewed-by: Dan Kenigsberg <danken>
modified per upstream rebase.
Setting requires_doc_text-, I'm assuming that if users need to reconfigure VDSM they should either be re-installing the machine from the management interface or contacting GSS,
OK - SF11 Creating /var/lib/vdsm/reconfigure does indeed cause VDSM to reconfigure on next startup.
3.2 has been released