Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

rec_control(1) [debian man page]

REC_CONTROL(1)							  [FIXME: manual]						    REC_CONTROL(1)

NAME

       rec_control - control pdns_recursor

SYNOPSIS

       rec_control [--help] [--socket-dir] [--socket-pid] command ..

DESCRIPTION

       rec_control(1) allows the operator to control a running instance of the pdns_recursor.

       The commands that can be passed to the recursor are described on http://doc.powerdns.com/rec-control.html

EXAMPLES

       To stop the recursor by hand, run:

	   # rec_control quit

       To dump the cache to disk, execute:

	   # rec_control dump-cache /tmp/the-cache

OPTIONS

       --help
	   provide this helpful message

       --socket-dir
	   Where the controlsocket will live

       --socket-pid
	   When running in SMP mode, pid of pdns_recursor to control

       --timeout
	   Number of seconds to wait for the remote PowerDNS Recursor to respond. Set to 0 for infinite.

COMMANDS

       dump-cache filename
	   Dumps the entire cache to the filename mentioned. This file should not exist already, PowerDNS will refuse to overwrite it. While
	   dumping, the recursor will not answer questions.

       get statistic
	   Retrieve a statistic. For items that can be queried, see http://doc.powerdns.com/recursor-stats.html

       get-all
	   Retrieve all known statistics.

       ping
	   Check if server is alive.

       quit
	   Request shutdown of the recursor

       reload-zones
	   Reload authoritative and forward zones. Retains current configuration in case of errors.

       top-remotes
	   Shows the top-20 most active remote hosts. Statistics are over the last remotes-ringbuffer-entries queries, which defaults to 0.

       wipe-cache domain0 [domain1]
	   Wipe entries from the cache. This is useful if, for example, an important server has a new IP address, but the TTL has not yet expired.
	   Multiple domain names can be passed. Note that you must terminate a domain with a .! So to wipe powerdns.org, issue rec_control
	   wipe-cache powerdns.org.. Versions beyond 3.1 don't need the trailing dot. Consider not only wiping www.domain.com.	but also
	   domain.com., as the cached nameservers or target of CNAME may continue to be undesired.

BUGS

       None known. File new ones at http://wiki.powerdns.com.

AUTHOR

       Written by PowerDNS.COM BV, bert hubert, <bert.hubert@netherlabs.nl[1]>

RESOURCES

       Website: http://wiki.powerdns.com, http://www.powerdns.com

SEE ALSO

       pdns_recursor(1)

COPYING

       Copyright (C) 2006 PowerDNS.COM BV. Free use of this software is granted under the terms of the GNU General Public License (GPL) version 2.

NOTES

	1. bert.hubert@netherlabs.nl
	   mailto:bert.hubert@netherlabs.nl

[FIXME: source] 						    08/30/2010							    REC_CONTROL(1)

Check Out this Related Man Page

GIT-CREDENTIAL-CAC(1)						    Git Manual						     GIT-CREDENTIAL-CAC(1)

NAME

       git-credential-cache - Helper to temporarily store passwords in memory

SYNOPSIS

       git config credential.helper 'cache [options]'

DESCRIPTION

       This command caches credentials in memory for use by future Git programs. The stored credentials never touch the disk, and are forgotten
       after a configurable timeout. The cache is accessible over a Unix domain socket, restricted to the current user by filesystem permissions.

       You probably don't want to invoke this command directly; it is meant to be used as a credential helper by other parts of Git. See
       gitcredentials(7) or EXAMPLES below.

OPTIONS

       --timeout <seconds>
	   Number of seconds to cache credentials (default: 900).

       --socket <path>
	   Use <path> to contact a running cache daemon (or start a new cache daemon if one is not started). Defaults to
	   $XDG_CACHE_HOME/git/credential/socket unless ~/.git-credential-cache/ exists in which case ~/.git-credential-cache/socket is used
	   instead. If your home directory is on a network-mounted filesystem, you may need to change this to a local filesystem. You must specify
	   an absolute path.

CONTROLLING THE DAEMON

       If you would like the daemon to exit early, forgetting all cached credentials before their timeout, you can issue an exit action:

	   git credential-cache exit

EXAMPLES

       The point of this helper is to reduce the number of times you must type your username or password. For example:

	   $ git config credential.helper cache
	   $ git push http://example.com/repo.git
	   Username: <type your username>
	   Password: <type your password>

	   [work for 5 more minutes]
	   $ git push http://example.com/repo.git
	   [your credentials are used automatically]

       You can provide options via the credential.helper configuration variable (this example drops the cache time to 5 minutes):

	   $ git config credential.helper 'cache --timeout=300'

GIT

       Part of the git(1) suite

Git 2.17.1							    10/05/2018						     GIT-CREDENTIAL-CAC(1)
Man Page