From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Erik K." To: development@lists.ipfire.org Subject: Re: IPTraf-ng problem with version 1.1.4 Date: Wed, 28 Aug 2013 20:03:49 +0200 Message-ID: <0D1AF94E-D44E-4DDC-A6C0-D2471ABBF43D@ipfire.org> In-Reply-To: <1377689181.19053.14.camel@rice-oxley.tremer.info> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4178005791484043400==" List-Id: --===============4178005791484043400== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, Am 28.08.2013 um 13:26 schrieb Michael Tremer: > Hi Erik, >=20 > 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-= ng-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 IPT= raf-ng quits. Until now i couldn=C2=B4t localize the problem, but it seems li= ke a bug in the new version.=20 >> The IPTraf-ng version 1.1.3 works without this problem. >=20 > 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. i have sent an mail to IPTraf mailinglist and i=C2=B4am currently compile the= patched iptraf-ng source with some fixes from the community. Hope this solve= s the problem, will let you know this after some testing results. >=20 >> 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=3D16= bcdaebca3586fda824e03822f82eecb796dc65 the diff can be found. >=20 > Should this be merged? Why is iptraf-ng writing log files any way? I think version 1.1.3 is also pretty much up to date (on my Fedora 16 system = version 1.1.1 works) and a good possibility to use IPTraf-ng nevertheless in = IPFire, i don=C2=B4t know how much time it takes that the above mentioned pat= ch will be provided in the official source code and also if it solves the pro= blem. The logging of IPTraf-ng is very nice i think, especially with the ability of= the filter usage the output can be very clear and applicable for different n= eeds also easy to use for further processing with shell scripting. The config= uration window allows to activate or deactivate the logging, so i thought it = might be a good idea to add it also in logrotate.conf. >=20 > -Michael >=20 > _______________________________________________ > Development mailing list > Development(a)lists.ipfire.org > http://lists.ipfire.org/mailman/listinfo/development --===============4178005791484043400==--