tcptrace csv format does not format number properly

Bug #1428828 reported by De Coninck
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tcptrace (Ubuntu)
New
Undecided
Unassigned

Bug Description

When I analyze a connection using 'tcptrace -n -l -r', I get for instance

...
TCP connection 20:
 host am: 192.168.1.190:34086
 host an: 37.187.114.90:995
 complete conn: no (SYNs: 2) (FINs: 0)
 first packet: Fri Feb 20 04:49:22.092902 2015
 last packet: Fri Feb 20 04:49:22.335740 2015
 elapsed time: 0:00:00.242838
...

But if I add the option --csv ('tcptrace -n -l -r --csv', I get

conn_#,host_a,host_b,port_a,port_b,first_packet,last_packet,...
...
20,192.168.1.190,37.187.114.90,34086,995,1424404162.92902 , 1424404162.335740 , ...

In other words, the 0 just after the decimal goes away for the first packet attribute, and instead of having 1424404162.092902, we have 1424404162.92902. The same remark applies for last packet

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: tcptrace 6.6.7-4.1
ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Thu Mar 5 21:06:04 2015
InstallationDate: Installed on 2014-12-26 (68 days ago)
InstallationMedia: Cubuntu 14.04.182 LTS - Release amd64
SourcePackage: tcptrace
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
De Coninck (quentindeco54) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.