Apropos (2) - FreeBSD 15.1-RELEASE and Ports.quarterly Manual Pages

home | help

SHA224_Init(3), SHA224_Update(3), SHA224_Final(3), SHA224_End(3), SHA224_Fd(3), SHA224_FdChunk(3), SHA224_File(3), SHA224_FileChunk(3), SHA224_Data(3), SHA256_Init(3), SHA256_Update(3), SHA256_Final(3), SHA256_End(3), SHA256_Fd(3), SHA256_FdChunk(3), SHA256_File(3), SHA256_FileChunk(3), SHA256_Data(3): calculate the FIPS 180-2 ``SHA-256'' (or SHA-224) message digest
_exit(2): terminate the calling process
_umtx_op(2): interface for implementation of userspace threading synchronization primitives
abort2(2): abort process with diagnostics
accept(2), accept4(2): accept a connection on a socket
access(2), eaccess(2), faccessat(2): check accessibility of a file
acct(2): enable or disable process accounting
adjtime(2): correct the time to allow synchronization of the system clock
aio_cancel(2): cancel an outstanding asynchronous I/O operation (REALTIME)
aio_error(2): retrieve error status of asynchronous I/O operation (REALTIME)
aio_fsync(2): asynchronous file synchronization (REALTIME)
aio_mlock(2): asynchronous mlock(2) operation
aio_read(2), aio_read2(2), aio_readv(2): asynchronous read from a file (REALTIME)
aio_return(2): retrieve return status of asynchronous I/O operation (REALTIME)
aio_suspend(2): suspend until asynchronous I/O operations or timeout complete (REALTIME)
aio_waitcomplete(2): wait for the next completion of an aio request
aio_write(2), aio_write2(2), aio_writev(2): asynchronous write to a file (REALTIME)
amdsmb(4): AMD-8111 SMBus 2.0 controller driver
au_bsm_to_fcntl_cmd(3), au_fcntl_cmd_to_bsm(3): convert between BSM and local fcntl(2) command values
audit(2): commit BSM audit record to audit log
auditctl(2): configure system audit parameters
auditon(2): configure system audit parameters
bcm283x_pwm(4): bcm283x_pwm - driver for Raspberry Pi 2/3 PWM
bind(2): assign a local protocol address to a socket
bindat(2): assign a local protocol address to a socket
brk(2), sbrk(2): change data segment size
c89(1): POSIX.2 C language compiler
cap_enter(2), cap_getmode(2): Capability mode system calls
cap_fcntls_limit(2), cap_fcntls_get(2): manage allowed fcntl commands
cap_ioctls_limit(2), cap_ioctls_get(2): manage allowed ioctl commands
cap_rights_limit(2): limit capability rights
chdir(2), fchdir(2): change current working directory
chflags(2), lchflags(2), fchflags(2), chflagsat(2): set file flags
chmod(2), fchmod(2), lchmod(2), fchmodat(2): change mode of file
chown(2), fchown(2), lchown(2), fchownat(2): change owner and group of a file
chroot(2), fchroot(2): change root directory
clock_gettime(2), clock_settime(2), clock_getres(2): get/set/calibrate date and time
close(2): delete a descriptor
closefrom(2), close_range(2): delete open file descriptors
connect(2): initiate a connection on a socket
connectat(2): initiate a connection on a socket
copy_file_range(2): kernel copy of a byte range from one regular file to another or within one regular file
cpuset(2), cpuset_getid(2), cpuset_setid(2): manage CPU affinity sets
cpuset_getaffinity(2), cpuset_setaffinity(2): manage CPU affinity
cpuset_getdomain(2), cpuset_setdomain(2): manage memory domain policy
cpuset_parselist(3), domainset_parselist(3): utility functions for cpuset(2) handling
creat(2): create a new file
dup(2), dup2(2): duplicate an existing file descriptor
eventfd(2): create a file descriptor for event notification
execve(2), fexecve(2): execute a file
extattr_delete_fd(2), extattr_delete_file(2), extattr_delete_link(2), extattr_get_fd(2), extattr_get_file(2), extattr_get_link(2), extattr_list_fd(2), extattr_list_file(2), extattr_list_link(2), extattr_set_fd(2), extattr_set_file(2), extattr_set_link(2): system calls to manipulate VFS extended attributes
fcntl(2): file control
fdatasync(2), fsync(2): synchronise changes to a file
ffclock_getcounter(2), ffclock_getestimate(2), ffclock_setestimate(2): Retrieve feed-forward counter, get and set feed-forward clock estimates
fhlink(2), fhlinkat(2): make a hard file link
fhopen(2), fhstat(2), fhstatfs(2): access file via file handle
fhreadlink(2): read value of a symbolic link
flock(2): apply or remove an advisory lock on an open file
fork(2): create a new process
fspacectl(2): space management in a file
futimens(2), utimensat(2): set file access and modification times
getaudit(2), getaudit_addr(2): retrieve audit session state
getauid(2): retrieve audit session ID
getdirentries(2), getdents(2): get directory entries in a file system independent format
getdtablesize(2): get file descriptor limit
getfh(2), lgetfh(2), getfhat(2): get file handle
getfsstat(2): get list of all mounted file systems
getgid(2), getegid(2): get group process identification
getgroups(2): get the calling process' supplementary groups
getitimer(2), setitimer(2): get/set value of interval timer
getlogin(2), getlogin_r(2), setlogin(2): get/set login name
getloginclass(2), setloginclass(2): get/set login class
getpeername(2): get name of connected peer
getpgrp(2): get process group
getpid(2), getppid(2): get parent or calling process identification
getpriority(2), setpriority(2): get/set program scheduling priority
getrandom(2): get random data
getresgid(2), getresuid(2), setresgid(2), setresuid(2): get or set real, effective and saved user or group ID
getrlimit(2), setrlimit(2): control maximum system resource consumption
getrlimitusage(2): Query usage of the current process' limited resources
getrusage(2): get information about resource utilization
getsid(2): get process session
getsockname(2): get socket name
getsockopt(2), setsockopt(2): get and set options on sockets
gettimeofday(2), settimeofday(2): get/set date and time
getuid(2), geteuid(2): get user identification
ibv_rate_to_mult(3): convert IB rate enumeration to multiplier of 2.5 Gbit/sec mult_to_ibv_rate - convert multiplier of 2.5 Gbit/sec to an IB rate enumeration
igc(4): Intel Ethernet Controller I225 2.5GbE driver
inotify_init(2), inotify_init1(2), inotify_add_watch(2), inotify_add_watch_at(2), inotify_rm_watch(2): monitor file system events
intro(2), errno(2): introduction to system calls and their error numbers
ioctl(2): control device
ismt(4): Intel SMBus Message Transport (SMBus 2.0) driver
issetugid(2): is current process tainted by uid or gid changes
jail(2), jail_get(2), jail_set(2), jail_remove(2), jail_attach(2), jail_remove_jd(2), jail_attach_jd(2): create and manage system jails
kcmp(2): compare two kernel objects
kenv(2): kernel environment
kill(2): send signal to a process
killpg(2): send signal to a process group
kldfind(2): returns the fileid of a kld file
kldfirstmod(2): return first module id from the kld file specified
kldload(2): load KLD files into the kernel
kldnext(2): return the fileid of the next kld file
kldstat(2): get status of kld file
kldsym(2): look up address by symbol name in a KLD
kldunload(2), kldunloadf(2): unload kld files
kqueue(2), kevent(2): kernel event notification mechanism
ktrace(2): process tracing
ldexp(3), ldexpf(3), ldexpl(3): multiply floating-point number by integral power of 2
link(2), linkat(2): make a hard file link
lio_listio(2): list directed I/O (REALTIME)
listen(2): listen for connections on a socket
lseek(2): reposition read/write file offset
madvise(2), posix_madvise(2): give advice about use of memory
membarrier(2): memory barrier
memfd_create(2), shm_create_largepage(2), shm_open(2), shm_rename(2), shm_unlink(2): shared memory object operations
mincore(2): determine residency of memory pages
minherit(2): control the inheritance of pages
mkdir(2), mkdirat(2): make a directory file
mkfifo(2), mkfifoat(2): make a fifo file
mknod(2), mknodat(2): make a special file node
mlock(2), munlock(2): lock (unlock) physical pages in memory
mlockall(2), munlockall(2): lock (unlock) the address space of a process
mmap(2): allocate memory, or map files or devices into memory
modfind(2): returns the modid of a kernel module
modnext(2): return the modid of the next kernel module
modstat(2): get status of kernel module
mount(2), nmount(2), unmount(2): mount or dismount a file system
mprotect(2): control the protection of pages
mps(4): LSI Fusion-MPT 2 IT/IR 6Gb/s Serial Attached SCSI/SATA driver
mpsutil(8), mprutil(8): Utility for managing LSI Fusion-MPT 2/3 controllers
mq_close(2): close a message queue (REALTIME)
mq_getattr(2): get message queue attributes (REALTIME)
mq_notify(2): notify process that a message is available (REALTIME)
mq_open(2): open a message queue (REALTIME)
mq_receive(2), mq_timedreceive(2): receive a message from message queue (REALTIME)
mq_send(2), mq_timedsend(2): send a message to message queue (REALTIME)
mq_setattr(2): set message queue attributes (REALTIME)
mq_unlink(2): mq_unlink - remove a message queue (REALTIME)
msgctl(2): message control operations
msgget(2): get message queue
msgrcv(2): receive a message from a message queue
msgsnd(2): send a message to a message queue
msync(2): synchronize a mapped region
munmap(2): remove a mapping
nanosleep(2): high resolution sleep
nfsmb(4): NVIDIA nForce2/3/4 SMBus 2.0 controller driver
nfssvc(2): NFS services
ntp_adjtime(2), ntp_gettime(2): Network Time Protocol daemon (ntpd) interface system calls
open(2), openat(2): open or create a file for reading, writing or executing
pathconf(2), lpathconf(2), fpathconf(2): get configurable pathname variables
pdfork(2), pdrfork(2), pdgetpid(2), pdkill(2), pdwait(2): System calls to manage process descriptors
pipe(2), pipe2(2): create descriptor pair for interprocess communication
pnfs(4), pNFS(4): NFS Version 4.1 and 4.2 Parallel NFS Protocol
pnfsserver(4), pNFSserver(4): NFS Version 4.1 and 4.2 Parallel NFS Protocol Server
poll(2): synchronous I/O multiplexing
posix_fadvise(2): give advice about use of file data
posix_fallocate(2): pre-allocate storage for a range in a file
posix_openpt(2): open a pseudo-terminal device
procctl(2): control processes
profil(2): control process profiling
pselect(2): synchronous I/O multiplexing a la POSIX.1g
psm(4): PS/2 mouse style pointing device driver
ptrace(2): process tracing and debugging
quotactl(2): manipulate file system quotas
rctl_add_rule(2), rctl_get_limits(2), rctl_get_racct(2), rctl_get_rules(2), rctl_remove_rule(2): manipulate and query the resource limits database
re_format(7): POSIX 1003.2 regular expressions
read(2), readv(2), pread(2), preadv(2): read input
readlink(2), readlinkat(2): read value of a symbolic link
reboot(2): reboot system or halt processor
recv(2), recvfrom(2), recvmsg(2), recvmmsg(2): receive message(s) from a socket
rename(2): change the name of a file
revoke(2): revoke file access
rfork(2): manipulate process resources
rmdir(2): remove a directory file
rndtest(4): FIPS 140-2 random number generator test monitor
rtprio(2), rtprio_thread(2): examine or modify realtime or idle priority
sbp(4): Serial Bus Protocol 2 (SBP-2) Mass Storage Devices driver
sbp_targ(4): Serial Bus Protocol 2 (SBP-2) Target Mode devices driver
sched_get_priority_max(2), sched_get_priority_min(2), sched_rr_get_interval(2): get scheduling parameter limits
sched_setparam(2), sched_getparam(2): set/get scheduling parameters
sched_setscheduler(2), sched_getscheduler(2): set/get scheduling policy and scheduler parameters
sched_yield(2): yield processor
sctp_generic_recvmsg(2): receive data from a peer
sctp_generic_sendmsg(2), sctp_generic_sendmsg_iov(2): send data to a peer
sctp_peeloff(2): detach an association from a one-to-many socket to its own fd
select(2): synchronous I/O multiplexing
semctl(2): control operations on a semaphore set
semget(2): obtain a semaphore id
semop(2): atomic array of operations on a semaphore set
send(2), sendto(2), sendmsg(2), sendmmsg(2): send message(s) from a socket
sendfile(2): send a file to a socket
setaudit(2), setaudit_addr(2): set audit session state
setauid(2): set audit session ID
setcred(2): set current process credentials atomically
setfib(2): set the default FIB (routing table) for the calling process
setgroups(2): set the calling process' supplementary groups
setpgid(2), setpgrp(2): set process group
setregid(2): set real and effective group ID
setreuid(2): set real and effective user ID's
setsid(2): create session and set process group ID
setuid(2), seteuid(2), setgid(2), setegid(2): set user and group ID
shmat(2), shmdt(2): attach or detach shared memory
shmctl(2): shared memory control
shmget(2): obtain a shared memory identifier
shutdown(2): disable sends and/or receives on a socket
sigaction(2): software signal facilities
sigaltstack(2): set and/or get signal stack context
sigfastblock(2): controls signals blocking with a simple memory write
sighold(2), sigignore(2), sigpause(2), sigrelse(2), sigset(2): legacy interface for signal management
sigpending(2): get pending signals
sigprocmask(2): manipulate current signal mask
sigqueue(2): queue a signal to a process (REALTIME)
sigreturn(2): return from signal
sigsetmask(2), sigblock(2): manipulate current signal mask
sigstack(2): set and/or get signal stack context
sigsuspend(2): atomically release blocked signals and wait for interrupt
sigtimedwait(2), sigwaitinfo(2): wait for queued signals (REALTIME)
sigvec(2): software signal facilities
sigwait(2): select a set of signals
snmp_mibII(3), mibII(3), mibif_notify_f(3), mib_netsock(3), mib_if_set_dyn(3), mib_refresh_iflist(3), mib_find_if(3), mib_find_if_sys(3), mib_find_if_name(3), mib_first_if(3), mib_next_if(3), mib_register_newif(3), mib_unregister_newif(3), mib_fetch_ifmib(3), mib_if_admin(3), mib_find_ifa(3), mib_first_ififa(3), mib_next_ififa(3), mib_ifstack_create(3), mib_ifstack_delete(3), mib_find_rcvaddr(3), mib_rcvaddr_create(3), mib_rcvaddr_delete(3), mibif_notify(3), mibif_unnotify(3): mib-2 module for bsnmpd
socket(2): create an endpoint for communication
socketpair(2): create a pair of connected sockets
stat(2), lstat(2), fstat(2), fstatat(2): get file status
statfs(2): get file system statistics
stdc_bit_ceil(3): round up to the next power of~2
stdc_bit_floor(3): round down to the previous power of~2
swapon(2), swapoff(2): control devices for interleaved paging/swapping
symlink(2), symlinkat(2): make symbolic link to a file
sync(2): schedule file system updates
sysarch(2): architecture-dependent system call
syscall(2), __syscall(2): indirect system call
thr_exit(2): terminate current thread
thr_kill(2): send signal to thread
thr_new(2): create new thread of execution
thr_self(2): return thread identifier for the calling thread
thr_set_name(2): set user-visible thread name
thr_suspend(2): suspend the calling thread
thr_wake(2): wake up the suspended thread
timer_create(2): create a per-process timer (REALTIME)
timer_delete(2): delete a per-process timer (REALTIME)
timer_getoverrun(2), timer_gettime(2), timer_settime(2): per-process timers (REALTIME)
timerfd(2), timerfd_create(2), timerfd_gettime(2), timerfd_settime(2): timers with file descriptor semantics
truncate(2), ftruncate(2): truncate or extend a file to a specified length
umask(2): set file creation mode mask
undelete(2): attempt to recover a deleted file
unlink(2), unlinkat(2), funlinkat(2): remove directory entry
utimes(2), lutimes(2), futimes(2), futimesat(2): set file access and modification times
utrace(2): insert user record in ktrace log
uuidgen(2): generate universally unique identifiers
vfork(2): create a new process without copying the address space
wait(2), waitid(2), waitpid(2), wait3(2), wait4(2), wait6(2): wait for processes to change status
write(2), writev(2), pwrite(2), pwritev(2): write output
EVP_mdc2(3): MDC-2 For EVP
EVP_sha224(3), EVP_sha256(3), EVP_sha512_224(3), EVP_sha512_256(3), EVP_sha384(3), EVP_sha512(3): SHA-2 For EVP
2diff(1): 2.11BSD differential file and directory comparator
CURLOPT_XOAUTH2_BEARER(3): OAuth 2.0 access token
DC_CTX_new(2), DC_CTX_free(2), DC_CTX_add_session(2), DC_CTX_remove_session(2), DC_CTX_get_session(2), DC_CTX_reget_session(2), DC_CTX_has_session(2): distcache blocking client API
DC_PLUG_new(2), DC_PLUG_free(2), DC_PLUG_to_select(2), DC_PLUG_io(2): basic DC_PLUG functions
DC_PLUG_read(2), DC_PLUG_consume(2), DC_PLUG_write(2), DC_PLUG_write_more(2), DC_PLUG_commit(2), DC_PLUG_rollback(2): DC_PLUG read/write functions
DC_SERVER_set_default_cache(2), DC_SERVER_set_cache(2), DC_SERVER_new(2), DC_SERVER_free(2), DC_SERVER_items_stored(2), DC_SERVER_reset_operations(2), DC_SERVER_num_operations(2), DC_SERVER_new_client(2), DC_SERVER_del_client(2), DC_SERVER_process_client(2), DC_SERVER_clients_to_sel(2), DC_SERVER_clients_io(2): distcache server API
DPGEN_ROM2(3): 2 words ROM Macro-Generator
EVP_mdc2(3ossl): MDC-2 For EVP
EVP_rc2_cbc(3), EVP_rc2_ecb(3), EVP_rc2_cfb64(3), EVP_rc2_cfb(3), EVP_rc2_ofb(3), EVP_rc2_40_cbc(3), EVP_rc2_64_cbc(3): Rivest Cipher 2 in the EVP framework
EVP_sha224(3ossl), EVP_sha256(3ossl), EVP_sha512_224(3ossl), EVP_sha512_256(3ossl), EVP_sha384(3ossl), EVP_sha512(3ossl): SHA-2 For EVP
HPL_lmul(3): multiplies 2 long positive integers
HPL_perm(3): Combine 2 index arrays - Generate the permutation
IV_WAIT_INTEREST_INIT(3), iv_wait_interest_register(3), iv_wait_interest_register_spawn(3), iv_wait_interest_unregister(3), iv_wait_interest_kill(3): ivykis wait4 (2) wrapper
NAL_ADDRESS_new(2), NAL_ADDRESS_free(2), NAL_ADDRESS_create(2), NAL_ADDRESS_set_def_buffer_size(2), NAL_ADDRESS_can_connect(2), NAL_ADDRESS_can_listen(2): libnal addressing functions
NAL_BUFFER_new(2), NAL_BUFFER_free(2), NAL_BUFFER_set_size(2), NAL_BUFFER_empty(2), NAL_BUFFER_full(2), NAL_BUFFER_notempty(2), NAL_BUFFER_notfull(2), NAL_BUFFER_used(2), NAL_BUFFER_unused(2), NAL_BUFFER_data(2), NAL_BUFFER_size(2), NAL_BUFFER_write(2), NAL_BUFFER_read(2), NAL_BUFFER_write_ptr(2), NAL_BUFFER_takedata(2), NAL_BUFFER_wrote(2): libnal buffer functions
NAL_CONNECTION_new(2), NAL_CONNECTION_free(2), NAL_CONNECTION_create(2), NAL_CONNECTION_create_pair(2), NAL_CONNECTION_create_dummy(2), NAL_CONNECTION_set_size(2), NAL_CONNECTION_get_read(2), NAL_CONNECTION_get_send(2), NAL_CONNECTION_io(2), NAL_CONNECTION_io_cap(2), NAL_CONNECTION_is_established(2), NAL_CONNECTION_add_to_selector(2), NAL_CONNECTION_del_from_selector(2): libnal connection functions
NAL_LISTENER_new(2), NAL_LISTENER_free(2), NAL_LISTENER_create(2): libnal listener functions
NAL_SELECTOR_new(2), NAL_SELECTOR_free(2), NAL_SELECTOR_reset(2), NAL_SELECTOR_select(2): libnal selector functions
NAL_decode_uint32(2), NAL_decode_uint16(2), NAL_decode_char(2), NAL_decode_bin(2), NAL_encode_uint32(2), NAL_encode_uint16(2), NAL_encode_char(2), NAL_encode_bin(2): libnal serialisation functions
RC2_set_key(3), RC2_encrypt(3), RC2_decrypt(3), RC2_cbc_encrypt(3), RC2_ecb_encrypt(3), RC2_cfb64_encrypt(3), RC2_ofb64_encrypt(3): low-level functions for Rivest Cipher 2
RNA2Dfold(1): manual page for RNA2Dfold 2.7.2
RNALalifold(1): manual page for RNALalifold 2.7.2
RNALfold(1): manual page for RNALfold 2.7.2
RNAPKplex(1): manual page for RNAPKplex 2.7.2
RNAaliduplex(1): manual page for RNAaliduplex 2.7.2
RNAalifold(1): manual page for RNAalifold 2.7.2
RNAcofold(1): manual page for RNAcofold 2.7.2
RNAdistance(1): manual page for RNAdistance 2.7.2
RNAdos(1): manual page for RNAdos 2.7.2
RNAduplex(1): manual page for RNAduplex 2.7.2
RNAeval(1): manual page for RNAeval 2.7.2
RNAfold(1): manual page for RNAfold 2.7.2
RNAheat(1): manual page for RNAheat 2.7.2
RNAinverse(1): manual page for RNAinverse 2.7.2
RNAlocmin(1): manual page for RNAlocmin 2.1.0
RNAmultifold(1): manual page for RNAmultifold 2.7.2
RNApaln(1): manual page for RNApaln 2.7.2
RNAparconv(1): manual page for RNAparconv 2.7.2
RNApdist(1): manual page for RNApdist 2.7.2
RNAplex(1): manual page for RNAplex 2.7.2
RNAplfold(1): manual page for RNAplfold 2.7.2
RNAplot(1): manual page for RNAplot 2.7.2
RNApvmin(1): manual page for RNApvmin 2.7.2
RNAsnoop(1): manual page for RNAsnoop 2.7.2
RNAsubopt(1): manual page for RNAsubopt 2.7.2
RNAup(1): manual page for RNAup 2.7.2
SDLmm_SPoint(3), SDLmm::SPoint(3): A small usefull class representing a point in 2 dimensional space
TPMLIB_SetProfile(3), TPMLIB_SetProfile (3): Set a profile for a TPM 2
abc2ly(1): manual page for abc2ly (LilyPond) 2.27.1
afterstep_faq(1x): This document is an ever growing set of questions, statements, ideas and complaints about AfterStep version 2.0
alephone(6): game engine based on Marathon 2
apachecouchdb(1): Apache CouchDB® 3.5.2
arandr(1): visual front end for XRandR 1.2
au_fcntl_cmd(3), au_bsm_to_fcntl_cmd(3), au_fcntl_cmd_to_bsm(3): convert between BSM and local fcntl(2) command values
audit(2): commit BSM audit record to audit log
auditctl(2): configure system audit parameters
auditon(2): configure system audit parameters
barman-cloud-backup(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-backup [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ { { -z | --gzip } | { -j | --bzip2 } | --snappy | --lz4 } ] [ { -h | --host } HOST ] [ { -p | --port } PORT ] [ { -U | --user } USER ] [ { -d | --dbname } DBNAME ] [ { -n | --name } BACKUP_NAME ] [ { -J | --jobs } JOBS ] [ { -S | --max-archive-size } MAX_ARCHIVE_SIZE ] [ --immediate-checkpoint ] [ --min-chunk-size MIN_CHUNK_SIZE ] [ --max-bandwidth MAX_BANDWIDTH ] [ --snapshot-instance SNAPSHOT_INSTANCE ] [ --snapshot-disk NAME [ --snapshot-disk NAME ... ] ] [ --snapshot-zone GCP_ZONE ] [ -snapshot-gcp-project GCP_PROJECT ] [ --tag KEY,VALUE [ --tag KEY,VALUE ... ] ] [ --endpoint-url ENDPOINT_URL ] [ --addressing-style { auto | virtual | path } ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ { -e | --encryption } { AES256 | aws:kms } ] [ --sse-kms-key-id SSE_KMS_KEY_ID ] [ --aws-region AWS_REGION ] [ --aws-await-snapshots-timeout AWS_AWAIT_SNAPSHOTS_TIMEOUT ] [ --aws-snapshot-lock-mode { compliance | governance } ] [ --aws-snapshot-lock-duration DAYS ] [ --aws-snapshot-lock-cool-off-period HOURS ] [ --aws-snapshot-lock-expiration-date DATETIME ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [ --encryption-scope ENCRYPTION_SCOPE ] [ --azure-subscription-id AZURE_SUBSCRIPTION_ID ] [ --azure-resource-group AZURE_RESOURCE_GROUP ] [ --gcp-project GCP_PROJECT ] [ --kms-key-name KMS_KEY_NAME ] [ --gcp-zone GCP_ZONE ] DESTINATION_URL SERVER_NAME Description The barman-cloud-backup script is used to create a local backup of a Postgres server and transfer it to a supported cloud provider, bypassing the Barman server. It can also be utilized as a hook script for copying Barman backups from the Barman server to one of the supported clouds (post_backup_retry_script). This script requires read access to PGDATA and tablespaces, typically run as the postgres user. When used on a Barman server, it requires read access to the directory where Barman backups are stored. If --snapshot- arguments are used and snapshots are supported by the selected cloud provider, the backup will be performed using snapshots of the specified disks (--snapshot-disk). The backup label and metadata will also be uploaded to the cloud. Note: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. To use an alternative GCP universe (e.g. S3NS/T-Systems), set the GOOGLE_CLOUD_UNIVERSE_DOMAIN environment variable to the desired universe domain. Important: 0.0 3.5 The cloud upload may fail if any file larger than the configured --max-archive-size is present in the data directory or tablespaces. However, Postgres files up to 1GB are always allowed, regardless of the --max-archive-size setting. Parameters 0.0 SERVER_NAME Name of the server to be backed up. DESTINATION_URL URL of the cloud destination, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. -z / --gzip gzip-compress the backup while uploading to the cloud (should not be used with python < 3.2). -j / --bzip2 bzip2-compress the backup while uploading to the cloud (should not be used with python < 3.3). --snappy snappy-compress the backup while uploading to the cloud (requires optional python-snappy library). --lz4 lz4-compress the backup while uploading to the cloud (requires optional lz4 Python library). -h / --host Host or Unix socket for Postgres connection (default: libpq settings). -p / --port Port for Postgres connection (default: libpq settings). -U / --user User name for Postgres connection (default: libpq settings). -d / --dbname Database name or conninfo string for Postgres connection (default: (dqpostgres(dq). -n / --name A name which can be used to reference this backup in commands such as barman-cloud-restore and barman-cloud-backup-delete. -J / --jobs Number of subprocesses to upload data to cloud storage (default: 2). -S / --max-archive-size Maximum size of an archive when uploading to cloud storage (default: 100GB). --immediate-checkpoint Forces the initial checkpoint to be done as quickly as possible. --min-chunk-size Minimum size of an individual chunk when uploading to cloud storage (default: 5MB for aws-s3, 64KB for azure-blob-storage, not applicable for google-cloud-storage). --max-bandwidth The maximum amount of data to be uploaded per second when backing up to object storages (default: 0 - no limit). --snapshot-instance Instance where the disks to be backed up as snapshots are attached. --snapshot-disk Name of a disk from which snapshots should be taken. --tag Tag to be added to all uploaded files in cloud storage, and/or to snapshots created, if snapshots are used. --tags Tags to be added to all uploaded files in cloud storage, and/or to snapshots created, if snapshots are used. Note: 0.0 3.5 If you are using --tags before positional arguments, you must insert -- after it to indicate the end of optional arguments. This tells the parser to treat everything after -- as positional arguments. Without the --, Barman may misinterpret positional arguments as values for the last option. Deprecated since version 3.15: --tags is deprecated. Use --tag instead. Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. --addressing-style The addressing style to use for S3 requests. This is useful when connecting to S3-compatible services that require a specific addressing style. Allowed options are: 7.0 (bu 2 auto (default): Uses the addressing style determined by the underlying library. (bu 2 virtual: Uses virtual-hosted style addressing (e.g., bucket-name.s3.amazonaws.com). (bu 2 path: Uses path-style addressing (e.g., s3.amazonaws.com/bucket-name). -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file): replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). -e / --encryption The encryption algorithm used when storing the uploaded data in S3. Allowed options: 7.0 (bu 2 AES256. (bu 2 aws:kms. --sse-kms-key-id The AWS KMS key ID that should be used for encrypting the uploaded data in S3. Can be specified using the key ID on its own or using the full ARN for the key. Only allowed if -e / --encryption is set to aws:kms. --aws-region The name of the AWS region containing the EC2 VM and storage volumes defined by the --snapshot-instance and --snapshot-disk arguments. --aws-await-snapshots-timeout The length of time in seconds to wait for snapshots to be created in AWS before timing out (default: 3600 seconds). --aws-snapshot-lock-mode The lock mode for the snapshot. This is only valid if --snapshot-instance and --snapshot-disk are set. Allowed options: 7.0 (bu 2 compliance. (bu 2 governance. --aws-snapshot-lock-duration The lock duration is the period of time (in days) for which the snapshot is to remain locked, ranging from 1 to 36,500. Set either the lock duration or the expiration date (not both). --aws-snapshot-lock-cool-off-period The cooling-off period is an optional period of time (in hours) that you can specify when you lock a snapshot in compliance mode, ranging from 1 to 72. --aws-snapshot-lock-expiration-date The lock duration is determined by an expiration date in the future. It must be at least 1 day after the snapshot creation date and time, using the format YYYY-MM-DDTHH:MM:SS.sssZ. Set either the lock duration or the expiration date (not both). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default. --encryption-scope The name of an encryption scope defined in the Azure Blob Storage service which is to be used to encrypt the data in Azure. --azure-subscription-id The ID of the Azure subscription which owns the instance and storage volumes defined by the --snapshot-instance and --snapshot-disk arguments. --azure-resource-group The name of the Azure resource group to which the compute instance and disks defined by the --snapshot-instance and --snapshot-disk arguments belong. Extra options for GCP cloud provider 0.0 --gcp-project GCP project under which disk snapshots should be stored. --snapshot-gcp-project (deprecated) GCP project under which disk snapshots should be stored - replaced by --gcp-project. --kms-key-name The name of the GCP KMS key which should be used for encrypting the uploaded data in GCS. --gcp-zone Zone of the disks from which snapshots should be taken. --snapshot-zone (deprecated) Zone of the disks from which snapshots should be taken - replaced by --gcp-zone
barman-cloud-backup-delete(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-backup-delete [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ --endpoint-url ENDPOINT_URL ] [ --addressing-style { auto | virtual | path } ] [ { -r | --retention-policy } RETENTION_POLICY ] [ { -m | --minimum-redundancy } MINIMUM_REDUNDANCY ] [ { -b | --backup-id } BACKUP_ID] [ --dry-run ] [ --check-object-lock ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [--batch-size DELETE_BATCH_SIZE] SOURCE_URL SERVER_NAME Description The barman-cloud-backup-delete script is used to delete one or more backups created with the barman-cloud-backup command from cloud storage and to remove the associated WAL files. Backups can be specified for deletion either by their backup ID (as obtained from barman-cloud-backup-list) or by a retention policy. Retention policies mirror those used by the Barman server, deleting all backups that are not required to meet the specified policy. When a backup is deleted, any unused WAL files associated with that backup are also removed. WALs are considered unused if: 0.0 (bu 2 The WALs predate the begin_wal value of the oldest remaining backup. (bu 2 The WALs are not required by any archival backups stored in the cloud. Note: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. To use an alternative GCP universe (e.g. S3NS/T-Systems), set the GOOGLE_CLOUD_UNIVERSE_DOMAIN environment variable to the desired universe domain. Important: 0.0 3.5 Each backup deletion involves three separate requests to the cloud provider: one for the backup files, one for the backup.info file, and one for the associated WALs. Deleting by retention policy may result in a high volume of delete requests if a large number of backups are accumulated in cloud storage. Important: 0.0 3.5 Starting with AWS boto3 1.36, the behavior of Data Integrity Protection checks has changed. Some methods used by Barman no longer require the Content-MD5 header. This means that S3-compatible storage providers that have not updated their server-side code may fail when used with newer boto3 versions. For example, MinIO addressed this change shortly after the boto3 1.36 announcement. If you are using MinIO, you must upgrade to the latest release (or at least RELEASE.2025-02-03T21-03-04Z or newer) to ensure compatibility and avoid failures. Parameters 0.0 SERVER_NAME Name of the server that holds the backup to be deleted. SOURCE_URL URL of the cloud source, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options are: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. -b / --backup-id ID of the backup to be deleted. You can use a shortcut instead of the backup ID. -m / --minimum-redundancy The minimum number of backups that should always be available. -r / --retention-policy If specified, delete all backups eligible for deletion according to the supplied retention policy. Syntax: REDUNDANCY value | RECOVERY WINDOW OF value { DAYS | WEEKS | MONTHS } --batch-size The maximum number of objects to be deleted in a single request to the cloud provider. If unset then the maximum allowed batch size for the specified cloud provider will be used (1000 for aws-s3, 256 for azure-blob-storage and 100 for google-cloud-storage). --dry-run Find the objects which need to be deleted but do not delete them. Extra options for the AWS cloud provider 0.0 --check-object-lock Check whether backup files are protected by S3 Object Lock before attempting deletion. Enable this when your S3 bucket has Object Lock configured and you want to ensure deletion operations respect object-level retention policies. If any base backup file is locked (either by an active retention period or legal hold), the deletion is aborted with an error. For performance reasons, lock checks are only performed for base backup files, since once the base backup is removed, the corresponding WAL files are no longer useful. Note that this check requires one request per file to check the lock status, which may increase deletion time for backups with many files. This feature is only available for AWS S3-compatible object stores and it also requires the s3:GetObjectRetention and s3:GetObjectLegalHold IAM permissions. --endpoint-url Override default S3 endpoint URL with the given one. --addressing-style The addressing style to use for S3 requests. This is useful when connecting to S3-compatible services that require a specific addressing style. Allowed options are: 7.0 (bu 2 auto (default): Uses the addressing style determined by the underlying library. (bu 2 virtual: Uses virtual-hosted style addressing (e.g., bucket-name.s3.amazonaws.com). (bu 2 path: Uses path-style addressing (e.g., s3.amazonaws.com/bucket-name). -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file): replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
barman-cloud-backup-keep(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-backup-keep [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ --endpoint-url ENDPOINT_URL ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ --addressing-style { auto | virtual | path } ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [ { { -r | --release } | { -s | --status } | --target { full | standalone } } ] SOURCE_URL SERVER_NAME BACKUP_ID Description Use this script to designate backups in cloud storage as archival backups, ensuring their indefinite retention regardless of retention policies. This script allows you to mark backups previously created with barman-cloud-backup as archival backups. Once flagged as archival, these backups are preserved indefinitely and are not subject to standard retention policies. Note: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. To use an alternative GCP universe (e.g. S3NS/T-Systems), set the GOOGLE_CLOUD_UNIVERSE_DOMAIN environment variable to the desired universe domain. Important: 0.0 3.5 Starting with AWS boto3 1.36, the behavior of Data Integrity Protection checks has changed. Some methods used by Barman no longer require the Content-MD5 header. This means that S3-compatible storage providers that have not updated their server-side code may fail when used with newer boto3 versions. For example, MinIO addressed this change shortly after the boto3 1.36 announcement. If you are using MinIO, you must upgrade to the latest release (or at least RELEASE.2025-02-03T21-03-04Z or newer) to ensure compatibility and avoid failures when releasing a keep annotation. Parameters 0.0 SERVER_NAME Name of the server that holds the backup to be kept. SOURCE_URL URL of the cloud source, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. BACKUP_ID The ID of the backup to be kept. You can use a shortcut instead of the backup ID. -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options are: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. -r / --release If specified, the command will remove the keep annotation and the backup will be eligible for deletion. -s / --status Print the keep status of the backup. --target Specify the recovery target for this backup. Allowed options are: 7.0 (bu 2 full (bu 2 standalone Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file): replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). --addressing-style The S3 addressing style to use when connecting to S3-compatible cloud storage. This option is useful when using custom S3 endpoints (such as MinIO) that may require a specific addressing style. Allowed options: 7.0 (bu 2 auto (default): Uses the addressing style determined by the boto3 library. (bu 2 virtual: Uses virtual-hosted-style addressing (bucket-name.s3.amazonaws.com). (bu 2 path: Uses path-style addressing (s3.amazonaws.com/bucket-name). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
barman-cloud-backup-list(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-backup-list [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ --endpoint-url ENDPOINT_URL ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ --addressing-style { auto | virtual | path } ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [ --format FORMAT ] SOURCE_URL SERVER_NAME Description This script lists backups stored in the cloud that were created using the barman-cloud-backup command. Backups in any state are included in the listing. Completed backups (status DONE) show their end time and, where applicable, their archival keep target (e.g. KEEP:FULL). In-progress or failed backups show their status (e.g. STARTED) in the Archival Status column and an empty End Time. Note: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. To use an alternative GCP universe (e.g. S3NS/T-Systems), set the GOOGLE_CLOUD_UNIVERSE_DOMAIN environment variable to the desired universe domain. Parameters 0.0 SERVER_NAME Name of the server that holds the backup to be listed. SOURCE_URL URL of the cloud source, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options are: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. --format Output format (console or json). Default console. Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file): replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). --addressing-style The S3 addressing style to use when connecting to S3-compatible cloud storage. This option is useful when using custom S3 endpoints (such as MinIO) that may require a specific addressing style. Allowed options: 7.0 (bu 2 auto (default): Uses the addressing style determined by the boto3 library. (bu 2 virtual: Uses virtual-hosted-style addressing (bucket-name.s3.amazonaws.com). (bu 2 path: Uses path-style addressing (s3.amazonaws.com/bucket-name). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
barman-cloud-backup-show(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-backup-show [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ --endpoint-url ENDPOINT_URL ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ --addressing-style { auto | virtual | path } ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [ --format FORMAT ] SOURCE_URL SERVER_NAME BACKUP_ID Description This script displays detailed information about a specific backup created with the barman-cloud-backup command. The output is similar to the barman show-backup from the barman show-backup %<#:commands-barman-show-backup> command reference, but it has fewer information. Note: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. To use an alternative GCP universe (e.g. S3NS/T-Systems), set the GOOGLE_CLOUD_UNIVERSE_DOMAIN environment variable to the desired universe domain. Parameters 0.0 BACKUP_ID The ID of the backup. You can use a shortcut instead of the backup ID. SERVER_NAME Name of the server that holds the backup to be displayed. SOURCE_URL URL of the cloud source, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options are: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. --format Output format (console or json). Default console. Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file): replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). --addressing-style The S3 addressing style to use when connecting to S3-compatible cloud storage. This option is useful when using custom S3 endpoints (such as MinIO) that may require a specific addressing style. Allowed options: 7.0 (bu 2 auto (default): Uses the addressing style determined by the boto3 library. (bu 2 virtual: Uses virtual-hosted-style addressing (bucket-name.s3.amazonaws.com). (bu 2 path: Uses path-style addressing (s3.amazonaws.com/bucket-name). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
barman-cloud-check-wal-archive(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-check-wal-archive [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ --endpoint-url ENDPOINT_URL ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ --addressing-style { auto | virtual | path } ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [ --timeline TIMELINE ] DESTINATION_URL SERVER_NAME Description Verify that the WAL archive destination for a server is suitable for use with a new Postgres cluster. By default, the check will succeed if the WAL archive is empty or if the target bucket is not found. Any other conditions will result in a failure. Note: 0.0 3.5 The barman-cloud-check-wal-archive command performs an initial HeadBucket call to verify whether the target bucket already exists in the S3 storage. If the bucket does not exist, the command will attempt to automatically create it. This is the only Barman command that performs these operations (bucket existence check and automatic creation). Note: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. To use an alternative GCP universe (e.g. S3NS/T-Systems), set the GOOGLE_CLOUD_UNIVERSE_DOMAIN environment variable to the desired universe domain. Parameters 0.0 SERVER_NAME Name of the server that needs to be checked. DESTINATION_URL URL of the cloud destination, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options are: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. --timeline The earliest timeline whose WALs should cause the check to fail. Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file): replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). --addressing-style The S3 addressing style to use when connecting to S3-compatible cloud storage. This option is useful when using custom S3 endpoints (such as MinIO) that may require a specific addressing style. Allowed options: 7.0 (bu 2 auto (default): Uses the addressing style determined by the boto3 library. (bu 2 virtual: Uses virtual-hosted-style addressing (bucket-name.s3.amazonaws.com). (bu 2 path: Uses path-style addressing (s3.amazonaws.com/bucket-name). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
barman-cloud-restore(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-restore [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ --endpoint-url ENDPOINT_URL ] [ --addressing-style { auto | virtual | path } ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [ --snapshot-recovery-instance SNAPSHOT_RECOVERY_INSTANCE ] [ --snapshot-recovery-zone GCP_ZONE ] [ --aws-region AWS_REGION ] [ --gcp-zone GCP_ZONE ] [ --azure-resource-group AZURE_RESOURCE_GROUP ] [ --tablespace NAME:LOCATION [ --tablespace NAME:LOCATION ... ] ] [ --target-lsn LSN ] [ --target-time TIMESTAMP ] [ --target-tli TLI ] SOURCE_URL SERVER_NAME BACKUP_ID RECOVERY_DESTINATION Description Use this script to restore a backup directly from cloud storage that was created with the barman-cloud-backup command. Additionally, this script can prepare for recovery from a snapshot backup by verifying that attached disks were cloned from the correct snapshots and by downloading the backup label from object storage. This command does not automatically prepare Postgres for recovery. You must manually manage any PITR %<#:term-PITR> options, custom restore_command values, signal files, or required WAL files to ensure Postgres starts, either manually or using external tools. Note: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. To use an alternative GCP universe (e.g. S3NS/T-Systems), set the GOOGLE_CLOUD_UNIVERSE_DOMAIN environment variable to the desired universe domain. Parameters 0.0 SERVER_NAME Name of the server that holds the backup to be restored. SOURCE_URL URL of the cloud source, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. BACKUP_ID The ID of the backup to be restored. You can use a shortcut instead of the backup ID. Besides that, you can use auto to have Barman automatically find the most suitable backup for the restore operation. RECOVERY_DESTINATION The path to a directory for recovery. -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options are: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. --snapshot-recovery-instance Instance where the disks recovered from the snapshots are attached. --tablespace Tablespace relocation rule. --target-lsn The recovery target lsn, e.g., 3/64000000. --target-time The recovery target timestamp with or without timezone, in the format %Y-%m-%d %H:%M:%S. --target-tli The recovery target timeline. Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. --addressing-style The addressing style to use for S3 requests. This is useful when connecting to S3-compatible services that require a specific addressing style. Allowed options are: 7.0 (bu 2 auto (default): Uses the addressing style determined by the underlying library. (bu 2 virtual: Uses virtual-hosted style addressing (e.g., bucket-name.s3.amazonaws.com). (bu 2 path: Uses path-style addressing (e.g., s3.amazonaws.com/bucket-name). -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file): replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). --aws-region The name of the AWS region containing the EC2 VM and storage volumes defined by the --snapshot-instance and --snapshot-disk arguments. Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default. --azure-resource-group The name of the Azure resource group to which the compute instance and disks defined by the --snapshot-instance and --snapshot-disk arguments belong. Extra options for GCP cloud provider 0.0 --gcp-zone Zone of the disks from which snapshots should be taken. --snapshot-recovery-zone (deprecated) Zone containing the instance and disks for the snapshot recovery - replaced by --gcp-zone
barman-cloud-wal-archive(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-wal-archive [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ { { -z | --gzip } | { -j | --bzip2 } | --xz | --snappy | --zstd | --lz4 } ] [ --compression-level COMPRESSION_LEVEL ] [ --tag KEY,VALUE [ --tag KEY,VALUE ... ] ] [ --history-tag KEY,VALUE [ --history-tag KEY,VALUE ... ] ] [ --endpoint-url ENDPOINT_URL ] [ --addressing-style { auto | virtual | path } ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ { -e | --encryption } ENCRYPTION ] [ --sse-kms-key-id SSE_KMS_KEY_ID ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [ --encryption-scope ENCRYPTION_SCOPE ] [ --max-block-size MAX_BLOCK_SIZE ] [ --max-concurrency MAX_CONCURRENCY ] [ --max-single-put-size MAX_SINGLE_PUT_SIZE ] [ --kms-key-name KMS_KEY_NAME ] DESTINATION_URL SERVER_NAME [ WAL_PATH ] Description The barman-cloud-wal-archive command is designed to be used in the archive_command of a Postgres server to directly ship WAL files to cloud storage. Note: 0.0 3.5 If you are using Python 2 or unsupported versions of Python 3, avoid using the compression options --gzip or --bzip2. The script cannot restore gzip-compressed WALs on Python < 3.2 or bzip2-compressed WALs on Python < 3.3. This script enables the direct transfer of WAL files to cloud storage, bypassing the Barman server. Additionally, it can be utilized as a hook script for WAL archiving (pre_archive_retry_script). Note: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. To use an alternative GCP universe (e.g. S3NS/T-Systems), set the GOOGLE_CLOUD_UNIVERSE_DOMAIN environment variable to the desired universe domain. Parameters 0.0 SERVER_NAME Name of the server that will have the WALs archived. DESTINATION_URL URL of the cloud destination, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. WAL_PATH The value of the (aq%p(aq keyword (according to archive_command). -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options are: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. -z / --gzip gzip-compress the WAL while uploading to the cloud. -j / --bzip2 bzip2-compress the WAL while uploading to the cloud. --xz xz-compress the WAL while uploading to the cloud. --snappy snappy-compress the WAL while uploading to the cloud (requires the python-snappy Python library to be installed). --zstd zstd-compress the WAL while uploading to the cloud (requires the zstandard Python library to be installed). --lz4 lz4-compress the WAL while uploading to the cloud (requires the lz4 Python library to be installed). --compression-level A compression level to be used by the selected compression algorithm. Valid values are integers within the supported range of the chosen algorithm or one of the predefined labels: low, medium, and high. The range of each algorithm as well as what level each predefined label maps to can be found in compression_level %<#:configuration-options-compression-level>. --tag Tag to be added to archived WAL files in cloud storage. --tags Tag to be added to archived WAL files in cloud storage. Note: 0.0 3.5 If you are using --tags before positional arguments, you must insert -- after it to indicate the end of optional arguments. This tells the parser to treat everything after -- as positional arguments. Without the --, Barman may misinterpret positional arguments as values for the last option. Deprecated since version 3.15: --tags is deprecated. Use --tag instead. 0.0 --history-tag Tag to be added to archived history files in cloud storage. --history-tags Tags to be added to archived history files in cloud storage. Note: 0.0 3.5 If you are using --history-tags before positional arguments, you must insert -- after it to indicate the end of optional arguments. This tells the parser to treat everything after -- as positional arguments. Without the --, Barman may misinterpret positional arguments as values for the last option. Deprecated since version 3.15: --history-tags is deprecated. Use --history-tag instead. Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. --addressing-style The addressing style to use for S3 requests. This is useful when connecting to S3-compatible services that require a specific addressing style. Allowed options are: 7.0 (bu 2 auto (default): Uses the addressing style determined by the underlying library. (bu 2 virtual: Uses virtual-hosted style addressing (e.g., bucket-name.s3.amazonaws.com). (bu 2 path: Uses path-style addressing (e.g., s3.amazonaws.com/bucket-name). -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file): replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). -e / --encryption The encryption algorithm used when storing the uploaded data in S3. Allowed options: 7.0 (bu 2 AES256. (bu 2 aws:kms. --sse-kms-key-id The AWS KMS key ID that should be used for encrypting the uploaded data in S3. Can be specified using the key ID on its own or using the full ARN for the key. Only allowed if -e / --encryption is set to aws:kms. Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default. --encryption-scope The name of an encryption scope defined in the Azure Blob Storage service which is to be used to encrypt the data in Azure. --max-block-size The chunk size to be used when uploading an object via the concurrent chunk method (default: 4MB). --max-concurrency The maximum number of chunks to be uploaded concurrently (default: 1). --max-single-put-size Maximum size for which the Azure client will upload an object in a single request (default: 64MB). If this is set lower than the Postgres WAL segment size after any applied compression then the concurrent chunk upload method for WAL archiving will be used. Extra options for GCP cloud provider 0.0 --kms-key-name The name of the GCP KMS key which should be used for encrypting the uploaded data in GCS
barman-cloud-wal-restore(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-wal-restore [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ --endpoint-url ENDPOINT_URL ] [ --addressing-style { auto | virtual | path } ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [ --no-partial ] [ { -p, --parallel } PARALLEL ] [ --spool-dir SPOOL_DIR ] SOURCE_URL SERVER_NAME WAL_NAME WAL_DEST Description The barman-cloud-wal-restore script functions as the restore_command for retrieving WAL files from cloud storage and placing them directly into a Postgres standby server, bypassing the Barman server. This script is used to download WAL files that were previously archived with the barman-cloud-wal-archive command. Disable automatic download of .partial files by calling --no-partial option. Note: 0.0 3.5 Partial WAL files (with a .partial suffix) can appear in the object store when a standby server is archiving WAL segments and is then promoted to primary. At the moment of promotion, the in-progress WAL segment has not been completed yet, so Postgres archives it as a .partial file before switching to a new timeline. These files represent an incomplete segment and are not suitable for crash recovery on their own. In most cases, downloading .partial files during WAL restore is harmless, because Postgres knows how to handle them correctly. However, when running barman-cloud-wal-restore on a cluster that has experienced a promotion, the restore_command may retrieve a .partial (after renaming it without the suffix) file where a complete WAL is expected. Use --no-partial to suppress the download of .partial files in this scenario, which will cause restore_command to signal to Postgres that the WAL is not available, prompting it to switch to the correct timeline via a timeline history file (.history) instead. Important: 0.0 3.5 On the target Postgres node, when pg_wal and the spool directory are on the same filesystem, files are moved via renaming, which is faster than copying and deleting. This speeds up serving WAL files significantly. If the directories are on different filesystems, the process still involves copying and deleting, so there(aqs no performance gain in that case. Note: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. To use an alternative GCP universe (e.g. S3NS/T-Systems), set the GOOGLE_CLOUD_UNIVERSE_DOMAIN environment variable to the desired universe domain. Parameters 0.0 SERVER_NAME Name of the server that will have WALs restored. SOURCE_URL URL of the cloud source, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. WAL_NAME The value of the (aq%f(aq keyword (according to restore_command). WAL_DEST The value of the (aq%p(aq keyword (according to restore_command). -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options are: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. --no-partial Do not download partial WAL files -p / --parallel Specifies the number of WAL files to fetch in parallel. Default is 0 (disabled). When set to a value greater than 1, fetches the requested WAL file along with the next N - 1 files simultaneously. The additional files are staged in a local spool directory (see --spool-dir) so that subsequent restore requests can be served immediately from local storage. --spool-dir Directory used for staging extra WALs fetched when using --parallel. Default is /var/tmp/walrestore. Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. --addressing-style The addressing style to use for S3 requests. This is useful when connecting to S3-compatible services that require a specific addressing style. Allowed options are: 7.0 (bu 2 auto (default): Uses the addressing style determined by the underlying library. (bu 2 virtual: Uses virtual-hosted style addressing (e.g., bucket-name.s3.amazonaws.com). (bu 2 path: Uses path-style addressing (e.g., s3.amazonaws.com/bucket-name). -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file): replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
bindtest(1): test bind(2) behavior on IPv6 implementation
blas2_grp(3): Level 2 BLAS: matrix-vector ops
blas2_like_grp(3): Level 2 BLAS-like matrix-vector ops
cdparanoia(1), cdparanoia 10.2 (Paranoia release III)(1): an audio CD reading utility which includes extra data verification features
cdxa2mpeg(1): manual page for cdxa2mpeg 2.0.0
cfgmaker(1): Creates mrtg.cfg files (for mrtg-2.17.10)
checkproof(1): manual page for checkproof 2.6
chkfont(6): checks figlet 2.0 and up font files for format errors
chyves(8): bhyve(8) front end manager -- version 0.2.0
clisp(1): m[blue]ANSIm[]u[38]d+2 m[blue]Common Lispm[]u[1]d+2 compiler, interpreter and debugger
clisp-link(1): link a new external module to m[blue]CLISPm[]u[1]d+2
cmake-variables(7): CMake Variables Reference This page documents variables that are provided by CMake or have meaning to CMake when set by project code. For general information on variables, see the %Variables section in the cmake-language manual. NOTE: 0.0 3.5 CMake reserves identifiers that: 0.0 (bu 2 begin with CMAKE_ (upper-, lower-, or mixed-case), or (bu 2 begin with _CMAKE_ (upper-, lower-, or mixed-case), or (bu 2 begin with _ followed by the name of any %CMake Command
cob-config(1): manual page for cob-config 3.2.0
cobc(1): manual page for cobc 3.2.0
cobcrun(1): manual page for cobcrun 3.2.0
convert-ly(1): manual page for convert-ly 2.27.1
cron(8): manual page for cron 1.2.3
crontab(1): manual page for crontab 1.2.3
ct2db(1): manual page for ct2db 2.7.2
ct2util(1): manual page for CheeseCutter 2 utilities (Nov 12 2018)
cut-diff(1): show difference between 2 files with color
cxpm(1): Check an XPM (X PixMap) file, versions XPM 1, 2, or 3
dmenu2(1): dynamic menu 2
e_axfilter(1): manual page for e_axfilter 2.6 Floral Guranse
e_deduction_server(1): manual page for e_deduction_server 2.6 Floral Guranse
e_ltb_runner(1): manual page for e_ltb_runner 2.6 Floral Guranse
e_stratpar(1): manual page for e_stratpar 2.6 Floral Guranse
eground(1): manual page for eground 2.6
ekb_create(1): manual page for ekb_create 2.6
ekb_delete(1): manual page for ekb_delete 2.6
ekb_ginsert(1): manual page for ekb_ginsert 2.6
ekb_insert(1): manual page for ekb_insert 2.6
enblend(1): manual page for enblend 4.2
encapsulate(1): multiplex several channels over a single socket with sampling of remote process exit status, and provide conversation termination without closing the socket. netpipes 4.2
enchant-2(1), Enchant(1): a spellchecker
enchant-lsmod-2(1), enchant-lsmod(1): list provider and dictionary information
enfuse(1): manual page for enfuse 4.2
epclextract(1): manual page for epclextract 2.6
eprover(1), E(1): manual page for E 2.6 Floral Guranse (8e8bfa2a3f682a4a7d96975eaa7b1133c4267b13)
etf2ly(1): manual page for etf2ly (LilyPond) 2.27.1
exparna_p(1): manual page for exparna_p (LocARNA 2.0.0)
explain_accept(3): explain accept(2) errors require_index { }
explain_accept4(3): explain accept4(2) errors require_index { }
explain_access(3): explain access(2) errors require_index { }
explain_acct(3): explain acct(2) errors require_index { }
explain_adjtime(3): explain adjtime(2) errors require_index { }
explain_adjtimex(3): explain adjtimex(2) errors require_index { }
explain_bind(3): explain bind(2) errors require_index { }
explain_chdir(3): explain chdir(2) errors require_index { }
explain_chmod(3): explain chmod(2) errors require_index { }
explain_chown(3): explain chown(2) errors require_index { }
explain_chroot(3): explain chroot(2) errors require_index { }
explain_close(3): explain close(2) errors require_index { }
explain_connect(3): explain connect(2) errors require_index { }
explain_creat(3): explain creat(2) errors require_index { }
explain_dup(3): explain dup(2) errors require_index { }
explain_dup2(3): explain dup2(2) errors require_index { }
explain_eventfd(3): explain eventfd(2) errors require_index { }
explain_execve(3): explain execve(2) errors require_index { }
explain_fchdir(3): explain fchdir(2) errors require_index { }
explain_fchmod(3): explain fchmod(2) errors require_index { }
explain_fchown(3): explain fchown(2) errors require_index { }
explain_fchownat(3): explain fchownat(2) errors require_index { }
explain_fcntl(3): explain fcntl(2) errors require_index { }
explain_flock(3): explain flock(2) errors require_index { }
explain_fork(3): explain fork(2) errors require_index { }
explain_fstat(3): explain fstat(2) errors require_index { }
explain_fstatat(3): explain fstatat(2) errors require_index { }
explain_fstatfs(3): explain fstatfs(2) errors require_index { }
explain_fstatvfs(3): explain fstatvfs(2) errors require_index { }
explain_fsync(3): explain fsync(2) errors require_index { }
explain_ftruncate(3): explain ftruncate(2) errors require_index { }
explain_futimesat(3): explain futimesat(2) errors require_index { }
explain_getcwd(3): explain getcwd(2) errors require_index { }
explain_getdomainname(3): explain getdomainname(2) errors require_index { }
explain_getgroups(3): explain getgroups(2) errors require_index { }
explain_gethostname(3): explain gethostname(2) errors require_index { }
explain_getpeername(3): explain getpeername(2) errors require_index { }
explain_getpgid(3): explain getpgid(2) errors require_index { }
explain_getpgrp(3): explain getpgrp(2) errors require_index { }
explain_getpriority(3): explain getpriority(2) errors require_index { }
explain_getresgid(3): explain getresgid(2) errors require_index { }
explain_getresuid(3): explain getresuid(2) errors require_index { }
explain_getrlimit(3): explain getrlimit(2) errors require_index { }
explain_getrusage(3): explain getrusage(2) errors require_index { }
explain_getsockname(3): explain getsockname(2) errors require_index { }
explain_getsockopt(3): explain getsockopt(2) errors require_index { }
explain_gettimeofday(3): explain gettimeofday(2) errors require_index { }
explain_ioctl(3): explain ioctl(2) errors require_index { }
explain_kill(3): explain kill(2) errors require_index { }
explain_lchmod(3): explain lchmod(2) errors require_index { }
explain_lchown(3): explain lchown(2) errors require_index { }
explain_lchownat(3): explain lchownat(2) errors require_index { }
explain_lchownat_or_die(3): Execute lchownat(2) and report errors require_index { "Execute lchownat(2) and report errors" }
explain_link(3): explain link(2) errors require_index { }
explain_listen(3): explain listen(2) errors require_index { }
explain_lseek(3): explain lseek(2) errors require_index { }
explain_mkdir(3): explain mkdir(2) errors require_index { }
explain_mknod(3): explain mknod(2) errors require_index { }
explain_mmap(3): explain mmap(2) errors require_index { }
explain_mount(3): explain mount(2) errors require_index { }
explain_munmap(3): explain munmap(2) errors require_index { }
explain_nanosleep(3): explain nanosleep(2) errors require_index { }
explain_nice(3): explain nice(2) errors require_index { }
explain_open(3): explain open(2) errors require_index { }
explain_openat(3): explain openat(2) errors require_index { }
explain_pipe(3): explain pipe(2) errors require_index { }
explain_pipe2(3): explain pipe2(2) errors require_index { }
explain_poll(3): explain poll(2) errors require_index { }
explain_pread(3): explain pread(2) errors require_index { }
explain_ptrace(3): explain ptrace(2) errors require_index { }
explain_pwrite(3): explain pwrite(2) errors require_index { }
explain_read(3): explain read(2) errors require_index { }
explain_readdir(3): explain readdir(2) errors require_index { }
explain_readlink(3): explain readlink(2) errors require_index { }
explain_readv(3): explain readv(2) errors require_index { }
explain_remove(3): explain remove(2) errors require_index { }
explain_rename(3): explain rename(2) errors require_index { }
explain_rmdir(3): explain rmdir(2) errors require_index { }
explain_select(3): explain select(2) errors require_index { }
explain_setdomainname(3): explain setdomainname(2) errors require_index { }
explain_setgid(3): explain setgid(2) errors require_index { }
explain_setgroups(3): explain setgroups(2) errors require_index { }
explain_sethostname(3): explain sethostname(2) errors require_index { }
explain_setpgid(3): explain setpgid(2) errors require_index { }
explain_setpgrp(3): explain setpgrp(2) errors require_index { }
explain_setpriority(3): explain setpriority(2) errors require_index { }
explain_setregid(3): explain setregid(2) errors require_index { }
explain_setresgid(3): explain setresgid(2) errors require_index { }
explain_setresuid(3): explain setresuid(2) errors require_index { }
explain_setreuid(3): explain setreuid(2) errors require_index { }
explain_setsid(3): explain setsid(2) errors require_index { }
explain_setsockopt(3): explain setsockopt(2) errors require_index { }
explain_settimeofday(3): explain settimeofday(2) errors require_index { }
explain_setuid(3): explain setuid(2) errors require_index { }
explain_shmat(3): explain shmat(2) errors require_index { }
explain_shmctl(3): explain shmctl(2) errors require_index { }
explain_signalfd(3): explain signalfd(2) errors require_index { }
explain_socket(3): explain socket(2) errors require_index { }
explain_socketpair(3): explain socketpair(2) errors require_index { }
explain_stat(3): explain stat(2) errors require_index { }
explain_statfs(3): explain statfs(2) errors require_index { }
explain_statvfs(3): explain statvfs(2) errors require_index { }
explain_stime(3): explain stime(2) errors require_index { }
explain_symlink(3): explain symlink(2) errors require_index { }
explain_time(3): explain time(2) errors require_index { }
explain_timerfd_create(3): explain timerfd_create(2) errors require_index { }
explain_truncate(3): explain truncate(2) errors require_index { }
explain_uname(3): explain uname(2) errors require_index { }
explain_unlink(3): explain unlink(2) errors require_index { }
explain_ustat(3): explain ustat(2) errors require_index { }
explain_utime(3): explain utime(2) errors require_index { }
explain_utimens(3): explain utimens(2) errors require_index { }
explain_utimensat(3): explain utimensat(2) errors require_index { }
explain_utimes(3): explain utimes(2) errors require_index { }
explain_vfork(3): explain vfork(2) errors require_index { }
explain_wait(3): explain wait(2) errors require_index { }
explain_wait3(3): explain wait3(2) errors require_index { }
explain_wait4(3): explain wait4(2) errors require_index { }
explain_waitpid(3): explain waitpid(2) errors require_index { }
explain_write(3): explain write(2) errors require_index { }
explain_writev(3): explain writev(2) errors require_index { }
extract_qupak(1): extract Quake/2 PACK files
faac(1): open source MPEG-4 and MPEG-2 AAC encoder
faucet(1): a fixture for a BSD network pipe netpipes 4.2
fd2(1): redirect from/to file descriptor 2
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
fvwm-convert-2.6(1): convert fvwm 2.4.x configuration file to fvwm 2.6 style
galculator(1): a GTK 2 / GTK 3 based scientific calculator

gbequb(3): gbequb: equilibration, power of 2
gbtf2(3): gbtf2: triangular factor, level 2
gconftool-2(1): GNOME configuration tool
gdal-vector-layer-algebra(1): Perform algebraic operation between 2 layers Added in version 3.12
gebd2(3): gebd2: reduction to bidiagonal, level 2
geequb(3): geequb: equilibration, power of 2
gehd2(3): gehd2: reduction to Hessenberg, level 2
gelq2(3): gelq2: LQ factor, level 2
gengetopt(1): manual page for gengetopt 2.23
geql2(3): geql2: QL factor, level 2
geqr2(3): geqr2: QR factor, level 2
geqr2p(3): geqr2p: QR factor, diag( R ) ≥ 0, level 2
geqrt2(3): geqrt2: QR factor, with T, level 2
gerq2(3): gerq2: RQ factor, level 2
getaudit(2), getaudit_addr(2): retrieve audit session state
getauid(2): retrieve audit session ID
getf2(3): getf2: triangular factor panel, level 2
getpeername(1): get information about this or that end of the socket's connection netpipes 4.2
gimptool-2.0(1): script to perform various GIMPy functions
gitprotocol-v2(5): Git Wire Protocol, Version 2
gittutorial-2(7): A tutorial introduction to Git: part two
glmark2(1): OpenGL (ES) 2.0 benchmark suite
glmark2-drm(1): OpenGL (ES) 2.0 benchmark suite
glmark2-egl(1): OpenGL (ES) 2.0 benchmark suite
glmark2-es2(1): OpenGL (ES) 2.0 benchmark suite
glmark2-es2-drm(1): OpenGL (ES) 2.0 benchmark suite
glmark2-es2-gbm(1): OpenGL (ES) 2.0 benchmark suite
glmark2-es2-wayland(1): OpenGL (ES) 2.0 benchmark suite
glmark2-gbm(1): OpenGL (ES) 2.0 benchmark suite
glmark2-wayland(1): OpenGL (ES) 2.0 benchmark suite
gluBuild2DMipmaps(3), "gluBuild2DMipmaps(3): builds a 2-D mipmap
gmx-rmsdist(1): Calculate atom pair distances averaged with power -2, -3 or -6
gpodder-migrate2tres(1): gpodder 2.x to 3.x profile migrator
gtk-chtheme(1): Gtk+ 2.0 theme preview and selection made slick
h2load(1): HTTP/2 benchmarking tool
h2o(8), H2O(8): the optimized HTTP/1.x, HTTP/2 server
h2o.conf(5): The configuration file for H2O, the optimized HTTP/1.x, HTTP/2 server
heequb(3): {he,sy}equb: equilibration, power of 2
heev_driver2(3): --- full, 2-stage
hegs2(3): {he,sy}gs2: reduction to standard form, level 2
hegv_2stage(3): {he,sy}gv_2stage: eig, QR iteration, 2-stage
her2(3): {he,sy}r2: Hermitian/symmetric rank-2 update
hesv_aa_2stage(3): {he,sy}sv_aa_2stage: Aasen, blocked 2-stage
hesv_comp_aasen2(3): --- full, Aasen, blocked 2-stage
heswapr(3): {he,sy}swapr: apply 2-sided permutation
hetd2(3): {he,sy}td2: reduction to tridiagonal, level 2
hetf2(3): {he,sy}tf2: triangular factor, level 2
hetf2_rk(3): {he,sy}tf2_rk: triangular factor, level 2
hetf2_rook(3): {he,sy}tf2_rook: triangular factor, level 2
hetrd_2stage(3): {he,sy}trd_2stage: reduction to tridiagonal, 2-stage
hose(1): the client end of a BSD network pipe netpipes 4.2
hpr2(3): {hp,sp}r2: Hermitian/symmetric rank-2 update
icinga2(8): The Icinga 2 network monitoring daemon
idn2.conf(5), .idn2rc(5): configuration files for idnkit version 2
iked(8): Internet Key Exchange version 2 (IKEv2) daemon
ilaenv2stage(3): ilaenv2stage: tuning parameters for 2-stage eig
indexmaker(1): Creates index files for mrtg web sites (mrtg-2.17.10)
iparam2stage(3): iparam2stage: sets parameters for 2-stage eig
kdrill(1), kdrill v6.2(1): drill program for kanji chars under Xwindows (X11R5 or better is required to run) kdrill also does dictionary lookup Yikes.. this man-page is getting huge. But I am a great believer in having proper documentation. Hopefully, this new format will help instead of hinder. At some future point in time, I shall convert this huge beast to HTML. But that point is not now. [Although actually, you CAN go to http://www.bolthole.com/kdrill/ for some help ] TIP: "/WORD" usually takes you to the next occurrence of "WORD", if you are viewing this using a "man"-like program
l2tpd(8): Layer 2 Tunnelling Protocol Daemon
lamrg(3): lamrg: permutation to merge 2 sorted lists
lapll(3): lapll: linear dependence of 2 vectors
lapy2(3): lapy2: robust sqrt( x^2 + y^2 )
lapy3(3): lapy3: robust sqrt( x^2 + y^2 + z^2 )
larfy(3): larfy: apply Householder reflector symmetrically (2-sided)
launhr_col_getrfnp2(3): la{un,or}hr_col_getrfnp2: LU factor without pivoting, level 2
lauu2(3): lauu2: triangular multiply: U^H U, level 2
ledit(1): line editor, version 2.06

home | help