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

FreeBSD Manual Pages

  
 
  

home | help
dladdr(3)
find the shared object containing a given address
gshsec(8)
control utility for shared secret devices
ibv_create_srq(3), ibv_destroy_srq(3)
create or destroy a shared receive queue (SRQ)
ibv_create_srq_ex(3), ibv_destroy_srq(3)
create or destroy a shared receive queue (SRQ)
ibv_get_srq_num(3), ibv_get_srq_num (3)
return srq number associated with the given shared receive queue (SRQ)
ibv_modify_srq(3)
modify attributes of a shared receive queue (SRQ)
ibv_open_qp(3)
open a shareable queue pair (QP)
ibv_post_srq_recv(3)
post a list of work requests (WRs) to a shared receive queue (SRQ)
ibv_query_srq(3)
get the attributes of a shared receive queue (SRQ)
ibv_srq_pingpong(1)
simple InfiniBand shared receive queue test
ipcrm(1)
remove the specified message queues, semaphore sets, and shared segments
ldconfig(8)
configure the dynamic linker search path for shared libraries
memfd_create(2), shm_open(2), shm_rename(2), shm_unlink(2)
shared memory object operations
memfd_create(3), shm_open(3), shm_rename(3), shm_unlink(3)
shared memory object operations
mount_smbfs(8)
mount a shared resource from an SMB file server
mpool(3)
shared memory buffer pool
posixshmcontrol(1)
Control POSIX shared memory segments
pthread_barrierattr_destroy(3), pthread_barrierattr_getpshared(3), pthread_barrierattr_init(3), pthread_barrierattr_setpshared(3)
manipulate a barrier attribute object
pthread_condattr_init(3), pthread_condattr_destroy(3), pthread_condattr_getclock(3), pthread_condattr_setclock(3), pthread_condattr_getpshared(3), pthread_condattr_setpshared(3)
condition attribute operations
pthread_mutexattr_init(3), pthread_mutexattr_destroy(3), pthread_mutexattr_setprioceiling(3), pthread_mutexattr_getprioceiling(3), pthread_mutexattr_setprotocol(3), pthread_mutexattr_getprotocol(3), pthread_mutexattr_setpshared(3), pthread_mutexattr_getpshared(3), pthread_mutexattr_setrobust(3), pthread_mutexattr_getrobust(3), pthread_mutexattr_settype(3), pthread_mutexattr_gettype(3)
mutex attribute operations
pthread_rwlockattr_getpshared(3)
get the process shared attribute
pthread_rwlockattr_setpshared(3)
set the process shared attribute
rdma_create_srq(3)
Allocate a shared receive queue
shm_map(9), shm_unmap(9)
map shared memory objects into the kernel's address space
shmat(2), shmdt(2)
attach or detach shared memory
shmctl(2)
shared memory control
shmget(2)
obtain a shared memory identifier
sx(9), sx_init(9), sx_init_flags(9), sx_destroy(9), sx_slock(9), sx_xlock(9), sx_slock_sig(9), sx_xlock_sig(9), sx_try_slock(9), sx_try_xlock(9), sx_sunlock(9), sx_xunlock(9), sx_unlock(9), sx_try_upgrade(9), sx_downgrade(9), sx_sleep(9), sx_xholder(9), sx_xlocked(9), sx_assert(9), SX_SYSINIT(9), SX_SYSINIT_FLAGS(9)
kernel shared/exclusive lock
wpa_passphrase(8)
utility for generating a 256-bit pre-shared WPA key from an ASCII passphrase
xstr(1)
extract strings from C programs to implement shared strings
zfs-share(8)
share and unshare ZFS filesystems
CT_POLICY_EVAL_CTX_new(3), CT_POLICY_EVAL_CTX_free(3), CT_POLICY_EVAL_CTX_get0_cert(3), CT_POLICY_EVAL_CTX_set1_cert(3), CT_POLICY_EVAL_CTX_get0_issuer(3), CT_POLICY_EVAL_CTX_set1_issuer(3), CT_POLICY_EVAL_CTX_get0_log_store(3), CT_POLICY_EVAL_CTX_set_shared_CTLOG_STORE(3), CT_POLICY_EVAL_CTX_get_time(3), CT_POLICY_EVAL_CTX_set_time(3)
Encapsulates the data required to evaluate whether SCTs meet a Certificate Transparency policy
EVP_PKEY_derive_init(3), EVP_PKEY_derive_set_peer(3), EVP_PKEY_derive(3)
derive public key algorithm shared secret
SSL_CTX_set1_curves(3), SSL_CTX_set1_curves_list(3), SSL_set1_curves(3), SSL_set1_curves_list(3), SSL_get1_curves(3), SSL_get_shared_curve(3), SSL_CTX_set_ecdh_auto(3), SSL_set_ecdh_auto(3)
EC supported curve functions
SSL_CTX_set1_groups(3), SSL_CTX_set1_groups_list(3), SSL_set1_groups(3), SSL_set1_groups_list(3), SSL_get1_groups(3), SSL_get_shared_group(3), SSL_CTX_set1_curves(3), SSL_CTX_set1_curves_list(3), SSL_set1_curves(3), SSL_set1_curves_list(3), SSL_get1_curves(3), SSL_get_shared_curve(3)
EC supported curve functions
SSL_get1_supported_ciphers(3), SSL_get_client_ciphers(3), SSL_get_ciphers(3), SSL_CTX_get_ciphers(3), SSL_bytes_to_cipher_list(3), SSL_get_cipher_list(3), SSL_get_shared_ciphers(3)
get list of available SSL_CIPHERs
SSL_get_shared_sigalgs(3), SSL_get_sigalgs(3)
get supported signature algorithms
CT_POLICY_EVAL_CTX_new(3), CT_POLICY_EVAL_CTX_free(3), CT_POLICY_EVAL_CTX_get0_cert(3), CT_POLICY_EVAL_CTX_set1_cert(3), CT_POLICY_EVAL_CTX_get0_issuer(3), CT_POLICY_EVAL_CTX_set1_issuer(3), CT_POLICY_EVAL_CTX_get0_log_store(3), CT_POLICY_EVAL_CTX_set_shared_CTLOG_STORE(3), CT_POLICY_EVAL_CTX_get_time(3), CT_POLICY_EVAL_CTX_set_time(3)
Encapsulates the data required to evaluate whether SCTs meet a Certificate Transparency policy
CT_POLICY_EVAL_CTX_new_ex(3ossl), CT_POLICY_EVAL_CTX_new(3ossl), CT_POLICY_EVAL_CTX_free(3ossl), CT_POLICY_EVAL_CTX_get0_cert(3ossl), CT_POLICY_EVAL_CTX_set1_cert(3ossl), CT_POLICY_EVAL_CTX_get0_issuer(3ossl), CT_POLICY_EVAL_CTX_set1_issuer(3ossl), CT_POLICY_EVAL_CTX_get0_log_store(3ossl), CT_POLICY_EVAL_CTX_set_shared_CTLOG_STORE(3ossl), CT_POLICY_EVAL_CTX_get_time(3ossl), CT_POLICY_EVAL_CTX_set_time(3ossl)
Encapsulates the data required to evaluate whether SCTs meet a Certificate Transparency policy
CURLOPT_SHARE(3)
specify share handle to use
EVP_PKEY-FFC(7ossl)
EVP_PKEY DSA and DH/DHX shared FFC parameters
EVP_PKEY_derive_init(3), EVP_PKEY_derive_set_peer(3), EVP_PKEY_derive(3)
derive public key algorithm shared secret
EVP_PKEY_derive_init(3ossl), EVP_PKEY_derive_init_ex(3ossl), EVP_PKEY_derive_set_peer_ex(3ossl), EVP_PKEY_derive_set_peer(3ossl), EVP_PKEY_derive(3ossl)
derive public key algorithm shared secret
LOAD(7)
load a shared library file
MPIX_Win_allocate_shared(3)
Create an MPI Window object for one-sided communication and allocate memory at each process
MPIX_Win_shared_query(3)
Query the size and base pointer for a patch of a shared memory window
MPI_File_get_position_shared(3)
Returns the current position of the shared file pointer in etype units relative to the current view
MPI_File_iread_shared(3)
Nonblocking read using shared file pointer
MPI_File_iwrite_shared(3)
Nonblocking write using shared file pointer
MPI_File_read_ordered(3)
Collective read using shared file pointer
MPI_File_read_ordered_begin(3)
Begin a split collective read using shared file pointer
MPI_File_read_ordered_end(3)
Complete a split collective read using shared file pointer
MPI_File_read_shared(3)
Read using shared file pointer
MPI_File_seek_shared(3)
Updates the shared file pointer
MPI_File_write_ordered(3)
Collective write using shared file pointer
MPI_File_write_ordered_begin(3)
Begin a split collective write using shared file pointer
MPI_File_write_ordered_end(3)
Complete a split collective write using shared file pointer
MPI_File_write_shared(3)
Write using shared file pointer
MPI_Win_allocate_shared(3)
Create an MPI Window object for one-sided communication and shared memory access, and allocate memory at each process
MPI_Win_shared_query(3)
Query the size and base pointer for a patch of a shared memory window
SDL_CreateThread(3)
Creates a new thread of execution that shares its parent's properties
SSL_CTX_set1_groups(3), SSL_CTX_set1_groups_list(3), SSL_set1_groups(3), SSL_set1_groups_list(3), SSL_get1_groups(3), SSL_get_shared_group(3), SSL_CTX_set1_curves(3), SSL_CTX_set1_curves_list(3), SSL_set1_curves(3), SSL_set1_curves_list(3), SSL_get1_curves(3), SSL_get_shared_curve(3)
EC supported curve functions
SSL_CTX_set1_groups(3ossl), SSL_CTX_set1_groups_list(3ossl), SSL_set1_groups(3ossl), SSL_set1_groups_list(3ossl), SSL_get1_groups(3ossl), SSL_get_shared_group(3ossl), SSL_get_negotiated_group(3ossl), SSL_CTX_set1_curves(3ossl), SSL_CTX_set1_curves_list(3ossl), SSL_set1_curves(3ossl), SSL_set1_curves_list(3ossl), SSL_get1_curves(3ossl), SSL_get_shared_curve(3ossl)
EC supported curve functions
SSL_get1_supported_ciphers(3), SSL_get_client_ciphers(3), SSL_get_ciphers(3), SSL_CTX_get_ciphers(3), SSL_bytes_to_cipher_list(3), SSL_get_cipher_list(3), SSL_get_shared_ciphers(3)
get list of available SSL_CIPHERs
SSL_get1_supported_ciphers(3ossl), SSL_get_client_ciphers(3ossl), SSL_get_ciphers(3ossl), SSL_CTX_get_ciphers(3ossl), SSL_bytes_to_cipher_list(3ossl), SSL_get_cipher_list(3ossl), SSL_get_shared_ciphers(3ossl)
get list of available SSL_CIPHERs
SSL_get_shared_sigalgs(3), SSL_get_sigalgs(3)
get supported signature algorithms
SSL_get_shared_sigalgs(3ossl), SSL_get_sigalgs(3ossl)
get supported signature algorithms
Sympa::WWW::SharedDocument(3Sympa)
Shared document repository and its nodes
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_DecrRefCount.tcl85(3), Tcl_NewObj(3), Tcl_DuplicateObj(3), Tcl_IncrRefCount(3), Tcl_DecrRefCount(3), Tcl_IsShared(3), Tcl_InvalidateStringRep(3)
manipulate Tcl objects
Tcl_DecrRefCount.tcl86(3), Tcl_NewObj(3), Tcl_DuplicateObj(3), Tcl_IncrRefCount(3), Tcl_DecrRefCount(3), Tcl_IsShared(3), Tcl_InvalidateStringRep(3)
manipulate Tcl values
Tcl_DecrRefCount.tcl87(3), Tcl_NewObj(3), Tcl_DuplicateObj(3), Tcl_IncrRefCount(3), Tcl_DecrRefCount(3), Tcl_IsShared(3), Tcl_InvalidateStringRep(3)
manipulate Tcl values
XSetEventQueueOwner(3)
set event queue owner on a shared Xlib/XCB connection
XShmQueryExtension(3), XShmQueryVersion(3), XShmPixmapFormat(3), XShmAttach(3), XShmDetach XShmCreateImage(3), XShmPutImage(3), XShmGetImage(3), XShmCreatePixmap(3), XShmGetEventBase(3)
X Shared Memory extension functions
XcupStoreColors(3)
initialize shareable colormap entries at specific locations
cb_share_config(1)
Import/export parts of Code::Blocks configuration
cisco-decrypt(1)
decrypts an obfuscated Cisco vpn client pre-shared key
cups-browsed(8)
A daemon for browsing the Bonjour broadcasts of shared, remote CUPS printers
curl_share_cleanup(3)
Clean up a shared object
curl_share_init(3)
Create a shared object
curl_share_setopt(3)
Set options for a shared object
curl_share_strerror(3)
return string describing error code
deb-shlibs(5)
Debian shared library information file
deb-symbols(5)
Debian's extended shared library information file
dpkg-gensymbols(1)
generate symbols files (shared library dependency information)
dpkg-shlibdeps(1)
generate shared library substvar dependencies
explain_shmat_or_die(3)
shared memory attach and report errors require_index { "shared memory attach and report errors" }
explain_shmctl_or_die(3)
shared memory control and report errors require_index { "shared memory control and report errors" }
fi_endpoint(3)
Fabric endpoint operations fi_endpoint / fi_scalable_ep / fi_passive_ep / fi_close Allocate or close an endpoint. fi_ep_bind Associate an endpoint with hardware resources, such as event queues, completion queues, counters, address vectors, or shared transmit/receive contexts. fi_scalable_ep_bind Associate a scalable endpoint with an address vector fi_pep_bind Associate a passive endpoint with an event queue fi_enable Transitions an active endpoint into an enabled state. fi_cancel Cancel a pending asynchronous data transfer fi_ep_alias Create an alias to the endpoint fi_control Control endpoint operation. fi_getopt / fi_setopt Get or set endpoint options. fi_rx_context / fi_tx_context / fi_srx_context / fi_stx_context Open a transmit or receive context. fi_tc_dscp_set / fi_tc_dscp_get Convert between a DSCP value and a network traffic class fi_rx_size_left / fi_tx_size_left (DEPRECATED) Query the lower bound on how many RX/TX operations may be posted without an operation returning -FI_EAGAIN. This functions have been deprecated and will be removed in a future version of the library
image_matchstorage(3), image_matchstorage (3)
test if two vids share the same underlying storage
image_sharestorage(3), image_sharestorage (3)
Setup two VIDs to use the same texture store
libchk(1)
checks shared library links of binaries
libcurl-share(3)
how to use the share interface
libdavix(3)
shared library for HTTP I/O
libowfat_mmap_shared(3), mmap_shared(3)
memory map a file for reading and writing
lightning-getsharedsecret(7)
Command for computing an ECDH
mm(3), OSSP mm(3)
Shared Memory Allocation
mono-shlib-cop(1)
Shared Library Usage Checker
netevent(1)
show, share, clone evdev event devices
ocf_heartbeat_EvmsSCC(7)
Manages EVMS Shared Cluster Containers (SCCs) (deprecated)
ocf_heartbeat_Raid1(7)
Manages Linux software RAID (MD) devices on shared storage
ocf_heartbeat_ServeRAID(7)
Enables and disables shared ServeRAID merge groups
ocf_heartbeat_mdraid(7)
Manages Linux software RAID (MD) devices on shared storage
ocf_heartbeat_sfex(7)
Manages exclusive access to shared storage using Shared Disk File EXclusiveness (SF-EX)
open_rawresource(3), open_rawresource (3)
Open a private or shared resource for reading/writing
pkcsslotd(8)
shared memory manager for opencryptoki
pkg-shlib(8), pkg shlib(8)
display which installed package provides a specfic shared library, and the installed packages which require it library is the filename of the library without any leading path, but including the ABI version number. Only exact matches are handled
pnmquantall(1)
run Pnmquant on a bunch of files all at once, so they share a common colormap synopsis
pskgen(8)
Pre-shared key generater and converter for IKE
pvm_shmd(1)
PVM shared memory (2) daemon
read_rawresource(3), read_rawresource (3)
Read a line from the globally shared raw resource handle
sc_DistShellPair_SharedData(3), sc::DistShellPair::SharedData(3)
This is used to store data that must be shared between all cooperating shell pairs
sc_MemoryGrpBuf(3), sc::MemoryGrpBuf< data_t >(3)
The MemoryGrpBuf class provides access to pieces of the global shared memory that have been obtained with MemoryGrp
sc_ShmMessageGrp(3), sc::ShmMessageGrp(3)
The ShmMessageGrp class is an implementation of MessageGrp that allows multiple process to be started that communicate with shared memory
scache(8)
Postfix shared connection cache server
sharesec(1)
Set or get share ACLs
shmcat(1)
dump shared memory segments, files, standard input and/or text
shmidcat(1)
Copies stdin/file to a shared memory block for gtkwave(1)
smbcquotas(1)
Set or get QUOTAs of NTFS 5 shares
smbtar(1)
shell script for backing up SMB/CIFS shares directly to UNIX tape drives
soldumper(1)
Gnash Local Shared Object (LSO) File Dumper
sshare(1)
Tool for listing the shares of associations to a cluster
tsv(n)
Part of the Tcl threading extension allowing script level manipulation of data shared between threads
ttyd(1)
Share your terminal over the web
update-mime-database(1)
a program to build the Shared MIME-Info database cache
upgrade_shared_repository(1), upgrade_shared_repository.pl(1)
Migrating shared repository created by earlier versions
urxvt-remote-clipboard(1), remote-clipboard(1)
manage a shared and possibly remote clipboard
vfs_media_harmony(8)
Allow multiple Avid clients to share a network drive
vfs_readonly(8)
make a Samba share read only for a specified time period
vfs_unityed_media(8)
Allow multiple Avid clients to share a network drive
vfs_widelinks(8)
make a Samba share ignore filesystem symbolic links inside a share
vsl(7), VSL(7)
Varnish Shared Memory Logging
write_rawresource(3), write_rawresource (3)
Write a line from the globally shared raw resource handle
xrdsssadmin(8)
administer simple shared secret keytables
zfs-share(8)
share and unshare ZFS filesystems
zzip_open(3), zzip_open_ext_io(3), zzip_open_shared_io(3)
start usage
AnyEvent::Subprocess::Job::Delegate::Handle(3)
share a filehandle or socket with the child
Apache2::AuthCookie::Base(3)
Common Methods Shared by Apache2 and Apache2_4 AuthCookie Subclasses
Apache::Session::SharedMem(3)
Session management via shared memory
Apache::Session::Store::SharedMem(3)
Store persistent data in shared memory
Badger::Hub(3)
central repository of shared resources
Cache::FastMmap(3)
Uses an mmap'ed file to act as a shared memory interprocess cache
Cache::Mmap(3)
Shared data cache using memory mapped files
Cache::SharedMemoryBackend(3)
-- a shared memory based persistence mechanism
Cache::SharedMemoryCache(3)
-- extends the MemoryCache
Cache::SizeAwareSharedMemoryCache(3)
-- extends Cache::SizeAwareMemoryCache
Carp::Clan::Share(3)
Share your Carp::Clan settings with your whole Clan
Catalyst::Manual::Deployment::SharedHosting(3)
Deploying Catalyst on Shared Hosting
Class::MOP::Mixin::AttributeCore(3)
Core attributes shared by attribute metaclasses
Class::MakeMethods::Basic::Global(3)
Basic shared methods
Crypt::Curve25519(3)
Generate shared secret using elliptic-curve Diffie-Hellman function
DBIx::Class::Migration::ShareDirBuilder(3)
Build a target_dir in /share
Dancer::Plugin::Database::Core(3)
Shared core for D1 and D2 Database plugins
Dancer::SharedData(3)
Shared-data singleton for Dancer
Devel::RingBuffer(3)
Shared memory ring buffers for Perl scripts diagnosis/debug
Dist::Zilla::Plugin::ModuleShareDirs(3)
install a directory's contents as module-based "ShareDir" content
Dist::Zilla::Plugin::ShareDir(3)
install a directory's contents as "ShareDir" content
Dist::Zilla::Role::MintingProfile::ShareDir(3)
something that keeps its minting profile in a sharedir
Dist::Zilla::Role::ShareDir(3)
something that picks a directory to install as shared files
Excel::Writer::XLSX::Package::SharedStrings(3), SharedStrings(3)
A class for writing the Excel XLSX sharedStrings.xml file
FFI::Build(3)
Build shared libraries for use with FFI
File::Cache(3)
Share data between processes via filesystem
File::Share(3)
Extend File::ShareDir to Local Libraries
File::ShareDir(3)
Locate per-dist and per-module shared files
File::ShareDir::Install(3)
Install shared files
File::ShareDir::PAR(3)
File::ShareDir with PAR support
File::ShareDir::PathClass(3)
File::ShareDir returning Path::Class objects
File::ShareDir::ProjectDistDir(3)
Simple set-and-forget using of a '/share' directory in your projects root
File::ShareDir::Tarball(3)
Deal transparently with shared files distributed as tarballs
Filesys::Virtual::DAAP(3)
present a DAAP share as a VFS
Finance::Quote::ZA(3)
Obtain South African stock and prices from www.sharenet.co.za
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
HTML::DOM::CharacterData(3)
A base class shared by HTML::DOM::Text and ::Comment
HTML::FormFu::Role::ContainsElementsSharedWithField(3)
Role for constraints on elements and fields
IO::Lambda::Mutex(3)
wait for a shared resource
IPC::MMA(3)
Shared Memory using Ralf Engelschall's mm library
IPC::Mmap::Share(3)
Safely share structures among processes using anonymous mmap
IPC::ShareLite(3)
Lightweight interface to shared memory
IPC::Shareable(3)
Use shared memory backed variables across processes
IPC::Shareable::SharedMem(3)
Object oriented interface to shared memory
IPC::SharedCache(3)
a Perl module to manage a cache in SysV IPC shared memory
IPC::SharedMem(3)
SysV Shared Memory IPC object class
KinoSearch1::Analysis::Stemmer(3)
reduce related words to a shared root
Log::Dispatch::Base(3)
Code shared by dispatch and output objects
Log::Dispatch::FileShared(3)
Log::Dispatch output class for logging to shared files
MCE::Shared(3)
MCE extension for sharing data supporting threads and processes
MCE::Shared::Array(3)
Array helper class
MCE::Shared::Base(3)
Base package for helper classes
MCE::Shared::Cache(3)
A hybrid LRU-plain cache helper class
MCE::Shared::Condvar(3)
Condvar helper class
MCE::Shared::Handle(3)
Handle helper class
MCE::Shared::Hash(3)
Hash helper class
MCE::Shared::Minidb(3)
A pure-Perl in-memory data store
MCE::Shared::Ordhash(3)
An ordered hash class featuring tombstone deletion
MCE::Shared::Queue(3)
Hybrid-queue helper class
MCE::Shared::Scalar(3)
Scalar helper class
MCE::Shared::Sequence(3)
Sequence helper class
MCE::Shared::Server(3)
Server/Object packages for MCE::Shared
MPI_File_get_position_shared(3)
Returns the current position of the shared file pointer
MPI_File_iread_shared(3)
Reads a file using the shared file pointer (nonblocking, noncollective)
MPI_File_iwrite_shared(3)
Writes a file using the shared file pointer (nonblocking, noncollective)
MPI_File_read_ordered(3)
Reads a file at a location specified by a shared file pointer (blocking, collective)
MPI_File_read_ordered_begin(3)
Reads a file at a location specified by a shared file pointer; beginning part of a split collective routine (nonblocking)
MPI_File_read_ordered_end(3)
Reads a file at a location specified by a shared file pointer; ending part of a split collective routine (blocking)
MPI_File_read_shared(3)
Reads a file using the shared file pointer (blocking, noncollective)
MPI_File_seek_shared(3)
Updates the global shared file pointer (collective)
MPI_File_write_ordered(3)
Writes a file at a location specified by a shared file pointer (blocking, collective)
MPI_File_write_ordered_begin(3)
Writes a file at a location specified by a shared file pointer; beginning part of a split collective routine (nonblocking)
MPI_File_write_ordered_end(3)
Writes a file at a location specified by a shared file pointer; ending part of a split collective routine (blocking)
MPI_File_write_shared(3)
Writes a file using the shared file pointer (blocking, noncollective)
MPI_Win_allocate_shared(3)
One-sided MPI call that allocates shared memory and returns a window object for RMA operations
MPI_Win_shared_query(3)
Query a shared memory window
Mail::ListDetector::Detector::AutoShare(3)
AutoShare message detector
MaxMind::DB::Common(3)
Code shared by the MaxMind DB reader and writer modules
Metabase::User::Secret(3)
Metabase fact for user shared authentication secret
Module::Install::Share(3)
Install non-code files for use during run-time
Moose::Meta::Attribute::Native::Trait(3)
Shared role for native delegation traits
Moose::Meta::Mixin::AttributeCore(3)
Core attributes shared by attribute metaclasses
Net::Curl::Share(3)
Perl interface for curl_share_* functions
Net::HTTP::Methods(3)
Methods shared by Net::HTTP and Net::HTTPS
Net::OpenID::Common(3)
Libraries shared between Net::OpenID::Consumer and Net::OpenID::Server
Net::SSH::Perl::Util(3)
Shared utility functions
PDL::CallExt(3)
call functions in external shared libraries
Perl::Critic::Pulp::PodParser(3)
shared POD parsing code for the Pulp perlcritic add-on
Perl::Critic::Pulp::Utils(3)
shared helper code for the Pulp perlcritic add-on
Pithub::Result::SharedCache(3)
A role to share the LRU cache with all Pithub objects
Pod::Elemental::Transformer::Gatherer(3)
gather related paragraphs under a shared header
Prima::StdBitmap(3)
shared access to the standard toolkit bitmaps
RRDs(3)
Access RRDtool as a shared module
Rex::Shared::Var(3)
Share variables across Rex tasks
SMS::Send::TW::ShareSMS(3)
SMS::Send driver for www.ShareSMS.com
Shared::Examples::Net::Amazon::S3(3)
used for testing and as example
Shared::Examples::Net::Amazon::S3::API(3)
used for testing and as example
Shared::Examples::Net::Amazon::S3::Client(3)
used for testing and as example
Shared::Examples::Net::Amazon::S3::Fixture(3)
used for testing to provide test fixtures
Shared::Examples::Net::Amazon::S3::Fixture::error::access_denied(3)
Shared::Examples providing error fixture
Shared::Examples::Net::Amazon::S3::Fixture::error::bucket_already_exists(3)
Shared::Examples providing error fixture
Shared::Examples::Net::Amazon::S3::Fixture::error::bucket_not_empty(3)
Shared::Examples providing error fixture
Shared::Examples::Net::Amazon::S3::Fixture::error::http_bad_request(3)
Shared::Examples providing error fixture
Shared::Examples::Net::Amazon::S3::Fixture::error::invalid_bucket_name(3)
Shared::Examples providing error fixture
Shared::Examples::Net::Amazon::S3::Fixture::error::invalid_object_state(3)
Shared::Examples providing error fixture
Shared::Examples::Net::Amazon::S3::Fixture::error::no_such_bucket(3)
Shared::Examples providing error fixture
Shared::Examples::Net::Amazon::S3::Fixture::error::no_such_key(3)
Shared::Examples providing error fixture
Shared::Examples::Net::Amazon::S3::Fixture::request::bucket_create_ca_central_1(3)
Shared::Examples providing request fixture
Shared::Examples::Net::Amazon::S3::Fixture::response::acl(3)
Shared::Examples providing response fixture
Shared::Examples::Net::Amazon::S3::Fixture::response::bucket_objects_delete_quiet_without_errors(3)
Shared::Examples providing response fixture
Shared::Examples::Net::Amazon::S3::Fixture::response::bucket_objects_list_v1(3)
Shared::Examples providing response fixture
Shared::Examples::Net::Amazon::S3::Fixture::response::bucket_objects_list_v1_google_cloud_storage(3), Shared::Examples::Net::Amazon::S3::Fixture::response::bucket_objects_list_v1_google_clout_storage(3)
Shared::Examples providing response fixture
Shared::Examples::Net::Amazon::S3::Fixture::response::bucket_objects_list_v1_with_delimiter(3)
Shared::Examples providing response fixture
Shared::Examples::Net::Amazon::S3::Fixture::response::bucket_objects_list_v1_with_filter(3)
Shared::Examples providing response fixture
Shared::Examples::Net::Amazon::S3::Fixture::response::bucket_objects_list_v1_with_filter_truncated(3)
Shared::Examples providing response fixture
Shared::Examples::Net::Amazon::S3::Fixture::response::bucket_objects_list_v1_with_prefix_and_delimiter(3)
Shared::Examples providing response fixture
Shared::Examples::Net::Amazon::S3::Fixture::response::create_multipart_upload_with_success(3), Shared::Examples::Net::Amazon::S3::Fixture::response::create-multipart-upload-with-success(3)
Shared::Examples providing response fixture
Shared::Examples::Net::Amazon::S3::Fixture::response::http_ok_empty(3)
Shared::Examples providing response fixture
Shared::Examples::Net::Amazon::S3::Fixture::response::service_list_buckets_with_owner_displayname(3)
Shared::Examples providing response fixture
Shared::Examples::Net::Amazon::S3::Fixture::response::service_list_buckets_without_owner_displayname(3)
Shared::Examples providing response fixture
Shared::Examples::Net::Amazon::S3::Request(3)
used for testing and as example
Socket::Class::CTX(3), Socket::Class::SSL::CTX(3)
Shared context for Socket::Class::SSL
Software::License::CC_BY_NC_SA_1_0(3)
Creative Commons Attribution-NonCommercial-ShareAlike 1.0 License (CC BY-NC-SA 1.0)
Software::License::CC_BY_NC_SA_2_0(3)
Creative Commons Attribution-NonCommercial-ShareAlike 2.0 License (CC BY-NC-SA 2.0)
Software::License::CC_BY_NC_SA_3_0(3)
Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License (CC BY-NC-SA 3.0)
Software::License::CC_BY_NC_SA_4_0(3)
Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License (CC BY-NC-SA 4.0)
Software::License::CC_BY_SA_1_0(3)
Creative Commons Attribution-ShareAlike 1.0 License (CC BY-SA 1.0)
Software::License::CC_BY_SA_2_0(3)
Creative Commons Attribution-ShareAlike 2.0 License (CC BY-SA 2.0)
Software::License::CC_BY_SA_3_0(3)
Creative Commons Attribution-ShareAlike 3.0 Unported License (CC BY-SA 3.0)
Software::License::CC_BY_SA_4_0(3)
Creative Commons Attribution-ShareAlike 4.0 International License (CC BY-SA 4.0)
Sub::Exporter::GlobExporter(3)
export shared globs with Sub::Exporter collectors
Test2::Harness::Runner::Constants(3)
Constants shared between multiple runner modules
Test::File::ShareDir(3)
Create a Fake ShareDir for your modules for testing
Test::File::ShareDir::Dist(3)
Simplified dist oriented ShareDir tester
Test::File::ShareDir::Module(3)
Simplified module oriented ShareDir tester
Test::File::ShareDir::Object::Dist(3)
Object Oriented ShareDir creation for distributions
Test::File::ShareDir::Object::Inc(3)
Shared tempdir object code to inject into @INC
Test::File::ShareDir::Object::Module(3)
Object Oriented ShareDir creation for modules
Test::File::ShareDir::TempDirObject(3)
Internal Object to make code simpler
Test::File::ShareDir::Utils(3)
Simple utilities for File::ShareDir testing
Test::SharedFork(3)
fork test
Text::MicroMason::AllowGlobals(3)
Share package vars between templates
Tie::ShareLite(3)
Tied hash interface to IPC::ShareLite
Type::Tiny::ConstrainedObject(3)
shared behavour for Type::Tiny::Class, etc
WWW::Shorten::generic(3)
Methods shared across all WWW::Shorten modules
X11::Protocol::Ext::MIT_SHM(3)
images in SysV style shared memory
XML::Smart::Shared(3)
Shared functions and variables for XML::Smart
XML::XBEL::base(3)
shared private methods for XBEL thingies
auto::share::dist::Amon2::flavor::Basic::lib::__PATH__(3), <% $module %>(3)
<% $module %>
auto::share::dist::Amon2::flavor::Minimum::lib::__PATH__(3), <% $module %>(3)
<% $module %>
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: -2) --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 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.15.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) --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 all certificates (or more precisely, certificate lineages) you have previously obtained if they are close to expiry, and print a summary of the results. By default, (aqrenew(aq will reuse the options used to create obtain or most recently successfully renew each certificate lineage. You can try it with (ga--dry-run(ga first. For more fine-grained control, you can renew individual lineages with the (gacertonly(ga subcommand. 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
dcshare(1), run(1)
dc client with file sharing
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)
forks::shared(3)
drop-in replacement for Perl threads::shared with forks()
jmap(1)
Prints shared object memory maps or heap memory details for a process, core file, or remote debug server. This command is experimental and unsupported
threads::shared(3)
Perl extension for sharing data structures between threads
threads::shared::array(3)
default class for tie-ing arrays to threads with forks
threads::shared::handle(3)
default class for tie-ing handles to threads with forks
threads::shared::hash(3)
default class for tie-ing hashes to threads with forks
threads::shared::scalar(3)
default class for tie-ing scalars to threads with forks
home | help