This bug has been open for more than 6 months with no fix. It's caused by
an error in the rules file, causing syslogd to be built with incorrect
large file support. There are two lines that need to be altered. The
patch to fix the problem is inline below. It was also attached to the bug
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 file to get the LFS_CFLAGS were wrong. The patch is
simple:
--- debian/rules.orig 2005-09-03 22:34:01.0 -0700
+++
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 Tue, 23 Aug 2005,
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
what arch? i can't seem to reproduce this with i386 and i686
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: sysklogd
Version: 1.4.1-17
Severity: grave
Justification: causes non-serious data loss
After upgrading our main syslog server to sarge, I found that some log files
were not updating. This was traced to the fact that large filesystem support
was not enabled properly. I applied the
On Wed, Jul 27, 2005 at 01:41:01PM +0800, Steven wrote:
Package: sysklogd
Version: 1.4.1-17
Severity: grave
Justification: causes non-serious data loss
After upgrading our main syslog server to sarge, I found that some log files
were not updating. This was traced to the fact that large
-Original Message-
From: Steve Langasek [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 27, 2005 2:25 PM
To: Steven; [EMAIL PROTECTED]
Subject: Re: Bug#320119: sysklogd: Large file support is
broken in the sarge version
This patch is incorrect. $(getconf LFS_CFLAGS) already
8 matches
Mail list logo
