aboutsummaryrefslogtreecommitdiff
path: root/contrib/traceroute/README
diff options
context:
space:
mode:
Diffstat (limited to 'contrib/traceroute/README')
-rw-r--r--contrib/traceroute/README8
1 files changed, 4 insertions, 4 deletions
diff --git a/contrib/traceroute/README b/contrib/traceroute/README
index fa789ed52b43..bd4df4cb8295 100644
--- a/contrib/traceroute/README
+++ b/contrib/traceroute/README
@@ -1,10 +1,10 @@
-@(#) $Header: README,v 1.7 96/07/06 02:08:32 leres Exp $ (LBL)
+@(#) $Id: README,v 1.9 2000/09/16 05:32:01 leres Exp $ (LBL)
-TRACEROUTE 1.3
+TRACEROUTE 1.4
Lawrence Berkeley National Laboratory
Network Research Group
traceroute@ee.lbl.gov
-ftp://ftp.ee.lbl.gov/traceroute.tar.Z
+ftp://ftp.ee.lbl.gov/traceroute.tar.gz
Traceroute is a system administrators utility to trace the route
ip packets from the current system take in getting to some
@@ -19,7 +19,7 @@ included. "mean.awk" and "median.awk" compute the mean and median time
to each hop, respectively. I've found that something like
traceroute -q 7 foo.somewhere >t
- awk -f median.awk t | graph
+ awk -f median.awk t | xgraph
can give you a quick picture of the bad spots on a long path (median is
usually a better noise filter than mean).