On Wed, Oct 12, 2016 at 02:06:35PM +0200, Reyk Floeter wrote: > On Wed, Oct 12, 2016 at 01:44:25PM +0200, Reyk Floeter wrote: > > Hi, > > > > vmctl reload is currently broken, the attached diff fixes it and > > re-introduces the semantics that originally came from iked: > > > > - load/reload just reloads the configuration without clearing any > > running configuration. This way you can start vmd with a few > > configured vms, terminate one vm, and reload the configuration which > > will restart the terminated vm but keep the running ones. > > > > - reset clears the configuration (and possibly terminates vms) without > > reloading the configuration. "vmctl reset" thus terminates all vms. > > > > # vmctl load /etc/my-personal-vm.conf > > # vmctl reload > > # vmctl reset > > > > OK? > > > > ajacoutot@ reminded me of SIGHUP: > change it to reload instead of reset on HUP. > > Updated diff, OK?
It fixes my reload problem (vmctl and SIGHUP), "vmctl load <file>" works, "vmctl reset" also works and the code reads fine. ok rzalamena@
