Bug 1045601
Summary: | Allow tcpdump to support libpcap nanosecond timestamping | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Dave Sullivan <dsulliva> | |
Component: | tcpdump | Assignee: | Michal Sekletar <msekleta> | |
Status: | CLOSED ERRATA | QA Contact: | BaseOS QE Security Team <qe-baseos-security> | |
Severity: | medium | Docs Contact: | Eva Majorsinova <emajorsi> | |
Priority: | medium | |||
Version: | 6.5 | CC: | amelicha, ebenes, hartsjc, kdube, msekleta | |
Target Milestone: | beta | Keywords: | FutureFeature | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | tcpdump-4.0.0-5.20090921gitdf3cb4.2.el6 | Doc Type: | Enhancement | |
Doc Text: |
tcpdump supports -J, -j, and --time-stamp-precision options
As kernel, glibc, and libpcap now provide APIs to obtain nanosecond resolutions timestamps, tcpdump has been updated to leverage this functionality. Users can now query which timestamp sources are available (-J), set a specific timestamp source (-j), and request timestamps with a specified resolution (--time-stamp-precision).
|
Story Points: | --- | |
Clone Of: | ||||
: | 1151406 (view as bug list) | Environment: | ||
Last Closed: | 2015-07-22 06:19:59 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 994246, 1075802, 1095797, 1159820, 1159926 |
Description
Dave Sullivan
2013-12-20 20:10:13 UTC
I sent patches for this upstream and topic is discussed here [0]. Should be merged soonish. Arghh...Link to the upstream discussion. [0] https://github.com/the-tcpdump-group/tcpdump/pull/377 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1294.html |