bug-commoncpp
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fwd: Bug#352123: libcommoncpp2-dev: slog should not cut after 128 bytes


From: Mark Purcell
Subject: Fwd: Bug#352123: libcommoncpp2-dev: slog should not cut after 128 bytes
Date: Sun, 03 Dec 2006 12:01:58 -0000
User-agent: KMail/1.9.5


----------  Forwarded Message  ----------

Subject: Fwd: Bug#352123: libcommoncpp2-dev: slog should not cut after 128 
bytes
Date: Friday 10 February 2006 11:07
From: Mark Purcell <address@hidden>
To: address@hidden
Cc: address@hidden, Stephan A Suerken <address@hidden>

David,

Please find a suggestion from a Debian GNU/Linux user on your logging in
libcommoncpp2.

Mark

----------  Forwarded Message  ----------

Subject: Bug#352123: libcommoncpp2-dev: slog should not cut after 128 bytes
Date: Friday 10 February 2006 08:12
From: Stephan A Suerken <address@hidden>
To: Debian Bug Tracking System <address@hidden>

Package: libcommoncpp2-dev
Version: 1.3.22-1
Severity: wishlist
Tags: patch

Hi,

the thread safe logging currently cut lines after 128 bytes; this is a
bit short for real life logs.

Ideally, lines should be unlimited ;). However, I suggest to increase
that to 256 as a quick fix:

$ absurd? diff private.h.orig private.h
55c55
<       char _msgbuf[128];
---

>       char _msgbuf[256];

Thanks,

Stephan

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-2-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages libcommoncpp2-dev depends on:
ii  libcommoncpp2-1.3c2a          1.3.22-1   A GNU package for creating
 portabl

libcommoncpp2-dev recommends no packages.

-- no debconf information
--
Stephan A Suerken <suerken|address@hidden>
Phone: +49.721.91347-393

Schlund + Partner AG, Karlsruhe

-------------------------------------------------------

-------------------------------------------------------




reply via email to

[Prev in Thread] Current Thread [Next in Thread]