|
|
|
|
echoping appears to compile and run at least on Tru64 (ex-Digital
|
|
|
|
|
Unix, ex-OSF/1), Solaris, Linux, SunOS, FreeBSD, IRIX and Ultrix. You
|
|
|
|
|
do not have to be root to install it.
|
|
|
|
|
|
|
|
|
|
Just type "./configure", then "make", and then (as root if necessary),
|
|
|
|
|
"make install".
|
|
|
|
|
|
|
|
|
|
"configure" has some options:
|
|
|
|
|
--disable-http (suppress the HTTP support)
|
|
|
|
|
--enable-icp (add the ICP support, to monitor Web proxies like Squid)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Variables you may add in echoping.h:
|
|
|
|
|
|
|
|
|
|
TTCP
|
|
|
|
|
T/TCP support if your system supports it (FreeBSD does). See
|
|
|
|
|
<http://www.noao.edu/~rstevens/ttcp.html>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If 'echoping -h' fails with "tcp_open: unknown service: http/tcp", add
|
|
|
|
|
"http" to the services database (typically /etc/services or a NIS map).
|
|
|
|
|
Its value is 80. Or, change HTTP_TCP_PORT in echoping.h from "http" to "www"
|
|
|
|
|
or whatever is defined on your system (at least AIX or Solaris have the
|
|
|
|
|
problem). A workaround is to specify the port on the command line:
|
|
|
|
|
echoping -h / www.mydomain.org:80
|
|
|
|
|
|
|
|
|
|
If 'echoping -h' replies with a "404" error while the file really exists,
|
|
|
|
|
check first that you use the FQDN of the server on the command line
|
|
|
|
|
(this is a consequence of the HTTP 1.1 protocol, not a bug in echoping
|
|
|
|
|
and this will show only if the HTTP server uses "virtual hosting").
|
|
|
|
|
|
