On 22/10/2015 23:08, Patrick Mahoney wrote:
> I suppose that means when upgrading major version numbers, I should restart the
> entire supervision tree.
Yes. Generally, I recommend always using the binaries of the
*same* version of the package, but for long-running processes such
as the supervision tree, it's usually not a problem to not restart
them.
I don't like API/ABI changes, but this one was more or less
necessary, so yes, in this case you have to restart the supervision
tree, sorry. I try to keep major version number changes to a minimum.
> But the 'Broken pipe' error message in this case seems misleading.
It's a skalibs thing: it reports EPIPE on short reads, i.e. getting
EOF before the expected length of data. I find it's a very convenient
error code to use, though I agree the error message is confusing out
of context.
--
Laurent
Received on Thu Oct 22 2015 - 21:56:17 UTC