mirror of https://framagit.org/bortzmeyer/echoping
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
34 lines
1.4 KiB
Plaintext
34 lines
1.4 KiB
Plaintext
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)
|
|
--disable-ttcp (suppress the T/TCP support which is enabled only if
|
|
your system supports it - FreeBSD does. See
|
|
<http://www.kohala.com/start/ttcp.html>)
|
|
|
|
|
|
If 'echoping -h' fails with "tcp_open: unknown service:
|
|
undefined:use_:80/tcp",it means configure was not able to find a port
|
|
name for the HTTP protocol. Complain to your vendor and add by hand
|
|
"http" to the services database (typically /etc/services or a NIS
|
|
map). Its value is 80. Or, hack (warning: it's a hack) config.h to
|
|
change HTTP_TCP_PORT from "undefined:use_:80" to "www" or whatever is
|
|
defined on your system. A good 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").
|
|
|
|
$Id$
|
|
|
|
|
|
|