> Otherise the lxc.service is restarted when upgrading the > package causing all containers to be stopped. > > Note that this affects the 'prerm' portion of the package so > upgrading from an older package to this one still performs > the old version's stop action.
What if we do the following instead? --- lxc.service.org 2016-01-14 16:21:11.055274920 +0100 +++ lxc.service 2016-01-14 16:21:18.935208223 +0100 @@ -8,8 +8,6 @@ RemainAfterExit=yes ExecStartPre=/usr/lib/x86_64-linux-gnu/lxc/lxc-devsetup ExecStartPre=/usr/lib/x86_64-linux-gnu/lxc/lxc-apparmor-load -ExecStart=/usr/lib/x86_64-linux-gnu/lxc/lxc-containers start -ExecStop=/usr/lib/x86_64-linux-gnu/lxc/lxc-containers stop # Environment=BOOTUP=serial # Environment=CONSOLETYPE=serial #Delegate=yes We have our own autostart code anyways. _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
