diff options
| author | Michal Sekletar <sekletar.m@gmail.com> | 2014-03-19 14:14:25 +0100 |
|---|---|---|
| committer | Michal Sekletar <msekleta@redhat.com> | 2014-05-14 14:18:40 +0200 |
| commit | 52b27d11fc50ebc4f1fc54b53fd9437d62dd7f4a (patch) | |
| tree | 1e95f1125270c58cbfb3fec0a5591301e7715f8b /tcpdump.1.in | |
| parent | 86f3cae06d11516a3c22959a7b2b53bbaaa161d5 (diff) | |
| download | tcpdump-52b27d11fc50ebc4f1fc54b53fd9437d62dd7f4a.tar.gz | |
Introduce --time-stamp-precision
A while ago we introduced new API in libpcap which made possible to
request time stamps with higher precision (nanoseconds). This commit
aims to move things forward and implement missing bits. It introduces
new long option --time-stamp-precision. Note that there is no equivalent
short option.
When used for a live capture tcpdump will ask the kernel for time stamp
with desired precision and tcpdump will print fraction part of the time
stamp using respective format. We currently support only microsecond and
nanosecond precision. In the future we might support even more granular
time stamp precision, but we should be fine to support only
microseconds and nanoseconds for now. libpcap doesn't provide anything
else at the moment anyway.
When used in combination with -r/-w options then we obtain time stamps
appropriately scaled up or down from libpcap. Also note that distinct
magic number is used for savefiles containing nanosecond time stamps.
Diffstat (limited to 'tcpdump.1.in')
| -rw-r--r-- | tcpdump.1.in | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/tcpdump.1.in b/tcpdump.1.in index b1867419..3cceb468 100644 --- a/tcpdump.1.in +++ b/tcpdump.1.in @@ -432,6 +432,15 @@ List the supported time stamp types for the interface and exit. If the time stamp type cannot be set for the interface, no time stamp types are listed. .TP +.BI \-\-time\-stamp\-precision= tstamp_precision +.PD +Set the time stamp precision for the capture to +\fItstamp_precision\fP. Currently supported are microseconds and +nanoseconds. Note that availability of high precision time stamps (nanoseconds) +and their actual accuracy is platform and HW dependent. Also note that when +writing captures to the savefile, distinct magic number is used to distinguish +savefiles which contains time stamps in nanoseconds. +.TP .B \-K .PD 0 .TP |