Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ez-ipupdate(8) [debian man page]

EZ-IPUPDATE(8)							Dynamic DNS client						    EZ-IPUPDATE(8)

NAME
ez-ipupdate - dynamic DNS client SYNOPSIS
ez-ipupdate [options] DESCRIPTION
This manual page documents briefly the ez-ipupdate dynamic DNS client. OPTIONS
ez-ipupdate follows the usual GNU command line syntax, with long options starting with two dashes (`-'). -a, --address <ip address> string to send as your ip address -b, --cache-file <file> file to use for caching the ipaddress -c, --config-file <file> configuration file, almost all arguments can be given with: <name>[=<value>] to see a list of possible config commands try "echo help | ez-ipupdate -c -" -d, --daemon run as a daemon periodicly updating if necessary -e, --execute <command> shell command to execute after a successful update -f, --foreground when running as a daemon run in the foreground -F, --pidfile <file> use <file> as a pid file -g, --request-uri <uri> URI to send updates to -h, --host <host> string to send as host parameter -i, --interface <iface> which interface to use -L, --cloak_title <host> some stupid thing for DHS only -m, --mx <mail exchange> string to send as your mail exchange -M, --max-interval <# of sec> max time in between updates -N, --notify-email <email> address to send mail to if bad things happen -o, --offline set to off line mode -p, --resolv-period <sec> period to check IP if it can't be resolved -P, --period <# of sec> period to check IP in daemon mode (default: 1800 seconds) -q, --quiet be quiet -r, --retrys <num> number of trys (default: 1) -R, --run-as-user <user> change to <user> for running, be ware that this can cause problems with handeling SIGHUP properly if that user can't read the config file. also it can't write it's pid file to a root directory -Q, --run-as-euser <user> change to effective <user> for running, this is NOT secure but it does solve the problems with run-as-user and config files and pid files. -s, --server <server[:port]> the server to connect to -S, --service-type <server> the type of service that you are using try one of: null ezip pgpow dhs dyndns dyndns-static dyndns-custom ods tzo easydns easydns- partner gnudip justlinux dyns hn zoneedit heipv6tb -t, --timeout <sec.millisec> the amount of time to wait on I/O -T, --connection-type <num> number sent to TZO as your connection type (default: 1) -U, --url <url> string to send as the url parameter -u, --user <user[:passwd]> user ID and password, if either is left blank they will be prompted for -w, --wildcard set your domain to have a wildcard alias -z, --partner <partner> specify easyDNS partner (for easydns-partner services) --help display this help and exit --version output version information and exit --credits print the credits and exit --signalhelp print help about signals AUTHOR
This manual page was written by Sam Hocevar <sam@zoy.org> for the Debian GNU/Linux system (but may be used by others). ez-ipupdate - 3.0.11b7 February 2003 EZ-IPUPDATE(8)

Check Out this Related Man Page

DHISD(8)						    BSD System Manager's Manual 						  DHISD(8)

NAME
dhisd -- Dynamic Host Information System server. SYNOPSIS
dhisd [-D] [-p port] [-d database] [-s services] [-l logfile] [-P pidfile] DESCRIPTION
DHIS is a client-server architecture meant to update databases for systems which are assigned a dynamic IP[v4] address. By the means of a DHIS client a host which is assigned a dynamic IP address (either from its ISP or from DHCP) is able to communicate with a DHIS server in order to advertise its newly acquired IP address. DHIS comprises a UDP based protocol to achieve this purpose. A DHIS client has a unique identification number and a set of authentication keys, runs in background, and attempts to reach its server. The DHIS server (permanently online) listens to UDP messages from its clients and authenticates these against its knowledge of keys. When authentication is successful the DHIS server updates one or more databases with the newly received IP address for the given client. The server then keeps sending, every period of time, check requests to each of its connected clients. These need to be acknowledged. If not the server will consider, on an individual basis, that the client has disconnected and will again update the databases to an offline state. Alternativelly the server may receive an OFFLINE_REQ packet from the client, in which case the DNS record is updated at once and the online state droped. OPTIONS
-D Increase debug level. -p port Specify port to listen on. If not specified, the default is port 58800. -d database Use an alternative database file instead of /etc/dhis-server/dhis.db. -s services Use an alternative database file instead of /etc/dhis-server/services.db. -l logfile Use an alternative log file instead of /var/log/dhisd.log. -P pidfile Use an alternative PID file instead of /var/run/dhisd.pid. FILES
/etc/dhis-server/dhis.db DHIS client database. Contains the credentials of clients. /etc/dhis-server/services.db DHIS service database. Contains a list of services and the location of the corresponding DHIS engine plugins. SEE ALSO
dhis-genkeys(8) AUTHOR
dhisd has been written by Joao Cabral <jcnc@dhis.org>. This manual page was written by Guus Sliepen <guus@debian.org> for the Debian GNU/Linux system. Debian GNU/Linux June 1, 2019 Debian GNU/Linux
Man Page