On 02/27/14 15:22, Dwight Engen wrote:
These changes will break the script on Fedora and derived distros. The reason for /var/lock/subsys is that without it [1], SysV init (on Fedora at least) won't call the K script at shutdown time so the containers don't get a chance to shut down cleanly.
this is not really an issue, vmware does [ -d /var/lock/subsys ] || mkdir -p /var/lock/subsys before doing touch it's harmless on debian but I don't think it usefull for debian
There are other problems as well, /lib/lsb/init-functions might not exist, and even when it does on Fedora it does not contain log_progress_msg() nor log_daemon_msg(). Maybe it is not practical to have a cross distro sysvinit script? Perhaps we should have distro specific scripts ala the way we do default.conf in lxc/config/etc?
Most of the script can be shared, there is already a configure time switch (with-distro), you can make lxc.in and replace the distro specific parts:
I'll check fedora init docs and make a patch, but doesn't fedora uses systemd now?
I don't think lxc is suitable for old distributions, I had to use kernels from backports to have a good support in debian stable (3.11 vs 3.2.0)
and I still waiting for 3.13 because 3.12 breaks lxc-attach Regards -- Gianluigi Tiesi <sher...@netfarm.it> EDP Project Leader Netfarm S.r.l. - http://www.netfarm.it/ Free Software: http://oss.netfarm.it/ Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? _______________________________________________ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel
