From f7f65478b89f314b854566f8daa8f5d54db73f57 Mon Sep 17 00:00:00 2001 From: Tzafrir Cohen Date: Mon, 16 Jun 2008 18:09:11 +0000 Subject: Add man pages based on Zaptel's man pages. git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@4368 a0bf4364-ded3-4de4-8d8a-66a801d63aff --- doc/dahdi_test.8 | 49 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 49 insertions(+) create mode 100644 doc/dahdi_test.8 (limited to 'doc/dahdi_test.8') diff --git a/doc/dahdi_test.8 b/doc/dahdi_test.8 new file mode 100644 index 0000000..c61f0f6 --- /dev/null +++ b/doc/dahdi_test.8 @@ -0,0 +1,49 @@ +.TH dahdi_test 8 "2005-06-25" +.SH "NAME" +dahdi_test \(em Test if the dahdi timer provides timely response +.SH "SYNOPSIS" +.B dahdi_test +.I [ -v ] + +.SH DESCRIPTION +.B dahdi_test +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). +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. + +Values of 100% and 99.99% Are normally considered a definite +.I pass. +Values of 99.98% and 99.97% are probably OK as well. + +.SH OPTIONS +.B -v +.RS +Be more verbose: print one line per test. +.RE + +.B -c +.I count +.RS +Run for +.I count +times instead of running forever. +.RE + +.SH FILES +.B /dev/dahdi/pseudo +.RS +.RE +The device file used to access the dahdi timer. + +.SH SEE ALSO +dahdi_tool(8), dahdi_cfg(8), asterisk(8). gettimeofday(2) + +.SH AUTHOR +This manual page was written by Tzafrir Cohen +Permission is granted to copy, distribute and/or modify this document under +the terms of the GNU General Public License, Version 2 any +later version published by the Free Software Foundation. -- cgit v1.2.3