Quoting Alexander Vladimirov ([email protected]):
> Despite container seems to work and shutdown without any visible errors, I
> get exit code 130 when lxc-start terminates. That's not much of a problem,
> but requires some workarounds when running as systemd service and could
> point to some locking issue if this exit code corresponds to EOWNERDEAD
> errno.
Must be:
if (WIFSIGNALED(status)) {
int signal = WTERMSIG(status);
ret = ret + 128 + signal;
INFO("child <%d> ended on signal (%d)", pid, signal);
}
That is, signal is 2 (kill), and we return 0 + 128 + signal. I don't
know why this code is there. It seems obfuscatory. Git-blame points
to Michel, so cc:ing him here.
-serge
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Lxc-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lxc-devel
