← Back to team overview

rohc team mailing list archive

Re: Tunnel tool ping error

 

Josephine,

> > In practice, to retrieve all the information, you may start the
> > rohctunnel tool as follow:
> >  # rohctunnel <parameters> \
> >     1> rohc_library.log \
> >     2> rohc_tunnel.log \
> >     3> rohc_comp.stats \
> >     4> rohc_decomp.stats
> > And have a look at content written in the 4 log files.
> 
> I used the redirection commands above, but while rohc_library.log and
> rohc_tunnel.log did contain information, both rohc_comp.stats and
> rohc_decomp.stats remained empty.

The system bufferizes the messages for performance reasons, so they are
not written to the files immediately. I you wait some time or stop the
rochtunnel tool, they should be flushed and you should then see them in
the files rohc_comp.stats and rohc_decomp.stats.

The problem may be definitively corrected by forcing the system to
flush the statistics messages to disk after every new line. I opened a
bug in the bugtracker and fixed the problem in the 1.2.x branch and in
the trunk. See https://bugs.launchpad.net/rohc/trunk/+bug/414032

In order to get the correction, you may retrieve the latest version
of the 1.2.x branch or apply the attached patch to the source code you
already have. Thank you for reporting the problem.

Regards,

Didier Barvaux
Viveris Technologies
=== modified file 'app/tunnel/tunnel.c'
--- app/tunnel/tunnel.c	2009-08-04 13:45:24 +0000
+++ app/tunnel/tunnel.c	2009-08-15 12:42:49 +0000
@@ -1044,6 +1044,7 @@
 	        comp->last_context->total_last_compressed_size,
 	        comp->last_context->header_last_compressed_size,
 	        dropped);
+	fflush(stats_comp);
 
 quit:
 	return 0;
@@ -1074,6 +1075,7 @@
 	fprintf(stats_decomp, "%u\t%d\t%u\t%d\n", seq,
 	        lost_packets + decomp->last_context->num_decomp_failures,
 	        lost_packets, decomp->last_context->num_decomp_failures);
+	fflush(stats_decomp);
 
 	return 0;
 


Follow ups

References