Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages

  
 
  

home | help
bsdiff(1)
generate a patch between two binary files
bspatch(1)
apply a patch built with bsdiff(1)
freebsd-version(1)
print the version and patch level of the installed system
netisr(9)
Kernel network dispatch service
ng_patch(4)
trivial mbuf data modifying netgraph node type
nsdispatch(3)
name-service switch dispatcher routine
patch(1)
apply a diff file to an original
pcap_breakloop(3)
force a pcap_dispatch() or pcap_loop() call to return
pcap_loop(3), pcap_dispatch(3)
process packets from a live capture or savefile
MPIX_Win_shared_query(3)
Query the size and base pointer for a patch of a shared memory window
MPI_Win_shared_query(3)
Query the size and base pointer for a patch of a shared memory window
OPENSSL_VERSION_MAJOR(3ossl), OPENSSL_VERSION_MINOR(3ossl), OPENSSL_VERSION_PATCH(3ossl), OPENSSL_VERSION_PRE_RELEASE(3ossl), OPENSSL_VERSION_BUILD_METADATA(3ossl), OPENSSL_VERSION_TEXT(3ossl), OPENSSL_VERSION_PREREQ(3ossl), OPENSSL_version_major(3ossl), OPENSSL_version_minor(3ossl), OPENSSL_version_patch(3ossl), OPENSSL_version_pre_release(3ossl), OPENSSL_version_build_metadata(3ossl), OpenSSL_version(3ossl), OPENSSL_VERSION_NUMBER(3ossl), OpenSSL_version_num(3ossl), OPENSSL_info(3ossl)
get OpenSSL version number and other information
OSSL_LIB_CTX(3ossl), OSSL_LIB_CTX_new(3ossl), OSSL_LIB_CTX_new_from_dispatch(3ossl), OSSL_LIB_CTX_new_child(3ossl), OSSL_LIB_CTX_free(3ossl), OSSL_LIB_CTX_load_config(3ossl), OSSL_LIB_CTX_get0_global_default(3ossl), OSSL_LIB_CTX_set0_default(3ossl)
OpenSSL library context
OSSL_PROVIDER_set_default_search_path(3ossl), OSSL_PROVIDER(3ossl), OSSL_PROVIDER_load(3ossl), OSSL_PROVIDER_try_load(3ossl), OSSL_PROVIDER_unload(3ossl), OSSL_PROVIDER_available(3ossl), OSSL_PROVIDER_do_all(3ossl), OSSL_PROVIDER_gettable_params(3ossl), OSSL_PROVIDER_get_params(3ossl), OSSL_PROVIDER_query_operation(3ossl), OSSL_PROVIDER_unquery_operation(3ossl), OSSL_PROVIDER_get0_provider_ctx(3ossl), OSSL_PROVIDER_get0_dispatch(3ossl), OSSL_PROVIDER_add_builtin(3ossl), OSSL_PROVIDER_get0_name(3ossl), OSSL_PROVIDER_get_capabilities(3ossl), OSSL_PROVIDER_self_test(3ossl)
provider routines
Sympa::Spindle::DispatchRequest(3Sympa)
Workflow to dispatch requests
XmtPatchVisualInheritance(3), XmtPatchVisualInheritance()(3)
apply a runtime patch to the Shell widget class so that it handles non-default visuals better
XtAppNextEvent(3), XtAppPending(3), XtAppPeekEvent(3), XtAppProcessEvent(3), XtDispatchEvent(3), XtAppMainLoop(3)
query and process events and input
XtInsertEventTypeHandler(3), XtRemoveEventTypeHandler(3), XtRegisterExtensionSelector(3), XtSetEventDispatcher(3), XtDispatchEventToWidget(3)
extension event handling
XtRegisterDrawable(3)
register a drawable with the Intrinsics event dispatcher
aepatch(1)
send and receive changes as patches
argc.tcl86(n), argc(n), argv(n), argv0(n), auto_path(n), env(n), errorCode(n), errorInfo(n), tcl_interactive(n), tcl_library(n), tcl_nonwordchars(n), tcl_patchLevel(n), tcl_pkgPath(n), tcl_platform(n), tcl_precision(n), tcl_rcFileName(n), tcl_traceCompile(n), tcl_traceExec(n), tcl_wordchars(n), tcl_version(n)
Variables used by Tcl
argc.tcl87(n), argc(n), argv(n), argv0(n), auto_path(n), env(n), errorCode(n), errorInfo(n), tcl_interactive(n), tcl_library(n), tcl_nonwordchars(n), tcl_patchLevel(n), tcl_pkgPath(n), tcl_platform(n), tcl_precision(n), tcl_rcFileName(n), tcl_traceCompile(n), tcl_traceExec(n), tcl_wordchars(n), tcl_version(n)
Variables used by Tcl
bpatch(1)
binary patch and dump file utility
calico(1)
dispatches cat
ck_epoch_barrier(3)
block until a grace period and all callbacks have been dispatched
ck_epoch_poll(3)
non-blocking poll of epoch object for dispatch cycles
cmap_dispatch(3)
Dispatches callbacks from the CMAP service
cmap_fd_get(3)
Dispatches callbacks from the CMAP service
commit-patch(1)
commit patches to Darcs, Git, Mercurial, Bazaar, Monotone, Subversion, or CVS repositories
cpg_dispatch(3)
Dispatches callbacks from the CPG service
cpg_fd_get(3)
Dispatches callbacks from the CPG service
cvsps(1), CVSps(1)
create patchset information from CVS
diff2php(1)
transform a patch into a self-serving PHP file
dot(1)
filter for drawing directed graphs neato - filter for drawing undirected graphs twopi - filter for radial layouts of graphs circo - filter for circular layout of graphs fdp - filter for drawing undirected graphs sfdp - filter for drawing large undirected graphs patchwork - filter for squarified tree maps osage - filter for array-based layouts
ezmlm-dispatch(1)
Dispatch an email to other ezmlm programs
genpatch(1)
generate patch quickly in standard FreeBSD ports format
geometry.tk86(n), geometry(n), tk_library(n), tk_patchLevel(n), tk_strictMotif(n), tk_version(n)
Variables used or set by Tk
gh-workflow-run(1)
Run a workflow by creating a workflow_dispatch event
git-am(1)
Apply a series of patches from a mailbox
git-apply(1)
Apply a patch to files and/or to the index
git-format-patch(1)
Prepare patches for e-mail submission
git-imap-send(1)
Send a collection of patches from stdin to an IMAP folder
git-mailinfo(1)
Extracts patch and authorship from a single e-mail message
git-paste(1)
Send patches to pastebin for chat conversations
git-patch-id(1)
Compute unique ID for a patch
git-quiltimport(1)
Applies a quilt patchset onto the current branch
git-rebase-patch(1)
Rebases a patch
git-send-email(1)
Send a collection of patches as emails
gpatch(1), patch(1)
apply a diff file to an original
hwloc-patch(1)
Apply a topology difference to an existing XML topology
icepatch2calc(1)
IcePatch2 tool to compress files and calculate checksums
icepatch2client(1)
The IcePatch2 client
icepatch2server(1)
The IcePatch2 server
kldpatch(8)
print/modify device/quirk tables in kernel modules
load_ibk(3)
Reads in a .IBK patch definition file for the Adlib driver. Allegro game programming library
load_midi_patches(3)
Forces the MIDI driver to load a set of patches. Allegro game programming library
maildist(1), mailhelp(1), maillist(1), mailpatch(1)
mailagent's commands
mission-control-5(8)
Telepathy account manager/chanel dispatcher
ne_request_create(3), ne_request_dispatch(3), ne_request_destroy(3)
low-level HTTP request handling
openssl-core_dispatch.h(7ossl), openssl/core_dispatch.h(7ossl)
OpenSSL provider dispatch numbers and function types
patch-metamail(1)
Install a patch to the latest metamail release
patchelf(1)
Modify ELF files
patchwork(1)
filter for drawing clustered graphs as treemaps
pcap_breakloop(3)
force a pcap_dispatch() or pcap_loop() call to return
pcap_loop(3), pcap_dispatch(3)
process packets from a live capture or savefile
portfix(1)
macro to execute three programs to create a ports patch
pycocci(1)
Coccinelle wrapper for SmPL patch development pycocci [-h | --help] [-p | --profile-cocci] [-j | --jobs <job-digit> ] [-v | --verbose] [-s | --show-proof] <SmPL-patch.cocci> <target> ]
quilt(1)
tool to manage series of patches
quorum_dispatch(3)
Dispatches callbacks from the quorum service
quorum_fd_get(3)
Dispatches callbacks from the quorum service
regpatch(1)
Applies registry patches to registry files
rlepatch(1)
patch smaller RLE files over a larger image
rodent-diff(1), Rodent-diff(1)
Graphic interface to the GNU diff and patch commands
spatch(1)
apply a semantic patch file to a set of C files
spd-conf(1)
configure Speech Dispatcher and diagnose problems
spd-say(1)
send text-to-speech output request to speech-dispatcher
speech-dispatcher(1)
speech synthesis daemon
spgen(1)
harden a Coccinelle semantic patch spgen <SmPL-patch.cocci> [-c | --config <spgen config>] [-i | --interactive] [--default] [-o <output file>] [--no-output] [-help | --help]
splitpatch(1)
split a patch up into files or hunks
votequorum_dispatch(3)
Dispatches callbacks from the votequorum service
votequorum_fd_get(3)
Dispatches callbacks from the votequorum service
wiggle(1)
apply rejected patches and perform word-wise diffs
xdiff(3), xdl_set_allocator(3), xdl_malloc(3), xdl_free(3), xdl_realloc(3), xdl_init_mmfile(3), xdl_free_mmfile(3), xdl_mmfile_iscompact(3), xdl_seek_mmfile(3), xdl_read_mmfile(3), xdl_write_mmfile(3), xdl_writem_mmfile(3), xdl_mmfile_writeallocate(3), xdl_mmfile_ptradd(3), xdl_mmfile_first(3), xdl_mmfile_next(3), xdl_mmfile_size(3), xdl_mmfile_cmp(3), xdl_mmfile_compact(3), xdl_diff(3), xdl_patch(3), xdl_merge3(3), xdl_bdiff_mb(3), xdl_bdiff(3), xdl_rabdiff_mb(3), xdl_rabdiff(3), xdl_bdiff_tgsize(3), xdl_bpatch(3)
File Differential Library support functions
zdir_patch(3)
Class for work with directory patches
Amon2::Plugin::LogDispatch(3)
Log::Dispatch glue for Amon2
Amon2::Web::Dispatcher::Lite(3)
Sinatra like dispatcher for Amon2
Amon2::Web::Dispatcher::RouterBoom(3)
Router::Boom bindings
Amon2::Web::Dispatcher::RouterSimple(3)
Router::Simple binding for Amon2
App::CLI(3)
Dispatcher module for command line interface programs
App::Cmd::Subdispatch(3)
an App::Cmd::Command that is also an App::Cmd
App::Cmd::Subdispatch::DashedStyle(3)
"app cmd --subcmd" style subdispatching
Bread::Board::Manual::Example::LogDispatch(3)
An example of composing a dynamic Log::Dispatch object
CGI::Application::Dispatch(3)
Dispatch requests to CGI::Application based objects
CGI::Application::Dispatch::PSGI(3)
Dispatch requests to CGI::Application based objects using PSGI
CGI::Application::Dispatch::Regexp(3)
Dispatch requests to CGI::Application based objects using regular expressions
CGI::Application::Dispatch::Server(3)
A simple HTTP server for developing with CGI::Application::Dispatch
CGI::Application::Plugin::LogDispatch(3)
Add Log::Dispatch support to CGI::Application
Catalyst::Action::REST(3)
Automated REST Method Dispatching
Catalyst::Action::REST::ForBrowsers(3)
Automated REST Method Dispatching that Accommodates Browsers
Catalyst::Action::SOAP::RPCEndpoint(3)
RPC Dispatcher
Catalyst::Controller::SRU(3)
Dispatch SRU methods with Catalyst
Catalyst::DispatchType(3)
DispatchType Base Class
Catalyst::DispatchType::Chained(3)
Path Part DispatchType
Catalyst::DispatchType::Default(3)
Default DispatchType
Catalyst::DispatchType::Index(3)
Index DispatchType
Catalyst::DispatchType::LocalRegex(3)
LocalRegex DispatchType
Catalyst::DispatchType::LocalRegexp(3)
LocalRegexp DispatchType
Catalyst::DispatchType::Path(3)
Path DispatchType
Catalyst::DispatchType::Regex(3)
Regex DispatchType
Catalyst::DispatchType::Regexp(3)
Regex DispatchType
Catalyst::Dispatcher(3)
The Catalyst Dispatcher
Catalyst::Exception::Detach(3)
Exception for redispatching using $ctx->detach()
Catalyst::Exception::Go(3)
Exception for redispatching using $ctx->go()
Catalyst::Plugin::Log::Dispatch(3)
Log module of Catalyst that uses Log::Dispatch
Catalyst::Plugin::Server::XMLRPC::DispatchType::XMLRPCPath(3)
XMLRPCPath DispatchType
Catalyst::Plugin::Server::XMLRPC::DispatchType::XMLRPCRegex(3)
XMLRPCRegex DispatchType
Catalyst::Plugin::XMLRPC(3)
DEPRECATED Dispatch XMLRPC methods with Catalyst
Catalyst::Plugin::XMLRPC::DispatchType::XMLRPC(3)
XMLRPC DispatchType
Class::Forward(3)
Namespace Dispatch and Resolution
Class::MixinFactory::NEXT(3)
Superclass method redispatch for mixins
Class::Multimethods::Pure(3)
Method-ordered multimethod dispatch
DNS::nsdiff(3pm)
the nsdiff, nspatch, and nsvi scripts
Dancer2::Core::Dispatcher(3)
Class for dispatching request to the appropriate route handler
Dancer::RPCPlugin::DispatchFromConfig(3)
Build dispatch-table from the Dancer Config
Dancer::RPCPlugin::DispatchFromPod(3)
Build dispatch-table from POD
Dancer::RPCPlugin::DispatchItem(3)
Small object to handle dispatch-table items
Dancer::RPCPlugin::DispatchMethodList(3)
Class for maintaining a global methodlist
DateTime::Format::Builder::Parser::Dispatch(3)
Dispatch parsers by group
Devel::PatchPerl(3)
Patch perl source a la Devel::PPPort's buildperl.pl
Devel::PatchPerl::Hints(3)
replacement 'hints' files
Devel::PatchPerl::Plugin(3)
Devel::PatchPerl plugins explained
Gantry::Conf::FAQ(3)
Frequently Asked Questions regarding Gantry::Conf "Why should I use Gantry::Conf at all?" 4 Item "Why should I use Gantry::Conf at all?" There are many reasons why we feel Gantry::Conf is helpful both during development and after deployment. The next two entries should hopefully answer this question for you as they outline a few common scenarios programmers and system administrators often face. "How is Gantry::Conf helpful during development?" 4 Item "How is Gantry::Conf helpful during development?" "Easy separation of development configs from production configs" 4 Item "Easy separation of development configs from production configs" Often programmers have a separate development environment from their production environment. By using <shared> blocks and dev instances you can avoid spending any serious time setting up your application in the development environment. Take this configuration example: <shared dev> dbuser nobody dbpass secret dbconn "dbi:Pg:dbname=dev" </shared> <shared production> dbuser apache dbpass secret2 dbconn "dbi:Pg:dbname=production" </shared> <instance app1> ConfigureVia FlatFile Config::General /etc/apps/app1.conf use production </instance> <instance app1-dev> ConfigureVia FlatFile Config::General /etc/apps/app1.conf use dev </instance> By separating out our production and dev database information into shared blocks we can essentially switch between our production and dev environments by simply changing the instance we are using. If you were working on a script this would be a simple matter of running: $ script.pl --instance=app1-dev instead of: $ script.pl --instance=app1 "How is Gatnry::Conf helpful in production?" 4 Item "How is Gatnry::Conf helpful in production?" Gantry::Conf has several advantages in a production environment. First, it provides a single place for all config information, if you commit to it. Even if you don't commit to it for all apps, it still provides control to the installing admin over how and where conf information is stored. For instance, the admin could put the config information directly into /etc/gantry.conf, or into a separate file in /etc/gantry.d. She could even set up a secure web server where all boxes would go to get their conf. The short answer is, Gantry::Conf is flexible and production environments benefit from flexibility. "How do I pass my instance information into my application?" 4 Item "How do I pass my instance information into my application?" There are many possible ways to do this a few of which are: "Command line arguments" 4 Item "Command line arguments" If your application accepts arguments on the command line we suggest adding an --instance option to pass in the instance's name. "PerlSetVar" 4 Item "PerlSetVar" In a mod_perl environment you could use a PerlSetVar, possibly named GantryConfInstance, to pull in this value for your application. "ModPerl::ParamBuilder" 4 Item "ModPerl::ParamBuilder" Again in a mod_perl environment, another option would be to use ModPerl::ParamBuilder to pass the instance name. "Hard coded" 4 Item "Hard coded" We include this for the sake of completeness, but advise against it. You could always simply hard code your instance information into your application, but this will greatly reduce the flexibility you have. "How do I add a different provider for an existing ConfigVia method?" 4 Item "How do I add a different provider for an existing ConfigVia method?" Place your provider module in the Gantry::Conf::Provider::Method::* namespace. Make sure your public API matches the existing providers which use the same method. For instance the flat file providers all implement a config method which is called as a class method and receives a file name. "How do I add to the ConfigVia methods?" 4 Item "How do I add to the ConfigVia methods?" If none of the existing provider methods will do, you need to work in Gantry::Conf. In particular, you need to augment the dispatch hash with the name of your provisioning method and a sub name which will handle it. Then you need to implement the method you put in %dispatch
Graphics::Primitive::Paint::Solid(3)
Solid patch of color
Gungho::Log::Dispatch(3)
Log::Dispatch-Based Log For Gungho
JSON::RPC::Dispatch(3)
Dispatch JSON RPC Requests To Handlers
JSON::RPC::Dispatcher(3)
A JSON-RPC 2.0 server
JSON::RPC::Dispatcher::App(3)
A base class for creating object oriented apps with JRD
JSON::RPC::Dispatcher::Procedure(3)
The data holder between RPC requests and responses
Jifty::Dispatcher(3)
The Jifty Dispatcher
Jifty::Plugin::AdminUI::Dispatcher(3)
dispatcher of the AdminUI plugin
Jifty::Plugin::Authentication::Password::Dispatcher(3)
password plugin dispatcher
Jifty::Plugin::Config::Dispatcher(3)
dispatcher of the Config plugin
Jifty::Plugin::LetMe::Dispatcher(3)
Dispatcher for LetMe plugin
Jifty::Plugin::OnlineDocs::Dispatcher(3)
Dispatcher for OnlineDocs plugin
Jifty::Plugin::REST::Dispatcher(3)
Dispatcher for REST plugin
Jifty::Plugin::SinglePage::Dispatcher(3)
Dispatcher for SinglePage plugin
Jifty::Plugin::SkeletonApp::Dispatcher(3)
Dispatcher for SkeletonApp plugin
Log::Any::Adapter::Dispatch(3)
Adapter to use Log::Dispatch with Log::Any
Log::Dispatch(3)
Dispatches messages to one or more outputs
Log::Dispatch::ApacheLog(3)
Object for logging to Apache::Log objects
Log::Dispatch::Array(3)
log events to an array (reference)
Log::Dispatch::ArrayWithLimits(3)
Log to array, with some limits applied
Log::Dispatch::Base(3)
Code shared by dispatch and output objects
Log::Dispatch::Code(3)
Object for logging to a subroutine reference
Log::Dispatch::Colorful(3)
Object for logging to screen
Log::Dispatch::Config(3)
Log4j for Perl
Log::Dispatch::Configurator(3)
Abstract Configurator class
Log::Dispatch::Configurator::Any(3)
Configurator implementation with Config::Any
Log::Dispatch::Configurator::AppConfig(3)
Configurator implementation with AppConfig
Log::Dispatch::Configurator::YAML(3)
Configurator implementation with YAML
Log::Dispatch::DBI(3)
Class for logging to database via DBI interface
Log::Dispatch::Dir(3)
Log messages to separate files in a directory, with rotate options
Log::Dispatch::Email(3)
Base class for objects that send log messages via email
Log::Dispatch::Email::EmailSend(3)
Subclass of Log::Dispatch::Email that uses Email::Send
Log::Dispatch::Email::MIMELite(3)
Subclass of Log::Dispatch::Email that uses the MIME::Lite module
Log::Dispatch::Email::MailSend(3)
Subclass of Log::Dispatch::Email that uses the Mail::Send module
Log::Dispatch::Email::MailSender(3)
Subclass of Log::Dispatch::Email that uses the Mail::Sender module
Log::Dispatch::Email::MailSendmail(3)
Subclass of Log::Dispatch::Email that uses the Mail::Sendmail module
Log::Dispatch::File(3)
Object for logging to files
Log::Dispatch::File::Locked(3)
Subclass of Log::Dispatch::File to facilitate locking
Log::Dispatch::File::Rolling(3)
Object for logging to date/time/pid stamped files
Log::Dispatch::File::Stamped(3)
Logging to date/time stamped files
Log::Dispatch::FileRotate(3)
Log to Files that Archive/Rotate Themselves
Log::Dispatch::FileRotate::Flock(3)
File Locking Functions for Log::Dispatch::FileRotate
Log::Dispatch::FileRotate::Mutex(3)
Flock Based File Mutex
Log::Dispatch::FileShared(3)
Log::Dispatch output class for logging to shared files
Log::Dispatch::FileWriteRotate(3)
Log to files that archive/rotate themselves, w/ File::Write::Rotate
Log::Dispatch::Handle(3)
Object for logging to IO::Handle classes
Log::Dispatch::Null(3)
Object that accepts messages and does nothing
Log::Dispatch::Output(3)
Base class for all Log::Dispatch::* objects
Log::Dispatch::Perl(3)
Use core Perl functions for logging
Log::Dispatch::Screen(3)
Object for logging to the screen
Log::Dispatch::Screen::Color(3)
attached color for Log::Dispatch::Screen
Log::Dispatch::Scribe(3)
Logging via Facebook's Scribe server software
Log::Dispatch::Syslog(3)
Object for logging to system log
Log::Dispatch::Types(3)
Types used for parameter checking in Log::Dispatch
Log::Dispatch::Vars(3)
Variables used internally by multiple packages
Log::Dispatchouli(3)
a simple wrapper around Log::Dispatch
Log::Dispatchouli::Global(3)
a system for sharing a global, dynamically-scoped logger
Log::Dispatchouli::Proxy(3)
a simple wrapper around Log::Dispatch
Log::Log4perl::JavaMap(3)
maps java log4j appenders to Log::Dispatch classes
Log::Log4perl::JavaMap::ConsoleAppender(3)
wraps Log::Dispatch::Screen
Log::Log4perl::JavaMap::FileAppender(3)
wraps Log::Dispatch::File
Log::Log4perl::JavaMap::NTEventLogAppender(3)
wraps Log::Dispatch::Win32EventLog
Log::Log4perl::JavaMap::RollingFileAppender(3)
wraps Log::Dispatch::FileRotate
Log::Log4perl::JavaMap::SyslogAppender(3), Log::Log4perl::JavaMap::SysLogAppender(3)
wraps Log::Dispatch::Syslog
Log::Report::Dispatcher(3)
manage message dispatching, display or logging
Log::Report::Dispatcher::Callback(3)
call a code-ref for each log-line
Log::Report::Dispatcher::File(3)
send messages to a file or file-handle
Log::Report::Dispatcher::Log4perl(3)
send messages to Log::Log4perl back-end
Log::Report::Dispatcher::LogDispatch(3)
send messages to Log::Dispatch back-end
Log::Report::Dispatcher::Perl(3)
send messages to die and warn
Log::Report::Dispatcher::Syslog(3)
send messages to syslog
Log::Report::Dispatcher::Try(3)
capture all reports as exceptions
Mail::DMARC::Report::Send(3)
report sending dispatch class
Mason::Manual::RequestDispatch(3)
How request paths get mapped to page components
Mixin::Event::Dispatch(3)
mixin methods for simple event/message dispatch framework
Mixin::Event::Dispatch::Bus(3)
a message bus
Mixin::Event::Dispatch::Event(3)
an event object
Mixin::Event::Dispatch::Methods(3)
importer class for applying Mixin::Event::Dispatch methods without inheritance
Mock::MonkeyPatch(3)
Monkey patching with test mocking in mind
Mojo::DynamicMethods(3)
Fast dynamic method dispatch
MojoMojo::Formatter::Main(3)
MojoMojo's main formatter, dispatching between Textile and MultiMarkdown
MojoX::Log::Dispatch::Simple(3)
Simple Log::Dispatch replacement of Mojo::Log
MooseX::Declare::Syntax::OptionHandling(3)
Option parser dispatching
MooseX::MultiMethods(3)
Multi Method Dispatch based on Moose type constraints
MooseX::Role::Loggable(3)
Extensive, yet simple, logging role using Log::Dispatchouli
NEXT(3)
Provide a pseudo-class NEXT (et al) that allows method redispatch
Net::Analysis::Dispatcher(3)
handle the event stuff for the proto analysers
Net::HTTP::Spore::Middleware::LogDispatch(3)
Net::HTTP::Spore::Middleware::LogDispatch is a middleware that allow you to use LogDispatch
Net::INET6Glue(3)
Make common modules IPv6 ready by hotpatching
Net::INET6Glue::FTP(3)
adds IPv6 support to Net::FTP by hotpatching
Net::SIP::Dispatcher(3)
dispatch SIP packets between legs and endpoint
Net::SIP::Dispatcher::Eventloop(3)
simple event loop for Net::SIP::Dispatcher
Nginx::Simple::Dispatch(3)
Easy to use dispatcher interface for "--with-http_perl_module"
Nginx::Simple::Dispatcher::Attributes(3)
Attributes: Index, Page
PAR::Filter::PatchContent(3)
Content patcher
POE::Session::MultiDispatch(3)
Callback dispatch for session events
PatchReader(3)
Utilities to read and manipulate patches and CVS
Path::Dispatcher(3)
Flexible and extensible dispatch
Path::Dispatcher::Cookbook(3)
A cookbook for Path::Dispatcher
Path::Dispatcher::Declarative(3)
sugary dispatcher
Path::Dispatcher::Dispatch(3)
a list of matches
Path::Dispatcher::Match(3)
the result of a successful rule match
Path::Dispatcher::Path(3)
path and some optional metadata
Path::Dispatcher::Role::Rules(3)
"has a list of rules"
Path::Dispatcher::Rule(3)
predicate and codeblock
Path::Dispatcher::Rule::Alternation(3)
any rule must match
Path::Dispatcher::Rule::Always(3)
always matches
Path::Dispatcher::Rule::Chain(3)
Chain rules for Path::Dispatcher
Path::Dispatcher::Rule::CodeRef(3)
predicate is any subroutine
Path::Dispatcher::Rule::Dispatch(3)
redispatch
Path::Dispatcher::Rule::Empty(3)
matches only the empty path
Path::Dispatcher::Rule::Enum(3)
one of a list of strings must match
Path::Dispatcher::Rule::Eq(3)
predicate is a string equality
Path::Dispatcher::Rule::Intersection(3)
all rules must match
Path::Dispatcher::Rule::Metadata(3)
match path's metadata
Path::Dispatcher::Rule::Regex(3)
predicate is a regular expression
Path::Dispatcher::Rule::Sequence(3)
a sequence of rules
Path::Dispatcher::Rule::Tokens(3)
predicate is a list of tokens
Path::Dispatcher::Rule::Under(3)
rules under a predicate
Pipeline::Dispatch(3)
dispatcher for pipeline segments
Plack::Middleware::LogDispatch(3)
Uses Log::Dispatch to configure logger
RDF::Trine::Exporter::RDFPatch(3)
RDF-Patch Export
RDF::Trine::Parser::RDFPatch(3)
RDF-Patch Parser
RDF::Trine::Serializer::RDFPatch(3)
RDF-Patch Serializer
STF::Dispatcher::Impl::File(3)
STF Storage to store data in file
STF::Dispatcher::Impl::Hash(3)
STF Storage to store data in hash
STF::Dispatcher::PSGI(3)
Pluggable STF Dispatcher Interface
STF::Dispatcher::PSGI::HTTPException(3)
Very Light Exception For STF Dispatcher
STF::Dispatcher::Test(3)
Basic Tests For STF Implementations
SUPER(3)
control superclass method dispatch
SVK::Command(3)
Base class and dispatcher for SVK commands
SVK::Command::Patch(3)
Manage patches
SVK::Editor::Patch(3)
An editor to serialize editor calls
SVK::Patch(3)
Class representing a patch to be applied
SVK::Patchset(3)
Calculate patch dependency
SVN::Web::DiffParser(3)
Parse patch files containing unified and standard diffs
Servlet::RequestDispatcher(3)
request dispatcher interface
Sub::Multi(3)
Data::Bind-based multi-sub dispatch
Sub::Signatures(3)
Use proper signatures for subroutines, including dispatching
Test::Mock::LWP::Dispatch(3)
mocks LWP::UserAgent and dispatches your requests/responses
Text::Diff::Parser(3)
Parse patch files containing unified and standard diffs
Text::Patch(3)
Patches text with given patch
TheSchwartz::Simple(3)
Lightweight TheSchwartz job dispatcher using plain DBI
UUID::Random::Patch::UseMRS(3)
Make UUID::Random use Math::Random::Secure's rand()
VCP::Patch(3)
Apply the (almost) unified diffs used in RevML
VM::EC2::Dispatch(3)
Create Perl objects from AWS XML requests
Web::Dispatch::HTTPMethods(3)
Helpers to make RESTFul Dispatchers Easier
WebService::GData::Collection(3)
Composite class redispatching method calls to query the items data
applypatch(1)
apply 'makepatch' generated script to update a source tree
bk-export(1), bk export(1)
export a patch or version of a repository
bk-makepatch(1), bk makepatch(1)
creates patches
bk-patch(1), bk patch(1)
apply a diff file to an original
bk-receive(1), bk receive(1)
receive a patch
bk-send(1), bk send(1)
send a patch
bk-takepatch(1), bk takepatch(1)
apply a patch
bk-unwrap(1), bk unwrap(1)
unwrap patches
cdpatch(1)
CD-XA image insert/extract utility
certbot(1)
certbot script documentation 0.0 3.5 C usage: certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ... Certbot can obtain and install HTTPS/TLS/SSL certificates. By default, it will attempt to use a webserver both for obtaining and installing the certificate. The most common SUBCOMMANDS and flags are: obtain, install, and renew certificates: (default) run Obtain & install a certificate in your current webserver certonly Obtain or renew a certificate, but do not install it renew Renew all previously obtained certificates that are near expiry enhance Add security enhancements to your existing configuration -d DOMAINS Comma-separated list of domains to obtain a certificate for --apache Use the Apache plugin for authentication & installation --standalone Run a standalone webserver for authentication --nginx Use the Nginx plugin for authentication & installation --webroot Place files in a server(aqs webroot folder for authentication --manual Obtain certificates interactively, or using shell script hooks -n Run non-interactively --test-cert Obtain a test certificate from a staging server --dry-run Test "renew" or "certonly" without saving any certificates to disk manage certificates: certificates Display information about certificates you have from Certbot revoke Revoke a certificate (supply --cert-name or --cert-path) delete Delete a certificate (supply --cert-name) manage your account: register Create an ACME account unregister Deactivate an ACME account update_account Update an ACME account --agree-tos Agree to the ACME server(aqs Subscriber Agreement -m EMAIL Email address for important account notifications optional arguments: -h, --help show this help message and exit -c CONFIG_FILE, --config CONFIG_FILE path to config file (default: /etc/letsencrypt/cli.ini and ~/.config/letsencrypt/cli.ini) -v, --verbose This flag can be used multiple times to incrementally increase the verbosity of output, e.g. -vvv. (default: 0) --max-log-backups MAX_LOG_BACKUPS Specifies the maximum number of backup logs that should be kept by Certbot(aqs built in log rotation. Setting this flag to 0 disables log rotation entirely, causing Certbot to always append to the same log file. (default: 1000) -n, --non-interactive, --noninteractive Run without ever asking for user input. This may require additional command line flags; the client will try to explain which ones are required if it finds one missing (default: False) --force-interactive Force Certbot to be interactive even if it detects it(aqs not being run in a terminal. This flag cannot be used with the renew subcommand. (default: False) -d DOMAIN, --domains DOMAIN, --domain DOMAIN Domain names to apply. For multiple domains you can use multiple -d flags or enter a comma separated list of domains as a parameter. The first domain provided will be the subject CN of the certificate, and all domains will be Subject Alternative Names on the certificate. The first domain will also be used in some software user interfaces and as the file paths for the certificate and related material unless otherwise specified or you already have a certificate with the same name. In the case of a name collision it will append a number like 0001 to the file path name. (default: Ask) --eab-kid EAB_KID Key Identifier for External Account Binding (default: None) --eab-hmac-key EAB_HMAC_KEY HMAC key for External Account Binding (default: None) --cert-name CERTNAME Certificate name to apply. This name is used by Certbot for housekeeping and in file paths; it doesn(aqt affect the content of the certificate itself. To see certificate names, run (aqcertbot certificates(aq. When creating a new certificate, specifies the new certificate(aqs name. (default: the first provided domain or the name of an existing certificate on your system for the same domains) --dry-run Perform a test run of the client, obtaining test (invalid) certificates but not saving them to disk. This can currently only be used with the (aqcertonly(aq and (aqrenew(aq subcommands. Note: Although --dry-run tries to avoid making any persistent changes on a system, it is not completely side-effect free: if used with webserver authenticator plugins like apache and nginx, it makes and then reverts temporary config changes in order to obtain test certificates, and reloads webservers to deploy and then roll back those changes. It also calls --pre-hook and --post-hook commands if they are defined because they may be necessary to accurately simulate renewal. --deploy- hook commands are not called. (default: False) --debug-challenges After setting up challenges, wait for user input before submitting to CA (default: False) --preferred-chain PREFERRED_CHAIN Set the preferred certificate chain. If the CA offers multiple certificate chains, prefer the chain whose topmost certificate was issued from this Subject Common Name. If no match, the default offered chain will be used. (default: None) --preferred-challenges PREF_CHALLS A sorted, comma delimited list of the preferred challenge to use during authorization with the most preferred challenge listed first (Eg, "dns" or "http,dns"). Not all plugins support all challenges. See https://certbot.eff.org/docs/using.html#plugins for details. ACME Challenges are versioned, but if you pick "http" rather than "http-01", Certbot will select the latest version automatically. (default: []) --user-agent USER_AGENT Set a custom user agent string for the client. User agent strings allow the CA to collect high level statistics about success rates by OS, plugin and use case, and to know when to deprecate support for past Python versions and flags. If you wish to hide this information from the Let(aqs Encrypt server, set this to "". (default: CertbotACMEClient/1.21.0 (certbot; OS_NAME OS_VERSION) Authenticator/XXX Installer/YYY (SUBCOMMAND; flags: FLAGS) Py/major.minor.patchlevel). The flags encoded in the user agent are: --duplicate, --force-renew, --allow-subset-of-names, -n, and whether any hooks are set. --user-agent-comment USER_AGENT_COMMENT Add a comment to the default user agent string. May be used when repackaging Certbot or calling it from another tool to allow additional statistical data to be collected. Ignored if --user-agent is set. (Example: Foo-Wrapper/1.0) (default: None) automation: Flags for automating execution & other tweaks --keep-until-expiring, --keep, --reinstall If the requested certificate matches an existing certificate, always keep the existing one until it is due for renewal (for the (aqrun(aq subcommand this means reinstall the existing certificate). (default: Ask) --expand If an existing certificate is a strict subset of the requested names, always expand and replace it with the additional names. (default: Ask) --version show program(aqs version number and exit --force-renewal, --renew-by-default If a certificate already exists for the requested domains, renew it now, regardless of whether it is near expiry. (Often --keep-until-expiring is more appropriate). Also implies --expand. (default: False) --renew-with-new-domains If a certificate already exists for the requested certificate name but does not match the requested domains, renew it now, regardless of whether it is near expiry. (default: False) --reuse-key When renewing, use the same private key as the existing certificate. (default: False) --no-reuse-key When renewing, do not use the same private key as the existing certificate. Not reusing private keys is the default behavior of Certbot. This option may be used to unset --reuse-key on an existing certificate. (default: False) --allow-subset-of-names When performing domain validation, do not consider it a failure if authorizations can not be obtained for a strict subset of the requested domains. This may be useful for allowing renewals for multiple domains to succeed even if some domains no longer point at this system. This option cannot be used with --csr. (default: False) --agree-tos Agree to the ACME Subscriber Agreement (default: Ask) --duplicate Allow making a certificate lineage that duplicates an existing one (both can be renewed in parallel) (default: False) -q, --quiet Silence all output except errors. Useful for automation via cron. Implies --non-interactive. (default: False) security: Security parameters & server settings --rsa-key-size N Size of the RSA key. (default: 2048) --key-type {rsa,ecdsa} Type of generated private key. Only *ONE* per invocation can be provided at this time. (default: rsa) --elliptic-curve N The SECG elliptic curve name to use. Please see RFC 8446 for supported values. (default: secp256r1) --must-staple Adds the OCSP Must Staple extension to the certificate. Autoconfigures OCSP Stapling for supported setups (Apache version >= 2.3.3 ). (default: False) --redirect Automatically redirect all HTTP traffic to HTTPS for the newly authenticated vhost. (default: redirect enabled for install and run, disabled for enhance) --no-redirect Do not automatically redirect all HTTP traffic to HTTPS for the newly authenticated vhost. (default: redirect enabled for install and run, disabled for enhance) --hsts Add the Strict-Transport-Security header to every HTTP response. Forcing browser to always use SSL for the domain. Defends against SSL Stripping. (default: None) --uir Add the "Content-Security-Policy: upgrade-insecure- requests" header to every HTTP response. Forcing the browser to use https:// for every http:// resource. (default: None) --staple-ocsp Enables OCSP Stapling. A valid OCSP response is stapled to the certificate that the server offers during TLS. (default: None) --strict-permissions Require that all configuration files are owned by the current user; only needed if your config is somewhere unsafe like /tmp/ (default: False) --auto-hsts Gradually increasing max-age value for HTTP Strict Transport Security security header (default: False) testing: The following flags are meant for testing and integration purposes only. --test-cert, --staging Use the staging server to obtain or revoke test (invalid) certificates; equivalent to --server https://acme-staging-v02.api.letsencrypt.org/directory (default: False) --debug Show tracebacks in case of errors (default: False) --no-verify-ssl Disable verification of the ACME server(aqs certificate. (default: False) --http-01-port HTTP01_PORT Port used in the http-01 challenge. This only affects the port Certbot listens on. A conforming ACME server will still attempt to connect on port 80. (default: 80) --http-01-address HTTP01_ADDRESS The address the server listens to during http-01 challenge. (default: ) --https-port HTTPS_PORT Port used to serve HTTPS. This affects which port Nginx will listen on after a LE certificate is installed. (default: 443) --break-my-certs Be willing to replace or renew valid certificates with invalid (testing/staging) certificates (default: False) paths: Flags for changing execution paths & servers --cert-path CERT_PATH Path to where certificate is saved (with certonly --csr), installed from, or revoked (default: None) --key-path KEY_PATH Path to private key for certificate installation or revocation (if account key is missing) (default: None) --fullchain-path FULLCHAIN_PATH Accompanying path to a full certificate chain (certificate plus chain). (default: None) --chain-path CHAIN_PATH Accompanying path to a certificate chain. (default: None) --config-dir CONFIG_DIR Configuration directory. (default: /etc/letsencrypt) --work-dir WORK_DIR Working directory. (default: /var/lib/letsencrypt) --logs-dir LOGS_DIR Logs directory. (default: /var/log/letsencrypt) --server SERVER ACME Directory Resource URI. (default: https://acme-v02.api.letsencrypt.org/directory) manage: Various subcommands and flags are available for managing your certificates: certificates List certificates managed by Certbot delete Clean up all files related to a certificate renew Renew all certificates (or one specified with --cert- name) revoke Revoke a certificate specified with --cert-path or --cert-name update_symlinks Recreate symlinks in your /etc/letsencrypt/live/ directory run: Options for obtaining & installing certificates certonly: Options for modifying how a certificate is obtained --csr CSR Path to a Certificate Signing Request (CSR) in DER or PEM format. Currently --csr only works with the (aqcertonly(aq subcommand. (default: None) renew: The (aqrenew(aq subcommand will attempt to renew any certificates previously obtained if they are close to expiry, and print a summary of the results. By default, (aqrenew(aq will reuse the plugins and options used to obtain or most recently renew each certificate. You can test whether future renewals will succeed with (ga--dry-run(ga. Individual certificates can be renewed with the (ga--cert-name(ga option. Hooks are available to run commands before and after renewal; see https://certbot.eff.org/docs/using.html#renewal for more information on these. --pre-hook PRE_HOOK Command to be run in a shell before obtaining any certificates. Intended primarily for renewal, where it can be used to temporarily shut down a webserver that might conflict with the standalone plugin. This will only be called if a certificate is actually to be obtained/renewed. When renewing several certificates that have identical pre-hooks, only the first will be executed. (default: None) --post-hook POST_HOOK Command to be run in a shell after attempting to obtain/renew certificates. Can be used to deploy renewed certificates, or to restart any servers that were stopped by --pre-hook. This is only run if an attempt was made to obtain/renew a certificate. If multiple renewed certificates have identical post- hooks, only one will be run. (default: None) --deploy-hook DEPLOY_HOOK Command to be run in a shell once for each successfully issued certificate. For this command, the shell variable $RENEWED_LINEAGE will point to the config live subdirectory (for example, "/etc/letsencrypt/live/example.com") containing the new certificates and keys; the shell variable $RENEWED_DOMAINS will contain a space-delimited list of renewed certificate domains (for example, "example.com www.example.com" (default: None) --disable-hook-validation Ordinarily the commands specified for --pre- hook/--post-hook/--deploy-hook will be checked for validity, to see if the programs being run are in the $PATH, so that mistakes can be caught early, even when the hooks aren(aqt being run just yet. The validation is rather simplistic and fails if you use more advanced shell constructs, so you can use this switch to disable it. (default: False) --no-directory-hooks Disable running executables found in Certbot(aqs hook directories during renewal. (default: False) --disable-renew-updates Disable automatic updates to your server configuration that would otherwise be done by the selected installer plugin, and triggered when the user executes "certbot renew", regardless of if the certificate is renewed. This setting does not apply to important TLS configuration updates. (default: False) --no-autorenew Disable auto renewal of certificates. (default: True) certificates: List certificates managed by Certbot delete: Options for deleting a certificate revoke: Options for revocation of certificates --reason {unspecified,keycompromise,affiliationchanged,superseded,cessationofoperation} Specify reason for revoking certificate. (default: unspecified) --delete-after-revoke Delete certificates after revoking them, along with all previous and later versions of those certificates. (default: None) --no-delete-after-revoke Do not delete certificates after revoking them. This option should be used with caution because the (aqrenew(aq subcommand will attempt to renew undeleted revoked certificates. (default: None) register: Options for account registration --register-unsafely-without-email Specifying this flag enables registering an account with no email address. This is strongly discouraged, because you will be unable to receive notice about impending expiration or revocation of your certificates or problems with your Certbot installation that will lead to failure to renew. (default: False) -m EMAIL, --email EMAIL Email used for registration and recovery contact. Use comma to register multiple emails, ex: u1@example.com,u2@example.com. (default: Ask). --eff-email Share your e-mail address with EFF (default: None) --no-eff-email Don(aqt share your e-mail address with EFF (default: None) update_account: Options for account modification unregister: Options for account deactivation. --account ACCOUNT_ID Account ID to use (default: None) install: Options for modifying how a certificate is deployed rollback: Options for rolling back server configuration changes --checkpoints N Revert configuration N number of checkpoints. (default: 1) plugins: Options for the "plugins" subcommand --init Initialize plugins. (default: False) --prepare Initialize and prepare plugins. (default: False) --authenticators Limit to authenticator plugins only. (default: None) --installers Limit to installer plugins only. (default: None) update_symlinks: Recreates certificate and key symlinks in /etc/letsencrypt/live, if you changed them by hand or edited a renewal configuration file enhance: Helps to harden the TLS configuration by adding security enhancements to already existing configuration. plugins: Plugin Selection: Certbot client supports an extensible plugins architecture. See (aqcertbot plugins(aq for a list of all installed plugins and their names. You can force a particular plugin by setting options provided below. Running --help <plugin_name> will list flags specific to that plugin. --configurator CONFIGURATOR Name of the plugin that is both an authenticator and an installer. Should not be used together with --authenticator or --installer. (default: Ask) -a AUTHENTICATOR, --authenticator AUTHENTICATOR Authenticator plugin name. (default: None) -i INSTALLER, --installer INSTALLER Installer plugin name (also used to find domains). (default: None) --apache Obtain and install certificates using Apache (default: False) --nginx Obtain and install certificates using Nginx (default: False) --standalone Obtain certificates using a "standalone" webserver. (default: False) --manual Provide laborious manual instructions for obtaining a certificate (default: False) --webroot Obtain certificates by placing files in a webroot directory. (default: False) --dns-cloudflare Obtain certificates using a DNS TXT record (if you are using Cloudflare for DNS). (default: False) --dns-cloudxns Obtain certificates using a DNS TXT record (if you are using CloudXNS for DNS). (default: False) --dns-digitalocean Obtain certificates using a DNS TXT record (if you are using DigitalOcean for DNS). (default: False) --dns-dnsimple Obtain certificates using a DNS TXT record (if you are using DNSimple for DNS). (default: False) --dns-dnsmadeeasy Obtain certificates using a DNS TXT record (if you are using DNS Made Easy for DNS). (default: False) --dns-gehirn Obtain certificates using a DNS TXT record (if you are using Gehirn Infrastructure Service for DNS). (default: False) --dns-google Obtain certificates using a DNS TXT record (if you are using Google Cloud DNS). (default: False) --dns-linode Obtain certificates using a DNS TXT record (if you are using Linode for DNS). (default: False) --dns-luadns Obtain certificates using a DNS TXT record (if you are using LuaDNS for DNS). (default: False) --dns-nsone Obtain certificates using a DNS TXT record (if you are using NS1 for DNS). (default: False) --dns-ovh Obtain certificates using a DNS TXT record (if you are using OVH for DNS). (default: False) --dns-rfc2136 Obtain certificates using a DNS TXT record (if you are using BIND for DNS). (default: False) --dns-route53 Obtain certificates using a DNS TXT record (if you are using Route53 for DNS). (default: False) --dns-sakuracloud Obtain certificates using a DNS TXT record (if you are using Sakura Cloud for DNS). (default: False) apache: Apache Web Server plugin (Please note that the default values of the Apache plugin options change depending on the operating system Certbot is run on.) --apache-enmod APACHE_ENMOD Path to the Apache (aqa2enmod(aq binary (default: None) --apache-dismod APACHE_DISMOD Path to the Apache (aqa2dismod(aq binary (default: None) --apache-le-vhost-ext APACHE_LE_VHOST_EXT SSL vhost configuration extension (default: -le- ssl.conf) --apache-server-root APACHE_SERVER_ROOT Apache server root directory (default: /etc/apache2) --apache-vhost-root APACHE_VHOST_ROOT Apache server VirtualHost configuration root (default: None) --apache-logs-root APACHE_LOGS_ROOT Apache server logs directory (default: /var/log/apache2) --apache-challenge-location APACHE_CHALLENGE_LOCATION Directory path for challenge configuration (default: /etc/apache2) --apache-handle-modules APACHE_HANDLE_MODULES Let installer handle enabling required modules for you (Only Ubuntu/Debian currently) (default: False) --apache-handle-sites APACHE_HANDLE_SITES Let installer handle enabling sites for you (Only Ubuntu/Debian currently) (default: False) --apache-ctl APACHE_CTL Full path to Apache control script (default: apache2ctl) --apache-bin APACHE_BIN Full path to apache2/httpd binary (default: None) dns-cloudflare: Obtain certificates using a DNS TXT record (if you are using Cloudflare for DNS). --dns-cloudflare-propagation-seconds DNS_CLOUDFLARE_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 10) --dns-cloudflare-credentials DNS_CLOUDFLARE_CREDENTIALS Cloudflare credentials INI file. (default: None) dns-cloudxns: Obtain certificates using a DNS TXT record (if you are using CloudXNS for DNS). --dns-cloudxns-propagation-seconds DNS_CLOUDXNS_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 30) --dns-cloudxns-credentials DNS_CLOUDXNS_CREDENTIALS CloudXNS credentials INI file. (default: None) dns-digitalocean: Obtain certificates using a DNS TXT record (if you are using DigitalOcean for DNS). --dns-digitalocean-propagation-seconds DNS_DIGITALOCEAN_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 10) --dns-digitalocean-credentials DNS_DIGITALOCEAN_CREDENTIALS DigitalOcean credentials INI file. (default: None) dns-dnsimple: Obtain certificates using a DNS TXT record (if you are using DNSimple for DNS). --dns-dnsimple-propagation-seconds DNS_DNSIMPLE_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 30) --dns-dnsimple-credentials DNS_DNSIMPLE_CREDENTIALS DNSimple credentials INI file. (default: None) dns-dnsmadeeasy: Obtain certificates using a DNS TXT record (if you are using DNS Made Easy for DNS). --dns-dnsmadeeasy-propagation-seconds DNS_DNSMADEEASY_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 60) --dns-dnsmadeeasy-credentials DNS_DNSMADEEASY_CREDENTIALS DNS Made Easy credentials INI file. (default: None) dns-gehirn: Obtain certificates using a DNS TXT record (if you are using Gehirn Infrastructure Service for DNS). --dns-gehirn-propagation-seconds DNS_GEHIRN_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 30) --dns-gehirn-credentials DNS_GEHIRN_CREDENTIALS Gehirn Infrastructure Service credentials file. (default: None) dns-google: Obtain certificates using a DNS TXT record (if you are using Google Cloud DNS for DNS). --dns-google-propagation-seconds DNS_GOOGLE_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 60) --dns-google-credentials DNS_GOOGLE_CREDENTIALS Path to Google Cloud DNS service account JSON file. (See https://developers.google.com/identity/protocols/ OAuth2ServiceAccount#creatinganaccount forinformation about creating a service account and https://cloud.google.com/dns/access- control#permissions_and_roles for information about therequired permissions.) (default: None) dns-linode: Obtain certificates using a DNS TXT record (if you are using Linode for DNS). --dns-linode-propagation-seconds DNS_LINODE_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 120) --dns-linode-credentials DNS_LINODE_CREDENTIALS Linode credentials INI file. (default: None) dns-luadns: Obtain certificates using a DNS TXT record (if you are using LuaDNS for DNS). --dns-luadns-propagation-seconds DNS_LUADNS_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 30) --dns-luadns-credentials DNS_LUADNS_CREDENTIALS LuaDNS credentials INI file. (default: None) dns-nsone: Obtain certificates using a DNS TXT record (if you are using NS1 for DNS). --dns-nsone-propagation-seconds DNS_NSONE_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 30) --dns-nsone-credentials DNS_NSONE_CREDENTIALS NS1 credentials file. (default: None) dns-ovh: Obtain certificates using a DNS TXT record (if you are using OVH for DNS). --dns-ovh-propagation-seconds DNS_OVH_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 30) --dns-ovh-credentials DNS_OVH_CREDENTIALS OVH credentials INI file. (default: None) dns-rfc2136: Obtain certificates using a DNS TXT record (if you are using BIND for DNS). --dns-rfc2136-propagation-seconds DNS_RFC2136_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 60) --dns-rfc2136-credentials DNS_RFC2136_CREDENTIALS RFC 2136 credentials INI file. (default: None) dns-route53: Obtain certificates using a DNS TXT record (if you are using AWS Route53 for DNS). --dns-route53-propagation-seconds DNS_ROUTE53_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 10) dns-sakuracloud: Obtain certificates using a DNS TXT record (if you are using Sakura Cloud for DNS). --dns-sakuracloud-propagation-seconds DNS_SAKURACLOUD_PROPAGATION_SECONDS The number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record. (default: 90) --dns-sakuracloud-credentials DNS_SAKURACLOUD_CREDENTIALS Sakura Cloud credentials file. (default: None) manual: Authenticate through manual configuration or custom shell scripts. When using shell scripts, an authenticator script must be provided. The environment variables available to this script depend on the type of challenge. $CERTBOT_DOMAIN will always contain the domain being authenticated. For HTTP-01 and DNS-01, $CERTBOT_VALIDATION is the validation string, and $CERTBOT_TOKEN is the filename of the resource requested when performing an HTTP-01 challenge. An additional cleanup script can also be provided and can use the additional variable $CERTBOT_AUTH_OUTPUT which contains the stdout output from the auth script. For both authenticator and cleanup script, on HTTP-01 and DNS-01 challenges, $CERTBOT_REMAINING_CHALLENGES will be equal to the number of challenges that remain after the current one, and $CERTBOT_ALL_DOMAINS contains a comma-separated list of all domains that are challenged for the current certificate. --manual-auth-hook MANUAL_AUTH_HOOK Path or command to execute for the authentication script (default: None) --manual-cleanup-hook MANUAL_CLEANUP_HOOK Path or command to execute for the cleanup script (default: None) nginx: Nginx Web Server plugin --nginx-server-root NGINX_SERVER_ROOT Nginx server root directory. (default: /etc/nginx or /usr/local/etc/nginx) --nginx-ctl NGINX_CTL Path to the (aqnginx(aq binary, used for (aqconfigtest(aq and retrieving nginx version number. (default: nginx) --nginx-sleep-seconds NGINX_SLEEP_SECONDS Number of seconds to wait for nginx configuration changes to apply when reloading. (default: 1) null: Null Installer standalone: Spin up a temporary webserver webroot: Place files in webroot directory --webroot-path WEBROOT_PATH, -w WEBROOT_PATH public_html / webroot path. This can be specified multiple times to handle different domains; each domain will have the webroot path that preceded it. For instance: (ga-w /var/www/example -d example.com -d www.example.com -w /var/www/thing -d thing.net -d m.thing.net(ga (default: Ask) --webroot-map WEBROOT_MAP JSON dictionary mapping domains to webroot paths; this implies -d for each entry. You may need to escape this from your shell. E.g.: --webroot-map (aq{"eg1.is,m.eg1.is":"/www/eg1/", "eg2.is":"/www/eg2"}(aq This option is merged with, but takes precedence over, -w / -d entries. At present, if you put webroot-map in a config file, it needs to be on a single line, like: webroot-map = {"example.com":"/var/www"}. (default: {}) P
combinediff(1)
create a cumulative unified patch from two incremental patches
dnscheck-dispatcher(1)
daemon program to run tests from a database queue
espdiff(1)
apply the appropriate transformation to a set of patches
flipdiff(1)
exchange the order of two incremental patches
lsdiff(1)
show which files are modified by a patch
makepatch(1)
create script to update a source tree
nspatch(1)
run `nsdiff | nsupdate` with error handling
patch(1)
a program for applying a diff file to an original
patch-g(1)
convert FASTGEN ASCII databases into binary MGED databases
patchperl(1)
patch a perl source tree
patchview(1)
Without options, show numbered files modified by the patch. With options, behave as filterdiff
perlhacktut(1)
Walk through the creation of a simple C code patch
r.li.mps(1), r.li.mps (1)
Calculates mean patch size index on a raster map, using a 4 neighbour algorithm
r.li.padcv(1), r.li.padcv (1)
Calculates coefficient of variation of patch area on a raster map
r.li.padrange(1), r.li.padrange (1)
Calculates range of patch area size on a raster map
r.li.padsd(1), r.li.padsd (1)
Calculates standard deviation of patch area a raster map
r.li.patchdensity(1), r.li.patchdensity (1)
Calculates patch density index on a raster map, using a 4 neighbour algorithm
r.li.patchnum(1), r.li.patchnum (1)
Calculates patch number index on a raster map, using a 4 neighbour algorithm
r.patch(1), r.patch (1)
Creates a composite raster map layer by using known category values from one (or more) map layer(s) to fill in areas of (dqno data(dq in another map layer
recountdiff(1)
recompute patch counts and offsets
remrt(1)
network distributed (remote) ray-trace dispatcher
rpatch(1)
convert FASTGEN ASCII databases into a format suitable for
snmpa_mpd(3)
Message Processing and Dispatch module for the SNMP agent
snmpm_mpd(3)
Message Processing and Dispatch module for the SNMP manager
splitdiff(1)
separate out incremental patches
uips(1)
Universal IPS patch create/apply utility
unwrapdiff(1)
demangle word-wrapped patches
v.patch(1), v.patch (1)
Creates a new vector map by combining other vector maps
home | help