From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: IPTraf-ng problem with version 1.1.4 Date: Wed, 28 Aug 2013 13:26:21 +0200 Message-ID: <1377689181.19053.14.camel@rice-oxley.tremer.info> In-Reply-To: <78E48C47-CD23-4B58-9C6B-77EB718C8C82@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6384624546824697086==" List-Id: --===============6384624546824697086== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Erik, On Wed, 2013-08-28 at 13:13 +0200, Erik K. wrote: > Hi all, > i want to report a problem with the unreleased, updated version of IPTraf-n= g-1.1.4 . The problem occurs if i turn on the IPTraf logging, after a while i= get an "Floating point exception" under the "Packets catured:" line and IPTr= af-ng quits. Until now i couldn=C2=B4t localize the problem, but it seems lik= e a bug in the new version.=20 > The IPTraf-ng version 1.1.3 works without this problem. This is most certainly a division by zero. If you do that, the floating point unit of the CPU throws a floating point exception. It is best to report that to the iptraf-ng developers and open a bug report about this on our own bugtracker as well, so that we can update as soon as a fix is available. > Beside info: > I have added an IPTraf-ng configuration for the logrotate.conf. In here -->= http://git.ipfire.org/?p=3Dpeople/ummeegge/ipfire-2.x.git;a=3Dcommit;h=3D16b= cdaebca3586fda824e03822f82eecb796dc65 the diff can be found. Should this be merged? Why is iptraf-ng writing log files any way? -Michael --===============6384624546824697086==--