e bug
earlier. The bug renders syslogd useless when log files grow over 2Gb.
-Chris
On Sat, 15 Oct 2005, Chris Stromsoe wrote:
Is there a new upload for sysklogd in the works? This bug is repeatable and
it causes real data loss if a log file grows to over 2gb in size. Changes to
the rules fi
) -D_LARGEFILE_SOURCE
else
-CFLAGS = -O2 -Wall $(getconf LFS_CFLAGS) -D_LARGEFILE_SOURCE
+CFLAGS = -O2 -Wall $(shell getconf LFS_CFLAGS) -D_LARGEFILE_SOURCE
endif
ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
STRIP = -s
Thanks.
-Chris
On Sat, 3 Sep 2005, Chris Stromsoe wrote:
From what I can tell
From what I can tell, CFLAGS isn't picking up the results of "getconf
LFS_CFLAGS" in debian/rules. A diff is attached. Please apply and push
out an update. Having to rotate logs every 4 hours is painful. Thanks.
-Chris
On Wed, 24 Aug 2005, Chris Stromsoe wrote:
On T
On Tue, 23 Aug 2005, Charles Majola wrote:
what arch? i can't seem to reproduce this with i386 and i686
I can confirm this on i386. System is stock sarge. syslogd was built
locally from debian source packages with a small local patch (at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=27
Package: mdadm
Version: 1.8.1-1
Severity: grave
mdadm 1.8.1 is not stable. The announcement (ANNOUNCE-1.8.1) states:
This is a "development" release of mdadm. It should *not* be
considered stable and should be used primarily for testing.
The current "stable" version is 1.8.0.
Please down
5 matches
Mail list logo
