From: "Erik K." <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPTraf-ng problem with version 1.1.4
Date: Wed, 28 Aug 2013 20:03:49 +0200 [thread overview]
Message-ID: <0D1AF94E-D44E-4DDC-A6C0-D2471ABBF43D@ipfire.org> (raw)
In-Reply-To: <1377689181.19053.14.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 2259 bytes --]
Hi Michael,
Am 28.08.2013 um 13:26 schrieb Michael Tremer:
> 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-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 IPTraf-ng quits. Until now i couldn´t localize the problem, but it seems like a bug in the new version.
>> 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.
i have sent an mail to IPTraf mailinglist and i´am currently compile the patched iptraf-ng source with some fixes from the community. Hope this solves the problem, will let you know this after some testing results.
>
>> Beside info:
>> I have added an IPTraf-ng configuration for the logrotate.conf. In here --> http://git.ipfire.org/?p=people/ummeegge/ipfire-2.x.git;a=commit;h=16bcdaebca3586fda824e03822f82eecb796dc65 the diff can be found.
>
> 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´t know how much time it takes that the above mentioned patch will be provided in the official source code and also if it solves the problem.
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 needs also easy to use for further processing with shell scripting. The configuration window allows to activate or deactivate the logging, so i thought it might be a good idea to add it also in logrotate.conf.
>
> -Michael
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
next prev parent reply other threads:[~2013-08-28 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 11:13 Erik K.
2013-08-28 11:26 ` Michael Tremer
2013-08-28 18:03 ` Erik K. [this message]
[not found] <08D07391-C82C-4E50-93D2-807D084E17AF@ipfire.org>
2013-08-30 14:43 ` Erik K.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0D1AF94E-D44E-4DDC-A6C0-D2471ABBF43D@ipfire.org \
--to=ummeegge@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox