clockdiff.8 2.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182
  1. .\" This manpage has been automatically generated by docbook2man
  2. .\" from a DocBook document. This tool can be found at:
  3. .\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
  4. .\" Please send any bug reports, improvements, comments, patches,
  5. .\" etc. to Steve Cheng <steve@ggi-project.org>.
  6. .TH "CLOCKDIFF" "8" "24 Mayıs 2011" "iputils-101006" "System Manager's Manual: iputils"
  7. .SH NAME
  8. clockdiff \- measure clock difference between hosts
  9. .SH SYNOPSIS
  10. \fBclockdiff\fR [ \fB-o\fR] [ \fB-o1\fR] \fB\fIdestination\fB\fR
  11. .SH "DESCRIPTION"
  12. .PP
  13. \fBclockdiff\fR Measures clock difference between us and
  14. \fIdestination\fR with 1 msec resolution using ICMP TIMESTAMP
  15. [2]
  16. packets or, optionally, IP TIMESTAMP option
  17. [3]
  18. option added to ICMP ECHO.
  19. [1]
  20. .SH "OPTIONS"
  21. .TP
  22. \fB-o\fR
  23. Use IP TIMESTAMP with ICMP ECHO instead of ICMP TIMESTAMP
  24. messages. It is useful with some destinations, which do not support
  25. ICMP TIMESTAMP (f.e. Solaris <2.4).
  26. .TP
  27. \fB-o1\fR
  28. Slightly different form of \fB-o\fR, namely it uses three-term
  29. IP TIMESTAMP with prespecified hop addresses instead of four term one.
  30. What flavor works better depends on target host. Particularly,
  31. \fB-o\fR is better for Linux.
  32. .SH "WARNINGS"
  33. .TP 0.2i
  34. \(bu
  35. Some nodes (Cisco) use non-standard timestamps, which is allowed
  36. by RFC, but makes timestamps mostly useless.
  37. .TP 0.2i
  38. \(bu
  39. Some nodes generate messed timestamps (Solaris>2.4), when
  40. run \fBxntpd\fR. Seems, its IP stack uses a corrupted clock source,
  41. which is synchronized to time-of-day clock periodically and jumps
  42. randomly making timestamps mostly useless. Good news is that you can
  43. use NTP in this case, which is even better.
  44. .TP 0.2i
  45. \(bu
  46. \fBclockdiff\fR shows difference in time modulo 24 days.
  47. .SH "SEE ALSO"
  48. .PP
  49. \fBping\fR(8),
  50. \fBarping\fR(8),
  51. \fBtracepath\fR(8).
  52. .SH "REFERENCES"
  53. .PP
  54. [1] ICMP ECHO,
  55. RFC0792, page 14.
  56. .PP
  57. [2] ICMP TIMESTAMP,
  58. RFC0792, page 16.
  59. .PP
  60. [3] IP TIMESTAMP option,
  61. RFC0791, 3.1, page 16.
  62. .SH "AUTHOR"
  63. .PP
  64. \fBclockdiff\fR was compiled by
  65. Alexey Kuznetsov
  66. <kuznet@ms2.inr.ac.ru>. It was based on code borrowed
  67. from BSD \fBtimed\fR daemon.
  68. It is now maintained by
  69. YOSHIFUJI Hideaki
  70. <yoshfuji@skbuff.net>.
  71. .SH "SECURITY"
  72. .PP
  73. \fBclockdiff\fR requires CAP_NET_RAWIO capability
  74. to be executed. It is safe to be used as set-uid root.
  75. .SH "AVAILABILITY"
  76. .PP
  77. \fBclockdiff\fR is part of \fIiputils\fR package
  78. and the latest versions are available in source form at
  79. http://www.skbuff.net/iputils/iputils-current.tar.bz2.