Re: Bug in ucspilogd v2.2.0.0

From: Laurent Bercot <ska-skaware_at_skarnet.org>
Date: Sun, 9 Aug 2015 10:44:02 +0200

On 09/08/2015 09:27, Colin Booth wrote:
> I haven't yet dug into the skalibs code to see what changed between
> those tags, or started bisecting it to find out which commit broke.

  The git diff between 2.3.5.1 and current HEAD is pretty small, and
there's really nothing that changed in the graph of functions
accessed by skagetlnsep(), the failing entry point.


> Functional:
> [pid 19388] readv(0, [{"<13>Aug 9 07:26:07 cathexis: wo"..., 8191},
> {NULL, 0}], 2) = 34
> (...)
> Dysfunctional:
> [pid 31983] readv(0, [{"<13>Aug 8 23:46:57 cathexis: wo"..., 8191},
> {NULL, 0}], 2) = 33

  The path leading to the first invocation of readv() hasn't changed,
but readv() gives different results. My first suspicion is that "logger"
isn't sending the last character (newline or \0) in the second case
before exiting, which skagetlnsep() interprets as "I was unable to
read a full line before EOF happened" and reports as EPIPE.
  Are you using the same version of "logger" on both machines ?

  Grrr. If "logger" starts sending incomplete lines, I may have to change
the ucspilogd code to accommodate it.

-- 
  Laurent
Received on Sun Aug 09 2015 - 08:44:02 UTC

This archive was generated by hypermail 2.3.0 : Sun May 09 2021 - 19:38:49 UTC