summaryrefslogtreecommitdiff
path: root/doc/dahdi_test.8
diff options
context:
space:
mode:
authorKevin P. Fleming <kpfleming@digium.com>2008-08-06 22:35:50 +0000
committerKevin P. Fleming <kpfleming@digium.com>2008-08-06 22:35:50 +0000
commitcbb14417fc15739925bdfb387f28df90f155219d (patch)
treed2e04374892793a262263c6404b0538a61afd108 /doc/dahdi_test.8
parentc401b656501abb34fbdeb38c3653d12e313f06ff (diff)
various updates to man pages
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@4732 a0bf4364-ded3-4de4-8d8a-66a801d63aff
Diffstat (limited to 'doc/dahdi_test.8')
-rw-r--r--doc/dahdi_test.86
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/dahdi_test.8 b/doc/dahdi_test.8
index c61f0f6..21cda80 100644
--- a/doc/dahdi_test.8
+++ b/doc/dahdi_test.8
@@ -1,6 +1,6 @@
.TH dahdi_test 8 "2005-06-25"
.SH "NAME"
-dahdi_test \(em Test if the dahdi timer provides timely response
+dahdi_test \(em Test if the DAHDI timer provides timely response
.SH "SYNOPSIS"
.B dahdi_test
.I [ -v ]
@@ -10,7 +10,7 @@ dahdi_test \(em Test if the dahdi timer provides timely response
dahdi_test runs a timing test in a loop and prints the result of each loop.
The test is as follows:
-It reads 8192 bytes from the dahdi timer device (\fI/dev/dahdi/pseudo\fR).
+It reads 8192 bytes from the DAHDI timer device (\fI/dev/dahdi/pseudo\fR).
This should take exactly 8000 ms . It uses calls to
.I gettimeofday(2)
before and after that read to check that indeed exactly 8000ms have passed.
@@ -37,7 +37,7 @@ times instead of running forever.
.B /dev/dahdi/pseudo
.RS
.RE
-The device file used to access the dahdi timer.
+The device file used to access the DAHDI timer.
.SH SEE ALSO
dahdi_tool(8), dahdi_cfg(8), asterisk(8). gettimeofday(2)