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

FreeBSD Manual Pages

  
 
  

home | help
baudrate(3), erasechar(3), erasewchar(3), has_ic(3), has_il(3), killchar(3), killwchar(3), longname(3), term_attrs(3), termattrs(3), termname(3)
curses environment query routines
etcupdate(8)
manage updates to system files not updated by installworld
iwlwifi(4)
Intel IEEE 802.11a/b/g/n/ac/ax wireless network driver
iwlwififw(4)
Firmware modules for Intel iwlwifi wireless network driver
mailer.conf(5)
configuration file for mailwrapper(8)
mailwrapper(8)
invoke appropriate MTA software based on configuration file
newwin(3), delwin(3), mvwin(3), subwin(3), derwin(3), mvderwin(3), dupwin(3), wsyncup(3), syncok(3), wcursyncup(3), wsyncdown(3)
create curses windows
procstat_close(3), procstat_freeargv(3), procstat_freeauxv(3), procstat_freeenvv(3), procstat_freefiles(3), procstat_freegroups(3), procstat_freekstack(3), procstat_freeprocs(3), procstat_freeptlwpinfo(3), procstat_freevmmap(3), procstat_get_pipe_info(3), procstat_get_pts_info(3), procstat_get_sem_info(3), procstat_get_shm_info(3), procstat_get_socket_info(3), procstat_get_vnode_info(3), procstat_getargv(3), procstat_getauxv(3), procstat_getenvv(3), procstat_getfiles(3), procstat_getgroups(3), procstat_getkstack(3), procstat_getosrel(3), procstat_getpathname(3), procstat_getprocs(3), procstat_getptlwpinfo(3), procstat_getrlimit(3), procstat_getumask(3), procstat_getvmmap(3), procstat_open_core(3), procstat_open_kvm(3), procstat_open_sysctl(3)
library interface for file and process information retrieval
seldrain(9), selrecord(9), selwakeup(9)
record and wakeup select requests
FeelWindowBox(1x)
defines placement policy for certain type of windows, based on desk, window attributes, window size, etc. Useful for xinerama configurations, where windows should not be placed in between screens
MPIX_Ialltoallw(3)
XXX description here
MPIX_Ineighbor_alltoallw(3)
Nonblocking version of MPIX_Neighbor_alltoallw
MPIX_Neighbor_alltoallw(3)
Like MPIX_Neighbor_alltoallv but it allows one to send and receive with different types to and from each neighbor
MPI_Alltoallw(3)
Generalized all-to-all communication allowing different datatypes, counts, and displacements for each partner
MPI_Ialltoallw(3)
Nonblocking generalized all-to-all communication allowing different datatypes, counts, and displacements for each partner
MPI_Ineighbor_alltoallw(3)
Nonblocking version of MPI_Neighbor_alltoallw
MPI_Neighbor_alltoallw(3)
Like MPI_Neighbor_alltoallv but it allows one to send and receive with different types to and from each neighbor
Munin::Node::SpoolWriter(3)
Writing side of the spool functionality
RlwrapFilter(3pm)
Perl class for rlwrap filters
Tcl_BadChannelOption.tcl85(3), Tcl_CreateChannel(3), Tcl_GetChannelInstanceData(3), Tcl_GetChannelType(3), Tcl_GetChannelName(3), Tcl_GetChannelHandle(3), Tcl_GetChannelMode(3), Tcl_GetChannelBufferSize(3), Tcl_SetChannelBufferSize(3), Tcl_NotifyChannel(3), Tcl_BadChannelOption(3), Tcl_ChannelName(3), Tcl_ChannelVersion(3), Tcl_ChannelBlockModeProc(3), Tcl_ChannelCloseProc(3), Tcl_ChannelClose2Proc(3), Tcl_ChannelInputProc(3), Tcl_ChannelOutputProc(3), Tcl_ChannelSeekProc(3), Tcl_ChannelWideSeekProc(3), Tcl_ChannelTruncateProc(3), Tcl_ChannelSetOptionProc(3), Tcl_ChannelGetOptionProc(3), Tcl_ChannelWatchProc(3), Tcl_ChannelGetHandleProc(3), Tcl_ChannelFlushProc(3), Tcl_ChannelHandlerProc(3), Tcl_ChannelThreadActionProc(3), Tcl_IsChannelShared(3), Tcl_IsChannelRegistered(3), Tcl_CutChannel(3), Tcl_SpliceChannel(3), Tcl_IsChannelExisting(3), Tcl_ClearChannelHandlers(3), Tcl_GetChannelThread(3), Tcl_ChannelBuffered(3)
procedures for creating and manipulating channels
Tcl_BadChannelOption.tcl86(3), Tcl_CreateChannel(3), Tcl_GetChannelInstanceData(3), Tcl_GetChannelType(3), Tcl_GetChannelName(3), Tcl_GetChannelHandle(3), Tcl_GetChannelMode(3), Tcl_GetChannelBufferSize(3), Tcl_SetChannelBufferSize(3), Tcl_NotifyChannel(3), Tcl_BadChannelOption(3), Tcl_ChannelName(3), Tcl_ChannelVersion(3), Tcl_ChannelBlockModeProc(3), Tcl_ChannelCloseProc(3), Tcl_ChannelClose2Proc(3), Tcl_ChannelInputProc(3), Tcl_ChannelOutputProc(3), Tcl_ChannelSeekProc(3), Tcl_ChannelWideSeekProc(3), Tcl_ChannelTruncateProc(3), Tcl_ChannelSetOptionProc(3), Tcl_ChannelGetOptionProc(3), Tcl_ChannelWatchProc(3), Tcl_ChannelGetHandleProc(3), Tcl_ChannelFlushProc(3), Tcl_ChannelHandlerProc(3), Tcl_ChannelThreadActionProc(3), Tcl_IsChannelShared(3), Tcl_IsChannelRegistered(3), Tcl_CutChannel(3), Tcl_SpliceChannel(3), Tcl_IsChannelExisting(3), Tcl_ClearChannelHandlers(3), Tcl_GetChannelThread(3), Tcl_ChannelBuffered(3)
procedures for creating and manipulating channels
Tcl_BadChannelOption.tcl87(3), Tcl_CreateChannel(3), Tcl_GetChannelInstanceData(3), Tcl_GetChannelType(3), Tcl_GetChannelName(3), Tcl_GetChannelHandle(3), Tcl_GetChannelMode(3), Tcl_GetChannelBufferSize(3), Tcl_SetChannelBufferSize(3), Tcl_NotifyChannel(3), Tcl_BadChannelOption(3), Tcl_ChannelName(3), Tcl_ChannelVersion(3), Tcl_ChannelBlockModeProc(3), Tcl_ChannelCloseProc(3), Tcl_ChannelClose2Proc(3), Tcl_ChannelInputProc(3), Tcl_ChannelOutputProc(3), Tcl_ChannelSeekProc(3), Tcl_ChannelWideSeekProc(3), Tcl_ChannelTruncateProc(3), Tcl_ChannelSetOptionProc(3), Tcl_ChannelGetOptionProc(3), Tcl_ChannelWatchProc(3), Tcl_ChannelGetHandleProc(3), Tcl_ChannelFlushProc(3), Tcl_ChannelHandlerProc(3), Tcl_ChannelThreadActionProc(3), Tcl_IsChannelShared(3), Tcl_IsChannelRegistered(3), Tcl_CutChannel(3), Tcl_SpliceChannel(3), Tcl_IsChannelExisting(3), Tcl_ClearChannelHandlers(3), Tcl_GetChannelThread(3), Tcl_ChannelBuffered(3)
procedures for creating and manipulating channels
Tcl_CallWhenDeleted.tcl85(3), Tcl_CallWhenDeleted(3), Tcl_DontCallWhenDeleted(3)
Arrange for callback when interpreter is deleted
Tcl_CallWhenDeleted.tcl86(3), Tcl_CallWhenDeleted(3), Tcl_DontCallWhenDeleted(3)
Arrange for callback when interpreter is deleted
Tcl_CallWhenDeleted.tcl87(3), Tcl_CallWhenDeleted(3), Tcl_DontCallWhenDeleted(3)
Arrange for callback when interpreter is deleted
Tk_MoveToplevelWindow.tk85(3), Tk_MoveToplevelWindow(3)
Adjust the position of a top-level window
Tk_MoveToplevelWindow.tk86(3), Tk_MoveToplevelWindow(3)
Adjust the position of a top-level window
baudrate(3x), erasechar(3x), erasewchar(3x), has_ic(3x), has_il(3x), killchar(3x), killwchar(3x), longname(3x), term_attrs(3x), termattrs(3x), termname(3x)
curses environment query routines
coolman(1), coolman-3.17.20(1)
Man page reader for the X Window System based on the Coolwidget library
delwords(1)
Deleting words from specified dictionary collectively
dns2blackhole(8)
Malware Prevention through Domain Blocking (Black Hole)
etcupdate(8)
manage updates to system files not updated by installworld
evilwm(1)
Minimalist Window Manager for X
fido_dev_enable_entattest(3), fido_dev_toggle_always_uv(3), fido_dev_force_pin_change(3), fido_dev_set_pin_minlen(3), fido_dev_set_pin_minlen_rpid(3)
CTAP 2.1 configuration authenticator API
flwm(1)
The Fast Light Window Manager
itclwidget(i4), itcl::widget(i4)
create a widget class of objects
killw(1)
kill windows
llvmopenmp-devel(1), llvmopenmp(1)
LLVM/OpenMP 15.0.0git NOTE: 0.0 3.5 This document is a work in progress and most of the expected content is not yet available. While you can expect changes, we always welcome feedback and additions. Please contact, e.g., through openmp-dev@lists.llvm.org. OpenMP impacts various parts of the LLVM project, from the frontends (%Clang and Flang), through middle-end optimizations, up to the multitude of available OpenMP runtimes. A high-level overview of OpenMP in LLVM can be found here
llvmopenmp12(1), llvmopenmp(1)
LLVM/OpenMP NOTE: 0.0 3.5 This document is a work in progress and most of the expected content is not yet available. While you can expect changes, we always welcome feedback and additions. Please contact, e.g., through openmp-dev@lists.llvm.org. OpenMP impacts various parts of the LLVM project, from the frontends (%Clang and Flang), through middle-end optimizations, up to the multitude of available OpenMP runtimes. A high-level overview of OpenMP in LLVM can be found here
llvmopenmp13(1), llvmopenmp(1)
LLVM/OpenMP NOTE: 0.0 3.5 This document is a work in progress and most of the expected content is not yet available. While you can expect changes, we always welcome feedback and additions. Please contact, e.g., through openmp-dev@lists.llvm.org. OpenMP impacts various parts of the LLVM project, from the frontends (%Clang and Flang), through middle-end optimizations, up to the multitude of available OpenMP runtimes. A high-level overview of OpenMP in LLVM can be found here
llvmopenmp14(1), llvmopenmp(1)
LLVM/OpenMP 14.0.0 NOTE: 0.0 3.5 This document is a work in progress and most of the expected content is not yet available. While you can expect changes, we always welcome feedback and additions. Please contact, e.g., through openmp-dev@lists.llvm.org. OpenMP impacts various parts of the LLVM project, from the frontends (%Clang and Flang), through middle-end optimizations, up to the multitude of available OpenMP runtimes. A high-level overview of OpenMP in LLVM can be found here
lwm(1)
Lightweight Window Manager for the X Window System
nbdkit-full-plugin(1)
nbdkit plugin which is always full
newwin(3x), delwin(3x), mvwin(3x), subwin(3x), derwin(3x), mvderwin(3x), dupwin(3x), wsyncup(3x), syncok(3x), wcursyncup(3x), wsyncdown(3x)
create curses windows
openbve(6), openBVE(6)
train/railway simulator and game
ovsdb-server(5)
_Server database schema Every ovsdb-server (version 2[char46]9 or later) always hosts an instance of this schema, which holds information on the status and configuration of the server itself[char46] This database is read-only[char46] This manpage describes the schema for this database[char46]
rlm_always(5)
FreeRADIUS Module
rlwrap(1)
readline wrapper OP
sigrok-fwextract-sysclk-lwla(1)
Extract SysClk LWLA* firmware
slw(1)
select window interactively
ustrlwr(3)
Replaces all letters with lower case. Allegro game programming library
vga_setlogicalwidth(3)
set the logical scanline width
whirlwindwarp(6)
crazy moving stars
xmailwatcher(1)
-- periodically check for mail
xmlwf(1)
Determines if an XML document is well-formed
xtoolwait(1)
start X client and wait for it to map a window
AMF::Perl(3)
Flash Remoting in Perl Translated from PHP Remoting v. 0.5b from the -PHP project. Main gateway class. This is always the file you call from flash remoting-enabled server scripts
Alien::Build::Plugin::Fetch::LWP(3)
Plugin for fetching files using LWP
AnyEvent::HTTP::LWP::UserAgent(3)
LWP::UserAgent interface but works using AnyEvent::HTTP
Bio::AlignIO::clustalw(3)
clustalw sequence input/output stream
Bio::Phylo::Parsers::Tolweb(3)
Parser used by Bio::Phylo::IO, no serviceable parts inside
Bio::Phylo::PhyloWS::Service::Tolweb(3)
PhyloWS service wrapper for Tree of Life
Bio::Root::HTTPget(3)
module for fallback HTTP get operations when LWP:: is unavailable
Blog::Spam::Plugin::00whitelist(3)
Always permit comments from some IP addresses
Bundle::ParallelUA(3)
CPAN Bundle for the LWP Parallel User Agent extension
Carp::Always(3)
Warns and dies noisily with stack backtraces
Carp::Always::Color(3)
Carp::Always, but with color
Carp::Always::Color::HTML(3)
Carp::Always, but with HTML color
Carp::Always::Color::Term(3)
Carp::Always, but with terminal color
Catalyst::Action::SOAP::DocumentLiteralWrapped(3)
Document/Literal Wrapped SOAP ActionClass
Catalyst::Controller::SOAP::DocumentLiteralWrapped(3)
Helper controller for SOAP
Coro::LWP(3)
make LWP non-blocking - as much as possible
Crypt::SSLeay(3)
OpenSSL support for LWP
DBIx::Class::Helper::ResultSet::OneRow(3)
The first you always wanted
Data::Printer::Filter::Web(3)
pretty-printing of HTTP/JSON/LWP/Plack/Dancer/Catalyst/Mojo
Data::Stag::PerlWriter(3), Data::Stag::PerlWriter(3)
writes stag events into perl POD documentation
Data::Stag::XMLWriter(3), Data::Stag::XMLWriter(3)
writes stag events into XML files
DateTime::TimeZone::Floating(3)
A time zone that is always local
DtWsmOccupyAllWorkspaces(3)
put a window into all workspaces
Email::MIME::CreateHTML::Resolver::LWP(3)
uses LWP as a resource resolver
Excel::Writer::XLSX::Package::XMLwriter(3), XMLwriter(3)
A base class for the Excel::Writer::XLSX writer classes
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
Gtk2::ImageView::ScrollWin(3)
Scrollable window suitable for Gtk2::ImageView
GunghoX::FollowLinks::Rule::Allow(3)
Always Allow
GunghoX::FollowLinks::Rule::Deny(3)
Always Deny
HTTP::AnyUA::Backend::LWP::UserAgent(3)
A unified programming interface for LWP::UserAgent
HTTP::CookieJar::LWP(3)
LWP adapter for HTTP::CookieJar
HTTP::MHTTP(3)
this library provides reasonably low level access to the HTTP protocol, for perl. This does not replace LWP (what possibly could :-) but is a cut for speed. It also supports all of HTTP 1.0, so you have GET, POST, PUT, HEAD, and DELETE. Some support of HTTP 1.1 is available - sepcifically Transfer-Encoding = chunked and the Keep-Alive extensions. Additionally - rudimentary SSL support can be compiled in. This effectively enables negotiation of TLS, but does not validate the certificates
IO::All::LWP(3)
Extends IO::All to HTTP URLs
IO::All::LWP(3)
IO::All interface to LWP
JMX::Jmx4Perl::Agent::Jolokia::DownloadAgent(3)
Specialized LWP::UserAgent adding some bells and whistles for downloading agents and other stuff
JMX::Jmx4Perl::Agent::UserAgent(3)
Specialized LWP::UserAgent adding authentication support
LW2(3pm)
Perl HTTP library version 2.5
LWP(3)
The World-Wide Web library for Perl
LWP::Authen::Negotiate(3)
GSSAPI based Authentication Plugin for LWP
LWP::Authen::Ntlm(3)
Library for enabling NTLM authentication (Microsoft) in LWP
LWP::Authen::OAuth(3)
generate signed OAuth requests
LWP::Authen::OAuth2(3)
Make requests to OAuth2 APIs
LWP::Authen::OAuth2::AccessToken(3)
Access tokens for OAuth 2
LWP::Authen::OAuth2::AccessToken::Bearer(3)
Bearer access tokens for OAuth 2
LWP::Authen::OAuth2::Overview(3)
Overview of accessing OAuth2 APIs with LWP::Authen::OAuth2
LWP::Authen::OAuth2::ServiceProvider(3)
Understand OAuth2 Service Providers
LWP::Authen::OAuth2::ServiceProvider::Dwolla(3)
Access Dwolla API v2
LWP::Authen::OAuth2::ServiceProvider::Google(3)
Access Google OAuth2 APIs
LWP::Authen::OAuth2::ServiceProvider::Line(3)
Access Line OAuth2 API v2
LWP::Authen::OAuth2::ServiceProvider::Strava(3)
Access Strava API v3 OAuth2 APIs
LWP::Authen::OAuth2::ServiceProvider::Yahoo(3)
Access Yahoo API OAuth2 APIs
LWP::Authen::Wsse(3)
Library for enabling X-WSSE authentication in LWP
LWP::ConnCache(3)
Connection cache manager
LWP::ConnCache::MaxKeepAliveRequests(3)
A connection cache that enforces a max keep alive limit
LWP::Debug(3)
deprecated
LWP::MediaTypes(3)
guess media type for a file or a URL
LWP::MemberMixin(3)
Member access mixin class
LWP::Online(3)
Does your process have access to the web
LWP::Parallel(3)
Extension for LWP to allow parallel HTTP and FTP access
LWP::Parallel::Protocol(3)
Base class for parallel LWP protocols
LWP::Parallel::RobotUA(3)
A class for Parallel Web Robots
LWP::Parallel::UserAgent(3)
A class for parallel User Agents
LWP::ParallelUA(3)
Parallel LWP::UserAgent
LWP::Protocol(3)
Base class for LWP protocols
LWP::Protocol::PSGI(3)
Override LWP's HTTP/HTTPS backend with your own PSGI application
LWP::Protocol::connect(3)
Provides HTTP/CONNECT proxy support for LWP::UserAgent
LWP::Protocol::http10(3)
Legacy HTTP/1.0 support for LWP
LWP::Protocol::https(3)
Provide https support for LWP::UserAgent
LWP::Protocol::ldap(3)
Provide LDAP support for LWP::UserAgent
LWP::Protocol::ldapi(3)
Provide LDAPI support for LWP::UserAgent
LWP::Protocol::ldaps(3)
Provide LDAPS support for LWP::UserAgent
LWP::Protocol::socks(3)
adds support for the socks protocol and proxy facility
LWP::RobotPUA(3)
Parallel LWP::RobotUA
LWP::RobotUA(3)
a class for well-behaved Web robots
LWP::Simple(3)
simple procedural interface to LWP
LWP::UserAgent(3)
Web user agent class
LWP::UserAgent::Determined(3)
a virtual browser that retries errors
LWP::UserAgent::POE(3)
Drop-in LWP::UserAgent replacement in POE environments
LWP::UserAgent::WithCache(3)
LWP::UserAgent extension with local cache
LWPx::ParanoidAgent(3)
subclass of LWP::UserAgent that protects you from harm
LWPx::TimedHTTP(3)
time the different stages of an HTTP request
MPIX_Allgather_init(3), MPIX_Allgatherv_init(3), MPIX_Allreduce_init(3), MPIX_Alltoall_init(3), MPIX_Alltoallv_init(3), MPIX_Alltoallw_init(3), MPIX_Barrier_init(3), MPIX_Bcast_init(3), MPIX_Exscan_init(3), MPIX_Gather_init(3), MPIX_Gatherv_init(3), MPIX_Reduce_init(3), MPIX_Reduce_scatter_init(3), MPIX_Reduce_scatter_block_init(3), MPIX_Scan_init(3), MPIX_Scatter_init(3), MPIX_Scatterv_init(3), MPIX_Neighbor_allgather_init(3), MPIX_Neighbor_allgatherv_init(3), MPIX_Neighbor_alltoall_init(3), MPIX_Neighbor_alltoallv_init(3), MPIX_Neighbor_alltoallw_init(3)
Builds a handle for a collective communication or neighborhood collective communication
MPI_Alltoallw(3), MPI_Ialltoallw(3)
All processes send data of different types to, and receive data of different types from, all processes
MPI_Neighbor_alltoallw(3), MPI_Ineighbor_alltoallw(3)
All processes send data of different types to, and receive data of different types from, all processes
Mojolicious::Routes(3)
Always find your destination with routes
Net::DRI::Protocol::IRIS::LWZ(3)
IRIS LWZ connection handling (RFC4993) for Net::DRI
Net::POP3::SSLWrapper(3)
simple POP3S wrapper for Net::POP3
Net::SSLGlue::LWP(3)
proper certificate checking for https in LWP
Nexmo::SMS::MockLWP(3)
Module for the Nexmo SMS API!
Nmap::Scanner::OS::Uptime(3), Uptime(3)
uptime for remote host (not always available)
POE::Component::Client::UserAgent(3), "POE::Component::Client::UserAgent"(3)
"LWP" and "LWP::Parallel" based user agent
Path::Dispatcher::Rule::Always(3)
always matches
Paws::SimpleWorkflow::RequestCancelWorkflowExecution(3)
Arguments for method RequestCancelWorkflowExecution on Paws::SimpleWorkflow
Paws::SimpleWorkflow::SignalWorkflowExecution(3)
Arguments for method SignalWorkflowExecution on Paws::SimpleWorkflow
Perl::Critic::Policy::Modules::RequireExplicitPackage(3)
Always make the "package" explicit
Perl::Critic::Policy::RegularExpressions::RequireDotMatchAnything(3)
Always use the "/s" modifier with regular expressions
Perl::Critic::Policy::RegularExpressions::RequireExtendedFormatting(3)
Always use the "/x" modifier with regular expressions
Perl::Critic::Policy::RegularExpressions::RequireLineBoundaryMatching(3)
Always use the "/m" modifier with regular expressions
Perl::Critic::Policy::Subroutines::RequireArgUnpacking(3)
Always unpack "@_" first
Perl::Critic::Policy::TestingAndDebugging::RequireUseStrict(3)
Always "use strict"
Perl::Critic::Policy::TestingAndDebugging::RequireUseWarnings(3)
Always "use warnings"
Perl::Critic::Policy::ValuesAndExpressions::ProhibitInterpolationOfLiterals(3)
Always use single quotes for literal strings
Plack::App::Proxy::Backend::LWP(3)
backend which uses LWP::UserAgent
Plack::LWPish(3)
HTTP::Request/Response compatible interface with HTTP::Tiny backend
Pod::Elemental::Autoblank(3)
a paragraph that always displays an extra blank line in Pod form
Pod::HTML_Elements(3)
Convert POD to tree of LWP's HTML::Element and hence HTML or PostScript
Prima::ScrollWidget(3)
scrollable generic document widget
RT::Client::REST::HTTPClient(3)
Subclass LWP::UserAgent in order to support basic authentication
Search::Elasticsearch::Cxn::LWP(3)
A Cxn implementation which uses LWP
Search::Xapian::BoolWeight(3)
Boolean Weighting scheme
Spreadsheet::WriteExcelXML::XMLwriter(3), XMLwriter(3)
A base class for Excel workbooks and worksheets
Sys::RunAlways(3)
make sure there is always one invocation of a script active
Test::FailWarnings(3)
Add test failures if warnings are caught
Test::LWP::UserAgent(3)
A LWP::UserAgent suitable for simulating and testing network calls
Test::Mock::LWP(3)
Easy mocking of LWP packages
Test::Mock::LWP::Dispatch(3)
mocks LWP::UserAgent and dispatches your requests/responses
Test::Mock::LWP::UserAgent(3)
Mocks LWP::UserAgent
Test::Nginx::LWP(3)
LWP-backed test scaffold for the Nginx C modules
Text::Shellwords::Cursor(3)
Parse a string into tokens
Text::VisualWidth(3)
Perl extension for trimming text by the number of the columns of terminals and mobile phones
Text::VisualWidth::EUC_JP(3)
Perl extension for Triming EUC-JP text by the number of the columns of terminals and mobile phones
Text::VisualWidth::UTF8(3), Text::TrimViewWidth::UTF8(3)
Perl extension for Triming UTF-8 text by the number of the columns of terminals and mobile phones
Text::WrapI18N(3)
Line wrapping module with support for multibyte, fullwidth, and combining characters and languages without whitespaces between words
Tk::OlWm(3)
Interface to OpenLook properties of toplevel windows
WWW::Mixi(3)
Mixiアクセス用のLWP::UserAgentモジュール
WWW::Shorten::UserAgent(3)
LWP::UserAgent subclass for WWW::Shorten modules
XML::Compile::SOAP::Daemon::LWPutil(3)
LWP helper routines
XML::Handler::CanonXMLWriter(3)
output XML in canonical XML format
XML::Handler::HTMLWriter(3)
SAX Handler for writing HTML 4.0
XML::Handler::XMLWriter(3)
a PerlSAX handler for writing readable XML
XML::RPC::UA::LWP(3)
XML::RPC useragent, using LWP
avl(3), mkavltree(3), insertavl(3), lookupavl(3), deleteavl(3), avlwalk(3), avlnext(3), avlprev(3), endwalk(3)
AVL tree routines
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
fish-completions(1)
Writing fish completions To specify a completion, use the complete command. complete takes as a parameter the name of the command to specify a completion for. For example, to add a completion for the program myprog, one would start the completion command with complete -c myprog ... To provide a list of possible completions for myprog, use the -a switch. If myprog accepts the arguments start and stop, this can be specified as complete -c myprog -a (aqstart stop(aq. The argument to the -a switch is always a single string. At completion time, it will be tokenized on spaces and tabs, and variable expansion, command substitution and other forms of parameter expansion will take place. fish has a special syntax to support specifying switches accepted by a command. The switches -s, -l and -o are used to specify a short switch (single character, such as -l), a gnu style long switch (such as --color) and an old-style long switch (like -shuffle), respectively. If the command (aqmyprog(aq has an option (aq-o(aq which can also be written as --output, and which can take an additional value of either (aqyes(aq or (aqno(aq, this can be specified by writing: 0.0 3.5 C complete -c myprog -s o -l output -a "yes no" P There are also special switches for specifying that a switch requires an argument, to disable filename completion, to create completions that are only available in some combinations, etc.. For a complete description of the various switches accepted by the complete command, see the documentation for the complete builtin, or write complete --help inside the fish shell. As a more comprehensive example, here(aqs a commented excerpt of the completions for systemd(aqs timedatectl: 0.0 3.5 C # All subcommands that timedatectl knows - this is useful for later. set -l commands status set-time set-timezone list-timezones set-local-rtc set-ntp # Disable file completions for the entire command # because it does not take files anywhere # Note that this can be undone by using "-F". # # File completions also need to be disabled # if you want to have more control over what files are offered # (e.g. just directories, or just files ending in ".mp3"). complete -c timedatectl -f # This line offers the subcommands # -"status", # -"set-timezone", # -"set-time" # -"list-timezones" # if no subcommand has been given so far. # # The (ga-n(ga/(ga--condition(ga option takes script as a string, which it executes. # If it returns true, the completion is offered. # Here the condition is the (ga__fish_seen_subcommands_from(ga helper function. # If returns true if any of the given commands is used on the commandline, # as determined by a simple heuristic. # For more complex uses, you can write your own function. # See e.g. the git completions for an example. # complete -c timedatectl -n "not __fish_seen_subcommand_from $commands" e -a "status set-time set-timezone list-timezones" # If the "set-timezone" subcommand is used, # offer the output of (gatimedatectl list-timezones(ga as completions. # Each line of output is used as a separate candidate, # and anything after a tab is taken as the description. # It(aqs often useful to transform command output with (gastring(ga into that form. complete -c timedatectl -n "__fish_seen_subcommand_from set-timezone" e -a "(timedatectl list-timezones)" # Completion candidates can also be described via (ga-d(ga, # which is useful if the description is constant. # Try to keep these short, because that means the user gets to see more at once. complete -c timedatectl -n "not __fish_seen_subcommand_from $commands" e -a "set-local-rtc" -d "Maintain RTC in local time" # We can also limit options to certain subcommands by using conditions. complete -c timedatectl -n "__fish_seen_subcommand_from set-local-rtc" e -l adjust-system-clock -d (aqSynchronize system clock from the RTC(aq # These are simple options that can be used everywhere. complete -c timedatectl -s h -l help -d (aqPrint a short help text and exit(aq complete -c timedatectl -l version -d (aqPrint a short version string and exit(aq complete -c timedatectl -l no-pager -d (aqDo not pipe output into a pager(aq P For examples of how to write your own complex completions, study the completions in /usr/share/fish/completions. (The exact path depends on your chosen installation prefix and may be slightly different)
libwww::lwpcook(3), lwpcook(3)
The libwww-perl cookbook
libwww::lwptut(3), lwptut(3)
-- An LWP Tutorial
lwp-download(1)
Fetch large files from the web
lwp-dump(1)
See what headers and content is returned for a URL
lwp-mirror(1)
Simple mirror utility
lwp-request(1)
Simple command line user agent
perlwin32(1)
Perl under Windows
r.in.aster(1), r.in.aster (1)
Georeference, rectify, and import Terra-ASTER imagery and relative DEMs using gdalwarp
sqlw_import(1)
import a Field:Value datafile into an SQLite database
sqlw_mail(1)
send mail with data from an SQLite table
urlwatch(1)
monitors webpages for you
vgmplay(1)
the official and always up-to-date player for all VGM files
wxControlWithItems(3)
Functions for wxControlWithItems class
wxHtmlWindow(3)
Functions for wxHtmlWindow class
wxScrollWinEvent(3)
Functions for wxScrollWinEvent class
wxTopLevelWindow(3)
Functions for wxTopLevelWindow class
home | help