I also couldn't reproduce this bug.
In a bionic VM, I installed iptraf-ng 1:1.1.4-6:
root@ubuntu:/var/log/iptraf# apt-cache policy iptraf-ng
iptraf-ng:
Installed: 1:1.1.4-6
Candidate: 1:1.1.4-6
Version table:
*** 1:1.1.4-6 500
500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
root@ubuntu:/var/log/iptraf#
I created /var/log/iptraf, entered the UI, enabled logging in the config. When
starting the monitor, it prompted me for the log file, where I had to correct
the log directory (from iptraf-ng to iptraf), but after that, it ran just fine
and produced the logfile I indicated:
# ll /var/log/iptraf/
total 12
drwxr-xr-x 2 root root 4096 Jul 9 20:40 ./
drwxrwxr-x 9 root syslog 4096 Jul 9 20:39 ../
-rw-r--r-- 1 root root 360 Jul 9 20:40 andreas.log
I agree that the log directory not being created is a bug. It's even mentioned
in the shipped logrotate file:
root@ubuntu:/var/log/iptraf# cat /etc/logrotate.d/iptraf-ng
# Logrotate file for iptraf
/var/log/iptraf/*.log {
compress
delaycompress
missingok
notifempty
rotate 4
create 0600 root root
}
Did you check if your crash produced a crash file in /var/crash? If yes,
please upload it to this bug, so we can take a look at the core dump
file. It may be related to the type of traffic you are seeing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778959
Title:
error floating point exception
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptraf-ng/+bug/1778959/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
