command
stringlengths 1
42
| description
stringlengths 29
182k
â | name
stringlengths 7
64.9k
â | synopsis
stringlengths 4
85.3k
â | options
stringclasses 593
values | examples
stringclasses 455
values |
|---|---|---|---|---|---|
unwrap-diff
| null | null | null | null | null |
gen-rc
| null | null | null | null | null |
adig
|
Send queries to DNS servers about NAME and print received information, where NAME is a valid DNS name (e.g. www.example.com, 1.2.3.10.in- addr.arpa). This utility comes with the c-ares asynchronous resolver library.
|
adig - print information collected from Domain Name System (DNS) servers
|
adig [OPTION]... NAME...
|
-c class Set the query class. Possible values for class are ANY, CHAOS, HS and IN (default). -d Print some extra debugging output. -f flag Add a behavior control flag. Possible values for flag are igntc - ignore query truncation, return answer as-is instead of retrying via tcp. noaliases - don't honor the HOSTALIASES environment variable, norecurse - don't query upstream servers recursively, primary - use the first server, stayopen - don't close the communication sockets, and usevc - always use TCP. -h, -? Display this help and exit. -s server Connect to specified DNS server, instead of the system's default one(s). Servers are tried in round-robin, if the previous one failed. -t type Query records of specified type. Possible values for type are A (default), AAAA, ANY, AXFR, CNAME, HINFO, MX, NAPTR, NS, PTR, SOA, SRV, TXT, URI, CAA, SVCB, and HTTPS. -T port Connect to the specified TCP port of DNS server. -U port Connect to the specified UDP port of DNS server. REPORTING BUGS Report bugs to the c-ares mailing list: https://lists.haxx.se/listinfo/c-ares SEE ALSO ahost(1). c-ares utilities April 2011 ADIG(1)
| null |
pydoc3.10
| null | null | null | null | null |
dh_server
| null | null | null | null | null |
speexdec
|
Decodes a Speex file and produce a WAV file or raw file input_file can be: filename.spx regular Speex file - stdin output_file can be: filename.wav Wav file filename.* Raw PCM file (any extension other that .wav) - stdout (nothing) Will be played to soundcard
|
speexdec - The reference implementation speex decoder.
|
speexdec [options] input_file.spx [output_file]
|
--enh Enable perceptual enhancement (default) --no-enh Disable perceptual enhancement --force-nb Force decoding in narrowband --force-wb Force decoding in wideband --force-uwb Force decoding in ultra-wideband --mono Force decoding in mono --stereo Force decoding in stereo --rate n Force decoding at sampling rate n Hz --packet-loss n Simulate n % random packet loss -V Verbose mode (show bit-rate) -h, --help This help -v, --version Version information --pf Deprecated, use --enh instead --no-pf Deprecated, use --no-enh instead More information is available from the Speex site: http://www.speex.org Please report bugs to the mailing list `speex-dev@xiph.org'. COPYRIGHT Copyright © 2002 Jean-Marc Valin speexdec version 1.1 September 2003 SPEEXDEC(1)
| null |
pkcs1-conv
| null | null | null | null | null |
aarch64-apple-darwin23-gcc-ar-13
| null | null | null | null | null |
gexpand
|
Convert tabs in each FILE to spaces, writing to standard output. With no FILE, or when FILE is -, read standard input. Mandatory arguments to long options are mandatory for short options too. -i, --initial do not convert tabs after non blanks -t, --tabs=N have tabs N characters apart, not 8 -t, --tabs=LIST use comma separated list of tab positions. The last specified position can be prefixed with '/' to specify a tab size to use after the last explicitly specified tab stop. Also a prefix of '+' can be used to align remaining tab stops relative to the last specified tab stop instead of the first column --help display this help and exit --version output version information and exit AUTHOR Written by David MacKenzie. REPORTING BUGS GNU coreutils online help: <https://www.gnu.org/software/coreutils/> Report any translation bugs to <https://translationproject.org/team/> COPYRIGHT Copyright © 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO unexpand(1) Full documentation <https://www.gnu.org/software/coreutils/expand> or available locally via: info '(coreutils) expand invocation' GNU coreutils 9.3 April 2023 EXPAND(1)
|
expand - convert tabs to spaces
|
expand [OPTION]... [FILE]...
| null | null |
gruncon
|
Run COMMAND with completely-specified CONTEXT, or with current or transitioned security context modified by one or more of LEVEL, ROLE, TYPE, and USER. If none of -c, -t, -u, -r, or -l, is specified, the first argument is used as the complete context. Any additional arguments after COMMAND are interpreted as arguments to the command. Note that only carefully-chosen contexts are likely to successfully run. Run a program in a different SELinux security context. With neither CONTEXT nor COMMAND, print the current security context. Mandatory arguments to long options are mandatory for short options too. CONTEXT Complete security context -c, --compute compute process transition context before modifying -t, --type=TYPE type (for same role as parent) -u, --user=USER user identity -r, --role=ROLE role -l, --range=RANGE levelrange --help display this help and exit --version output version information and exit Exit status: 125 if the runcon command itself fails 126 if COMMAND is found but cannot be invoked 127 if COMMAND cannot be found - the exit status of COMMAND otherwise AUTHOR Written by Russell Coker. REPORTING BUGS GNU coreutils online help: <https://www.gnu.org/software/coreutils/> Report any translation bugs to <https://translationproject.org/team/> COPYRIGHT Copyright © 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO Full documentation <https://www.gnu.org/software/coreutils/runcon> or available locally via: info '(coreutils) runcon invocation' GNU coreutils 9.3 April 2023 RUNCON(1)
|
runcon - run command with specified security context
|
runcon CONTEXT COMMAND [args] runcon [ -c ] [-u USER] [-r ROLE] [-t TYPE] [-l RANGE] COMMAND [args]
| null | null |
gpathchk
|
Diagnose invalid or unportable file names. -p check for most POSIX systems -P check for empty names and leading "-" --portability check for all POSIX systems (equivalent to -p -P) --help display this help and exit --version output version information and exit AUTHOR Written by Paul Eggert, David MacKenzie, and Jim Meyering. REPORTING BUGS GNU coreutils online help: <https://www.gnu.org/software/coreutils/> Report any translation bugs to <https://translationproject.org/team/> COPYRIGHT Copyright © 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO Full documentation <https://www.gnu.org/software/coreutils/pathchk> or available locally via: info '(coreutils) pathchk invocation' GNU coreutils 9.3 April 2023 PATHCHK(1)
|
pathchk - check whether file names are valid or portable
|
pathchk [OPTION]... NAME...
| null | null |
img2webp
|
This manual page documents the img2webp command. img2webp compresses a sequence of images using the animated WebP format. Input images can either be PNG, JPEG, TIFF or WebP. If a single file name (not starting with the character '-') is supplied as the argument, the command line arguments are actually tokenized from this file. This allows for easy scripting or using a large number of arguments. FILE-LEVEL OPTIONS The file-level options are applied at the beginning of the compression process, before the input frames are read. -o string Specify the name of the output WebP file. -min_size Encode images to achieve smallest size. This disables key frame insertion and picks the parameters resulting in the smallest output for each frame. It uses lossless compression by default, but can be combined with -q, -m, -lossy or -mixed options. -kmin int -kmax int Specify the minimum and maximum distance between consecutive key frames (independently decodable frames) in the output animation. The tool will insert some key frames into the output animation as needed so that this criteria is satisfied. -mixed Mixed compression mode: optimize compression of the image by picking either lossy or lossless compression for each frame heuristically. This global option disables the local option -lossy and -lossless . -near_lossless int Specify the level of near-lossless image preprocessing. This option adjusts pixel values to help compressibility, but has minimal impact on the visual quality. It triggers lossless compression mode automatically. The range is 0 (maximum preprocessing) to 100 (no preprocessing, the default). The typical value is around 60. Note that lossy with -q 100 can at times yield better results. -sharp_yuv Use more accurate and sharper RGB->YUV conversion if needed. Note that this process is slower than the default 'fast' RGB->YUV conversion. -loop int Specifies the number of times the animation should loop. Using '0' means 'loop indefinitely'. -v Be more verbose. -h, -help A short usage summary. -version Print the version numbers of the relevant libraries used. PER-FRAME OPTIONS The per-frame options are applied for the images following as arguments in the command line. They can be modified any number of times preceding each particular input image. -d int Specify the image duration in milliseconds. -lossless, -lossy Compress the next image(s) using lossless or lossy compression mode. The default mode is lossless. -q float Specify the compression factor between 0 and 100. The default is 75. -m int Specify the compression method to use. This parameter controls the trade off between encoding speed and the compressed file size and quality. Possible values range from 0 to 6. Default value is 4. EXAMPLE img2webp -loop 2 in0.png -lossy in1.jpg -d 80 in2.tiff -o out.webp BUGS Please report all bugs to the issue tracker: https://bugs.chromium.org/p/webp Patches welcome! See this page to get started: https://www.webmproject.org/code/contribute/submitting-patches/ AUTHORS img2webp is a part of libwebp and was written by the WebP team. The latest source tree is available at https://chromium.googlesource.com/webm/libwebp This manual page was written by Pascal Massimino <pascal.massimino@gmail.com>, for the Debian project (and may be used by others). SEE ALSO webpmux(1), gif2webp(1) Please refer to https://developers.google.com/speed/webp/ for additional information. March 17, 2023 IMG2WEBP(1)
|
img2webp - create animated WebP file from a sequence of input images.
|
img2webp [file_options] [[frame_options] frame_file]... [-o webp_file] img2webp argument_file_name
| null | null |
giftext
|
A program to dump (text only) general information about GIF file. If no GIF file is given, giftext will try to read a GIF file from stdin.
|
giftext - dump GIF pixels and metadata as text
|
giftext [-v] [-c] [-e] [-z] [-p] [-r] [-h] [gif-file]
|
-v Verbose mode (show progress). Enables printout of running scan lines. -c Dumps the color maps. -e Dumps encoded bytes - the pixels after compressed using LZ algorithm and chained to form bytes. This is the form the data is saved in the GIF file. Dumps in hex - 2 digit per byte. -z Dumps the LZ codes of the image. Dumps in hex - 3 digits per code (as we are limited to 12 bits). -p Dumps the pixels of the image. Dumps in hex - 2 digit per pixel (<=byte). -r Dumps raw pixels as one byte per pixel. This option inhibits all other options and only the pixels are dumped. This option may be used to convert GIF files into raw data. Note: the color map can be extracted by gifclrmp utility. If more than one image is included in the file, all images will be dumped in order. -h Print one line of command line help, similar to Usage above. AUTHOR Gershon Elber. GIFLIB 2 May 2012 GIFTEXT(1)
| null |
hwloc-ls
|
lstopo and lstopo-no-graphics are capable of displaying a topological map of the system in a variety of different output formats. The only difference between lstopo and lstopo-no-graphics is that graphical outputs are only supported by lstopo, to reduce dependencies on external libraries. hwloc-ls is identical to lstopo-no-graphics. The filename specified directly implies the output format that will be used; see the OUTPUT FORMATS section, below. Output formats that support color will indicate specific characteristics about individual CPUs by their color; see the COLORS section, below. OUTPUT FORMATS By default, if no output filename is specified, the output is sent to a graphical window if possible in the current environment (DISPLAY environment variable set on Unix, etc.). Otherwise, a text summary is displayed in the console. The console is also used when the program runs from a terminal and the output is redirected to a pipe or file. These default behaviors may be changed by passing --of console to force console mode or --of window for graphical window. The filename on the command line usually determines the format of the output. There are a few filenames that indicate specific output formats and devices (e.g., a filename of "-" will output a text summary to stdout), but most filenames indicate the desired output format by their suffix (e.g., "topo.png" will output a PNG-format file). The format of the output may also be changed with "--of". For instance, "--of pdf" will generate a PDF-format file on the standard output, while "--of fig toto" will output a Xfig-format file named "toto". The list of currently supported formats is given below. Any of them may be used with "--of" or as a filename suffix. default Send the output to a window or to the console depending on the environment. window Send the output to a graphical window. console Send a text summary to stdout. Binding or unallowed processors are only annotated in this mode if verbose; see the COLORS section, below. ascii Output an ASCII art representation of the map (formerly called txt). If outputting to stdout and if colors are supported on the terminal, the output will be colorized. tikz or tex Output a LaTeX tikzpicture representation of the map that can be compiled with a LaTeX compiler. fig Output a representation of the map that can be loaded in Xfig. svg Output a SVG representation of the map, using Cairo (by default, if supported) or a native SVG backend (fallback, always supported). See cairosvg and nativesvg below. cairosvg or svg(cairo) If lstopo was compiled with the proper support, output a SVG representation of the map using Cairo. nativesvg or svg(native) Output a SVG representation of the map using the native SVG backend. It may be less pretty than the Cairo output, but it is always supported, and SVG objects have attributes for identifying and manipulating them. See dynamic_SVG_example.html for an example. pdf If lstopo was compiled with the proper support, lstopo outputs a PDF representation of the map. ps If lstopo was compiled with the proper support, lstopo outputs a Postscript representation of the map. png If lstopo was compiled with the proper support, lstopo outputs a PNG representation of the map. synthetic If the topology is symmetric (which requires that the root object has its symmetric_subtree field set), lstopo outputs a synthetic description string. This output may be reused as an input synthetic topology description later. See also the Synthetic topologies section in the documentation. Note that Misc and I/O devices are ignored during this export. xml lstopo outputs an XML representation of the map. It may be reused later, even on another machine, with lstopo --input, the HWLOC_XMLFILE environment variable, or the hwloc_topology_set_xml() function. The following special names may be used: - Send a text summary to stdout. /dev/stdout Send a text summary to stdout. It is effectively the same as specifying "-". -.<format> If the entire filename is "-.<format>", lstopo behaves as if "--of <format> -" was given, which means a file of the given format is sent to the standard output. See the output of "lstopo --help" for a specific list of what graphical output formats are supported in your hwloc installation. GRAPHICAL OUTPUT The graphical output is made of nested boxes representing the inclusion of objects in the hierarchy of resources. Usually a Machine box contains one or several Package boxes, that contain multiple Core boxes, with one or several PUs each. Caches Caches are displayed in a slightly different manner because they do not actually include computing resources such as cores. For instance, a L2 Cache shared by a pair of Cores is drawn as a Cache box on top of two Core boxes (instead of having Core boxes inside the Cache box). NUMA nodes and Memory-side Caches By default, NUMA nodes boxes are drawn on top of their local computing resources. For instance, a processor Package containing one NUMA node and four Cores is displayed as a Package box containing the NUMA node box above four Core boxes. If a NUMA node is local to the L3 Cache, the NUMA node is displayed above that Cache box. All this specific drawing strategy for memory objects may be disabled by passing command- line option --children-order plain. If multiple NUMA nodes are attached to the same parent object, they are displayed inside an additional unnamed memory box. If some Memory-side Caches exist in front of some NUMA nodes, they are drawn as boxes immediately above them. PCI bridges, PCI devices and OS devices The PCI hierarchy is not drawn as a set of included boxes but rather as a tree of bridges (that may actually be switches) with links between them. The tree starts with a small square on the left for the hostbridge or root complex. It ends with PCI device boxes on the right. Intermediate PCI bridges/switches may appear as additional small squares in the middle. PCI devices on the right of the tree are boxes containing their PCI bus ID (such as 00:02.3). They may also contain sub-boxes for OS device objects such as a network interface eth0 or a CUDA GPU cuda0. When there is a single link (horizontal line) on the right of a PCI bridge, it means that a single device or bridge is connected on the secondary PCI bus behind that bridge. When there is a vertical line, it means that multiple devices and/or bridges are connected to the same secondary PCI bus. The datarate of a PCI link may be written (in GB/s) right below its drawn line (if the operating system and/or libraries are able to report that information). This datarate is the currently configured speed of the entire PCI link (sum of the bandwidth of all PCI lanes in that link). It may change during execution since some devices are able to slow their PCI links down when idle. LAYOUT In its graphical output, lstopo uses simple rectangular heuristics to try to achieve a 4/3 ratio between width and height. Although the hierarchy of resources is properly reflected, the exact physical organization (NUMA distances, rings, complete graphs, etc.) is currently ignored. The layout of a level may be changed with --vert, --horiz, and --rect to force a parent object to arrange its children in vertical, horizontal or rectangular manners respectively. The position of Memory, I/O and Misc children with respect to other children objects may be changed using --children-order. This effectivement divides children into multiple sections. The layout of children is first computed inside each section, before sections are placed inside (or below) the parent box. The vertical/horizontal/rectangular layout of these additional sections may also be configured through --children-order. COLORS Individual CPUs and NUMA nodes are colored in the graphical output formats to indicate different characteristics: Green The topology is reported as seen by a specific process (see --pid), and the given CPU or NUMA node is in this process CPU or Memory binding mask. White The CPU or NUMA node is in the allowed set (see below). If the topology is reported as seen by a specific process (see --pid), the object is also not in this process binding mask. Red The CPU or NUMA node is not in the allowed set (see below). The "allowed set" is the set of CPUs or NUMA nodes to which the current process is allowed to bind. The allowed set is usually either inherited from the parent process or set by administrative qpolicies on the system. Linux cpusets are one example of limiting the allowed set for a process and its children to be less than the full set of CPUs or NUMA nodes on the system. Different processes may therefore have different CPUs or NUMA nodes in the allowed set. Hence, invoking lstopo in different contexts and/or as different users may display different colors for the same individual CPUs (e.g., running lstopo in one context may show a specific CPU as red, but running lstopo in a different context may show the same CPU as white). Some lstopo output modes, e.g. the console mode (default non-graphical output), do not support colors at all. The console mode displays the above characteristics by appending text to each PU line if verbose messages are enabled. CUSTOM COLORS The colors of different kinds of boxes may be configured with --palette. The color of each object in the graphical output may also be enforced by specifying a "lstopoStyle" info attribute in that object. Its value should be a semi-colon separated list of "<attribute>=#rrggbb" where rr, gg and bb are the RGB components of a color, each between 0 and 255, in hexadecimal (00 to ff). <attribute> may be Background Sets the background color of the main object box. Text Sets the color of the text showing the object name, type, index, etc. Text2 Sets the color of the additional text near the object, for instance the link speed behind a PCI bridge. The "lstopoStyle" info may be added to a temporarily-saved XML topologies with hwloc-annotate, or with hwloc_obj_add_info(). For instance, to display all core objects in blue (with white names): lstopo save.xml hwloc-annotate save.xml save.xml core:all info lstopoStyle "Background=#0000ff;Text=#ffffff" lstopo -i save.xml
|
lstopo, lstopo-no-graphics, hwloc-ls - Show the topology of the system
|
lstopo [ options ]... [ filename ] lstopo-no-graphics [ options ]... [ filename ] hwloc-ls [ options ]... [ filename ] Note that hwloc(7) provides a detailed explanation of the hwloc system; it should be read before reading this man page
|
--of <format>, --output-format <format> Enforce the output in the given format. See the OUTPUT FORMATS section below. -i <path>, --input <path> Read the topology from <path> instead of discovering the topology of the local machine. If <path> is a file, it may be a XML file exported by a previous hwloc program. If <path> is "-", the standard input may be used as a XML file. On Linux, <path> may be a directory containing the topology files gathered from another machine topology with hwloc-gather- topology. On x86, <path> may be a directory containing a cpuid dump gathered with hwloc-gather-cpuid. When the archivemount program is available, <path> may also be a tarball containing such Linux or x86 topology files. -i <specification>, --input <specification> Simulate a fake hierarchy (instead of discovering the topology on the local machine). If <specification> is "node:2 pu:3", the topology will contain two NUMA nodes with 3 processing units in each of them. The <specification> string must end with a number of PUs. --if <format>, --input-format <format> Enforce the input in the given format, among xml, fsroot, cpuid and synthetic. --export-xml-flags <flags> Enforce flags when exporting to the XML format. Flags may be given as numeric values or as a comma-separated list of flag names that are passed to hwloc_topology_export_xml(). Those names may be substrings of actual flag names as long as a single one matches. A value of 1 (or v1) reverts to the format of hwloc v1.x. The default is 0 (or none). --export-synthetic-flags <flags> Enforce flags when exporting to the synthetic format. Flags may be given as numeric values or as a comma-separated list of flag names that are passed to hwloc_topology_export_synthetic(). Those names may be substrings of actual flag names as long as a single one matches. A value of 2 (or no_attr) reverts to the format of hwloc v1.9. A value of 3 (or no_ext,no_attr) reverts to the original minimalistic format (before v1.9). The default is 0 (or none). -v --verbose Include additional detail. The hwloc-info tool may be used to display even more information about specific objects. -q --quiet -s --silent Reduce the amount of details to show. --distances Only display distance matrices. --distances-transform <links|merge-switch-ports|transitive-closure> Try applying a transformation to distances structures before displaying them. See hwloc_distances_transform() for details. More transformations may be applied using hwloc-annotate(1) (and it may save their output to XML). --memattrs Only display memory attributes. All of them are displayed (while the default textual output selects memory attribute details depending on the verbosity level). --cpukinds Only display CPU kinds. CPU kinds are displayed in order, starting from the most energy efficient ones up to the rather higher performance and power hungry ones. --windows-processor-groups On Windows, only show information about processor groups. All of them are displayed, while the default verbose output only shows them if there are more than one. -f --force If the destination file already exists, overwrite it. -l --logical Display hwloc logical indexes of all objects, with prefix "L#". By default, both logical and physical/OS indexes are displayed for PUs and NUMA nodes, logical only for cores, dies and packages, and no index for other types. -p --physical Display OS/physical indexes of all objects, with prefix "P#". By default, both logical and physical/OS indexes are displayed for PUs and NUMA nodes, logical only for cores, dies and packages, and no index for other types. --logical-index-prefix <prefix> Replace " L#" with the given prefix for logical indexes. --os-index-prefix <prefix> Replace " P#" with the given prefix for physical/OS indexes. -c --cpuset Display the cpuset of each object. -C --cpuset-only Only display the cpuset of each object; do not display anything else about the object. --taskset Show CPU set strings in the format recognized by the taskset command-line program instead of hwloc-specific CPU set string format. This option should be combined with --cpuset or --cpuset-only, otherwise it will imply --cpuset. --only <type> Only show objects of the given type in the textual output. <type> may contain a filter to select specific objects among the type. For instance --only NUMA[HBM] only shows NUMA nodes marked with subtype "HBM", while --only "numa[mcdram]" only shows MCDRAM NUMA nodes on KNL. --filter <type>:<kind>, --filter <type> Filter objects of type <type>, or of any type if <type> is "all". "io", "cache" and "icache" are also supported. <kind> specifies the filtering behavior. If "none" or not specified, all objects of the given type are removed. If "all", all objects are kept as usual. If "structure", objects are kept when they bring structure to the topology. If "important" (only applicable to I/O), only important objects are kept. See hwloc_topology_set_type_filter() for more details. hwloc supports filtering any type except PUs and NUMA nodes. lstopo also offers PU and NUMA node filtering by hiding them in the graphical and textual outputs, but any object included in them (for instance Misc) will be hidden as well. Note that PUs and NUMA nodes may not be ignored in the XML output. Note also that the top-level object type cannot be ignored (usually Machine or System). --ignore <type> This is the old way to specify --filter <type>:none. --no-smt Ignore PUs. This is identical to --filter PU:none. --no-caches Do not show caches. This is identical to --filter cache:none. --no-useless-caches This is identical to --filter cache:structure. --no-icaches This is identical to --filter icache:none. --disallowed Include objects disallowed by administrative limitations (e.g Cgroups on Linux). Offline PUs and NUMA nodes are still ignored. --allow <all|local|0xff|nodeset=0xf0> Include objects disallowed by administrative limitations (implies --disallowed) and also change the set of allowed ones. If local is given, only objects available to the current process are allowed (default behavior when loading from the native operating system backend). It may be useful if the topology was created by another process (with different administrative restrictions such as Linux Cgroups) and loaded here loaded from XML or synthetic. This case implies --thissystem. If all, all objects are allowed. If a bitmap is given as a hexadecimal string, it is used as the set of allowed PUs. If a bitmap is given after prefix nodeset=, it is the set of allowed NUMA nodes. --flags <flags> Enforce topology flags. Flags may be given as numeric values or as a comma-separated list of flag names that are passed to hwloc_topology_set_flags(). Those names may be substrings of actual flag names as long as a single one matches, for instance disallowed,thissystem_allowed. The default is 8 (or import). --merge Do not show levels that do not have a hierarchical impact. This sets HWLOC_TYPE_FILTER_KEEP_STRUCTURE for all object types. This is identical to --filter all:structure. --no-factorize --no-factorize=<type> Never factorize identical objects in the graphical output. If an object type is given, only factorizing of these objects is disabled. This only applies to normal CPU-side objects, it is independent from PCI collapsing. --factorize --factorize=[<type>,]<N>[,<L>[,<F>] Factorize identical children in the graphical output (enabled by default). If <N> is specified (4 by default), factorizing only occurs when there are strictly more than N identical children. If <L> and <F> are specified, they set the numbers of first and last children to keep after factorizing. If an object type is given, only factorizing of these objects is configured. This only applies to normal CPU-side object, it is independent from PCI collapsing. --no-collapse Do not collapse identical PCI devices. By default, identical sibling PCI devices (such as many virtual functions inside a single physical device) are collapsed. --no-cpukinds Do not show different kinds of CPUs in the graphical output. By default, when supported, different types of lines, thickness and bold font may be used to display PU boxes of different kinds. --restrict <cpuset> Restrict the topology to the given cpuset. This removes some PUs and their now-child-less parents. Beware that restricting the PUs in a topology may change the logical indexes of many objects, including NUMA nodes. --restrict nodeset=<nodeset> Restrict the topology to the given nodeset. (unless --restrict-flags specifies something different). This removes some NUMA nodes and their now-child-less parents. Beware that restricting the NUMA nodes in a topology may change the logical indexes of many objects, including PUs. --restrict binding Restrict the topology to the current process binding. This option requires the use of the actual current machine topology (or any other topology with --thissystem or with HWLOC_THISSYSTEM set to 1 in the environment). Beware that restricting the topology may change the logical indexes of many objects, including PUs and NUMA nodes. --restrict-flags <flags> Enforce flags when restricting the topology. Flags may be given as numeric values or as a comma-separated list of flag names that are passed to hwloc_topology_restrict(). Those names may be substrings of actual flag names as long as a single one matches, for instance bynodeset,memless. The default is 0 (or none). --no-io Do not show any I/O device or bridge. This is identical to --filter io:none. By default, common devices (GPUs, NICs, block devices, ...) and interesting bridges/switches are shown. --no-bridges Do not show any I/O bridge except hostbridges. This is identical to --filter bridge:none. By default, common devices (GPUs, NICs, block devices, ...) and interesting bridges/switches are shown. --whole-io Show all I/O devices and bridges. This is identical to --filter io:all. By default, only common devices (GPUs, NICs, block devices, ...) and interesting bridges/switches are shown. --thissystem Assume that the selected backend provides the topology for the system on which we are running. This is useful when loading a custom topology such as an XML file and using --restrict binding or --allow all. --pid <pid> Detect topology as seen by process <pid>, i.e. as if process <pid> did the discovery itself. Note that this can for instance change the set of allowed processors. Also show this process current CPU and Memory binding by marking the corresponding PUs and NUMA nodes (in Green in the graphical output, see the COLORS section below, or by appending (binding) to the verbose text output). If 0 is given as pid, the current binding for the lstopo process will be shown. --ps --top Show existing processes as misc objects in the output. To avoid uselessly cluttering the output, only processes that are restricted to some part of the machine are shown. On Linux, kernel threads are not shown. If many processes appear, the output may become hard to read anyway, making the hwloc-ps program more practical. See --misc-from for a customizable variant using hwloc-ps. --misc-from <file> Add Misc objects as described in <file> containing entries such as: name=myMisc1 cpuset=0x5 name=myMisc2 cpuset=0x7 subtype=myOptionalSubtype This is useful for combining with hwloc-ps --lstopo-misc (see EXAMPLES below) because hwloc-ps is far more customizable than lstopo's --top option. --children-order <order> Change the order of the different kinds of children with respect to their parent in the graphical output. <order> may be a comma-separated list of keywords among: memory:above displays memory children above other children (and above the parent if it is a cache). PUs are therefore below their local NUMA nodes, like hwloc 1.x did. io:right and misc:right place I/O or Misc children on the right of CPU children. io:below and misc:below place I/O or Misc children below CPU children. plain places everything not specified together with normal CPU children. If only plain is specified, lstopo displays the topology in a basic manner that strictly matches the actual tree: Memory, I/O and Misc children are listed below their parent just like any other child. PUs are therefore on the side of their local NUMA nodes, below a common ancestor. This output may result in strange layouts since the size of Memory, CPU and I/O children may be very different, causing the placement algorithm to poorly arrange them in rows. The default order is memory:above,io:right,misc:right which means Memory children are above CPU children while I/O and Misc are together on the right. Up to hwloc 2.5, the default was rather to memory:above,plain. Additionally, memory:above, io:right, io:below, misc:right and misc:below may be suffixed with :horiz, :vert or :rect to force the horizontal, vertical or rectangular layout of children inside these sections. See also the GRAPHICAL OUTPUT and LAYOUT sections below. --fontsize <size> Set the size of text font in the graphical output. The default is 10. Boxes are scaled according to the text size. The LSTOPO_TEXT_XSCALE environment variable may be used to further scale the width of boxes (its default value is 1.0). The --fontsize option is ignored in the ASCII backend. --gridsize <size> Set the margin between elements in the graphical output. The default is 7. It was 10 prior to hwloc 2.1. This option is ignored in the ASCII backend. --linespacing <size> Set the spacing between lines of text in the graphical output. The default is 4. The option was included in --gridsize prior to hwloc 2.1 (and its default was 10). This option is ignored in the ASCII backend. --thickness <size> Set the thickness of lines and boxes in the graphical output. The default is 1. This option is ignored in the ASCII backend. --horiz, --horiz=<type1,...> Force a horizontal graphical layout instead of nearly 4/3 ratio in the graphical output. If a comma-separated list of object types is given, the layout only applies to the corresponding container objects. Ignored for bridges since their children are always vertically aligned. --vert, --vert=<type1,...> Force a vertical graphical layout instead of nearly 4/3 ratio in the graphical output. If a comma-separated list of object types is given, the layout only applies to the corresponding container objects. --rect, --rect=<type1,...> Force a rectangular graphical layout with nearly 4/3 ratio in the graphical output. If a comma-separated list of object types is given, the layout only applies to the corresponding container objects. Ignored for bridges since their children are always vertically aligned. --no-text, --no-text=<type1,...> Do not display any text in boxes in the graphical output. If a comma-separated list of object types is given, text is disabled for the corresponding objects. This is mostly useful for removing text from Group objects. --text, --text=<type1,...> Display text in boxes in the graphical output (default). If a comma-separated list of object types is given, text is reenabled for the corresponding objects (if it was previously disabled with --no-text). --no-index, --no-index=<type1,...> Do not show object indexes in the graphical output. If a comma- separated list of object types is given, indexes are disabled for the corresponding objects. --index, --index=<type1,...> Show object indexes in the graphical output (default). If a comma-separated list of object types is given, indexes are reenabled for the corresponding objects (if they were previously disabled with --no-index). --no-attrs, --no-attrs=<type1,...> Do not show object attributes (such as memory size, cache size, PCI bus ID, PCI link speed, etc.) in the graphical output. If a comma-separated list of object types is given, attributes are disabled for the corresponding objects. --attrs, --attrs=<type1,...> Show object attributes (such as memory size, cache size, PCI bus ID, PCI link speed, etc.) in the graphical output (default). If a comma-separated list of object types is given, attributes are reenabled for the corresponding objects (if they were previously disabled with --no-attrs). --no-legend Remove all text legend lines at the bottom of the graphical output. --no-default-legend Remove default text legend lines at the bottom of the graphical output. User-added legend lines with --append-legend or the "lstopoLegend" info are still displayed if any. --append-legend <line> Append the line of text to the bottom of the legend in the graphical output. If adding multiple lines, each line should be given separately by passing this option multiple times. Additional legend lines may also be specified inside the topology using the "lstopoLegend" info attributes on the topology root object. --grey, --greyscale Use greyscale instead of colors in the graphical output. --palette <grey|greyscale|defaut|colors|white|none> Change the color palette. Passing grey or greyscale is identical to passing --grey or --greyscale. Passing white or none uses white instead of colors for all box backgrounds. Passing default or colors reverts back to the default color palette. --palette type=#rrggbb Replace the color of the given box type with the given 3x8bit hexadecimal RGB combination (e.g. #ff0000 is red). Existing types are machine, group, package, group_in_package, die, core, pu, numanode, memories (box containing multiple memory children), cache, pcidev, osdev, bridge, and misc. See also CUSTOM COLOR below for customizing individual objects. --binding-color <none|#rrggbb> Do not colorize PUs and NUMA nodes according to the binding in the graphical output. Or change the color to the given 3x8bit hexadecimal RGB combination (e.g. #ff0000 is red). --disallowed-color <none|#rrggbb> Do not colorize disallowed PUs and NUMA nodes in the graphical output. Or change the color to the given 3x8bit hexadecimal RGB combination (e.g. #00ff00 is green). --top-color <none|#rrggbb> Do not colorize task objects in the graphical output when --top is given. Or change the color to the given 3x8bit hexadecimal RGB combination (e.g. #0000ff is blue). This is actually applied to Misc objects of subtype Process or Thread. --version Report version and exit. -h --help Display help message and exit.
|
To display the machine topology in textual mode: lstopo-no-graphics To display the machine topology in ascii-art mode: lstopo-no-graphics -.ascii To display in graphical mode (assuming that the DISPLAY environment variable is set to a relevant value): lstopo To export the topology to a PNG file: lstopo file.png To export an XML file on a machine and later display the corresponding graphical output on another machine: machine1$ lstopo file.xml <transfer file.xml from machine1 to machine2> machine2$ lstopo --input file.xml To save the current machine topology to XML and later reload it faster while still considering it as the current machine: $ lstopo file.xml <...> $ lstopo --input file.xml --thissystem To restrict an XML topology to only physical processors 0, 1, 4 and 5: lstopo --input file.xml --restrict 0x33 newfile.xml To restrict an XML topology to only numa node whose logical index is 1: lstopo --input file.xml --restrict $(hwloc-calc --input file.xml node:1) newfile.xml To display a summary of the topology: lstopo -s To get more details about the topology: lstopo -v To only show cores: lstopo --only core To show cpusets: lstopo --cpuset To only show the cpusets of package: lstopo --only package --cpuset-only Simulate a fake hierarchy; this example shows with 2 NUMA nodes of 2 processor units: lstopo --input "node:2 2" To count the number of logical processors in the system lstopo --only pu | wc -l To append the kernel release and version to the graphical legend: lstopo --append-legend "Kernel release: $(uname -r)" --append-legend "Kernel version: $(uname -v)" To show where a process and its children are bound by combining with hwloc-ps: hwloc-ps --pid-children 23 --lstopo-misc - | lstopo --misc-from - NOTES lstopo displays memory and cache sizes with units such as kB (1 kilobyte = 1000 bytes) or GB (1 gigabyte = 1000*1000*1000 bytes) while it actually means KiB (1 kibibyte = 1024 bytes) or GiB (1 gibibytes = 1024*1024*1024 bytes) . SEE ALSO hwloc(7), hwloc-info(1), hwloc-bind(1), hwloc-annotate(1), hwloc-ps(1), hwloc-gather-topology(1), hwloc-gather-cpuid(1) 2.10.0 December 4, 2023 LSTOPO(1)
|
strerror
|
The strerror(), strerror_r(), and perror() functions look up the error message string corresponding to an error number. The strerror() function accepts an error number argument errnum and returns a pointer to the corresponding message string. The strerror_r() function renders the same result into strerrbuf for a maximum of buflen characters and returns 0 upon success. The perror() function finds the error message corresponding to the current value of the global variable errno (intro(2)) and writes it, followed by a newline, to the standard error file descriptor. If the argument s is non-NULL and does not point to the null character, this string is prepended to the message string and separated from it by a colon and space (â: â); otherwise, only the error message string is printed. If the error number is not recognized, these functions return an error message string containing âUnknown error: â followed by the error number in decimal. The strerror() and strerror_r() functions return EINVAL as a warning. Error numbers recognized by this implementation fall in the range 0 <= errnum < sys_nerr. If insufficient storage is provided in strerrbuf (as specified in buflen) to contain the error string, strerror_r() returns ERANGE and strerrbuf will contain an error message that has been truncated and NUL terminated to fit the length specified by buflen. The message strings can be accessed directly using the external array sys_errlist. The external value sys_nerr contains a count of the messages in sys_errlist. The use of these variables is deprecated; strerror() or strerror_r() should be used instead. SEE ALSO intro(2), psignal(3) STANDARDS The perror() and strerror() functions conform to ISO/IEC 9899:1999 (âISO C99â). The strerror_r() function conforms to IEEE Std 1003.1-2001 (âPOSIX.1â). HISTORY The strerror() and perror() functions first appeared in 4.4BSD. The strerror_r() function was implemented in FreeBSD 4.4 by Wes Peters âšwes@FreeBSD.orgâ©. BUGS For unknown error numbers, the strerror() function will return its result in a static buffer which may be overwritten by subsequent calls. The return type for strerror() is missing a type-qualifier; it should actually be const char *. Programs that use the deprecated sys_errlist variable often fail to compile because they declare it inconsistently. macOS 14.5 October 12, 2004 macOS 14.5
|
perror, strerror, strerror_r, sys_errlist, sys_nerr â system error messages LIBRARY Standard C Library (libc, -lc)
|
#include <stdio.h> void perror(const char *s); extern const char * const sys_errlist[]; extern const int sys_nerr; #include <string.h> char * strerror(int errnum); int strerror_r(int errnum, char *strerrbuf, size_t buflen);
| null | null |
bd_splice
| null | null | null | null | null |
pdftotext
|
Pdftotext converts Portable Document Format (PDF) files to plain text. Pdftotext reads the PDF file, PDF-file, and writes a text file, text-file. If text-file is not specified, pdftotext converts file.pdf to file.txt. If text-file is ÂŽ-', the text is sent to stdout. If PDF-file is ÂŽ-', it reads the PDF file from stdin.
|
pdftotext - Portable Document Format (PDF) to text converter (version 3.03)
|
pdftotext [options] PDF-file [text-file]
|
-f number Specifies the first page to convert. -l number Specifies the last page to convert. -r number Specifies the resolution, in DPI. The default is 72 DPI. -x number Specifies the x-coordinate of the crop area top left corner -y number Specifies the y-coordinate of the crop area top left corner -W number Specifies the width of crop area in pixels (default is 0) -H number Specifies the height of crop area in pixels (default is 0) -layout Maintain (as best as possible) the original physical layout of the text. The default is to ÂŽundo' physical layout (columns, hyphenation, etc.) and output the text in reading order. -fixed number Assume fixed-pitch (or tabular) text, with the specified character width (in points). This forces physical layout mode. -raw Keep the text in content stream order. This is a hack which often "undoes" column formatting, etc. Use of raw mode is no longer recommended. -nodiag Discard diagonal text (i.e., text that is not close to one of the 0, 90, 180, or 270 degree axes). This is useful for skipping watermarks drawn on body text. -htmlmeta Generate a simple HTML file, including the meta information. This simply wraps the text in <pre> and </pre> and prepends the meta headers. -bbox Generate an XHTML file containing bounding box information for each word in the file. -bbox-layout Generate an XHTML file containing bounding box information for each block, line, and word in the file. -tsv Generate a TSV file containing the bounding box information for each block, line, and word in the file. -cropbox Use the crop box rather than the media box with -bbox and -bbox- layout. -colspacing number Specifies how much spacing we allow after a word before considering adjacent text to be a new column, measured as a fraction of the font size. Current default is 0.7, old releases had a 0.3 default. -enc encoding-name Sets the encoding to use for text output. This defaults to "UTF-8". -listenc Lists the available encodings -eol unix | dos | mac Sets the end-of-line convention to use for text output. -nopgbrk Don't insert page breaks (form feed characters) between pages. -opw password Specify the owner password for the PDF file. Providing this will bypass all security restrictions. -upw password Specify the user password for the PDF file. -q Don't print any messages or errors. -v Print copyright and version information. -h Print usage information. (-help and --help are equivalent.) BUGS Some PDF files contain fonts whose encodings have been mangled beyond recognition. There is no way (short of OCR) to extract text from these files. EXIT CODES The Xpdf tools use the following exit codes: 0 No error. 1 Error opening a PDF file. 2 Error opening an output file. 3 Error related to PDF permissions. 99 Other error. AUTHOR The pdftotext software and documentation are copyright 1996-2011 Glyph & Cog, LLC. SEE ALSO pdfdetach(1), pdffonts(1), pdfimages(1), pdfinfo(1), pdftocairo(1), pdftohtml(1), pdftoppm(1), pdftops(1), pdfseparate(1), pdfsig(1), pdfunite(1) 15 August 2011 pdftotext(1)
| null |
plotframes
| null | null | null | null | null |
obs
| null | null | null | null | null |
vlc
| null | null | null | null | null |
defncopy
|
defncopy is a utility program distributed with FreeTDS. It replaces a similar program of the same name distributed by Sybase. defncopy reads the text of a stored procedure or view, and writes a script suitable for recreating the procedure or view. For tables, it reads the output of sp_help and constructs a âCREATE TABLEâ statement, complete with âCREATE INDEXâ,too. owner is optional if you or the database owner is the owner of the procedure/view being copied. object_name is the name of the system object you wish to extract.
|
defncopy â extract procedures and views from a Microsoft server.
|
defncopy [-v] [-U username] [-P password] [-S server] [-D database] [-i input_file] [-o output_file] [owner.object_name [owner.object_name ...]]
|
-U username database server login name. -P password database server password. -S server database server to which to connect. -D database database to use. Optional if the procedure/view being extracted is in your default database. -i input_file a script to apply to the database. Not currently implemented. -o output_file a file to hold the script, defaults to standard output. -v Show version information and copyright notice. NOTES defncopy is a filter; it reads from standard input, writes to standard output, and writes errors to standard error. The -i, -o, and -e options override these defaults. defncopy makes use of the db-lib API provided by FreeTDS. This API is of course also available to application developers. EXIT STATUS defncopy exits 0 on success, and >0 if the server cannot process the query. defncopy will report any errors returned by the server, but will continue processing. HISTORY defncopy first appeared in FreeTDS 0.63. AUTHORS The defncopy utility was written by James K. Lowden âšjklowden@schemamania.org.â© BUGS Works only with Microsoft servers and ancient Sybase servers. Does not create primary keys. Many options are defined by Sybase that this version does not implement. Feel free to correct this situation. In theory, defncopy could apply/produce DDL for any system object, but at present only tables, procedures and views are supported, and only for extraction. FreeTDS 1.4.21 April 26, 2012 FreeTDS 1.4.21
| null |
yapf
| null | null | null | null | null |
generate_lut_template
| null | null | null | null | null |
filetype
| null | null | null | null | null |
pyrsa-keygen
| null | null | null | null | null |
chktest
| null | null | null | null | null |
geckodriver
| null | null | null | null | null |
crl_app
| null | null | null | null | null |
python3-config
| null | null | null | null | null |
pango-segmentation
| null | null | null | null | null |
rsa_verify
| null | null | null | null | null |
f2py
| null | null | null | null | null |
pinecone
| null | null | null | null | null |
gradio
| null | null | null | null | null |
tiffset
|
tiffset sets the value of a TIFF header to a specified value or removes an existing setting.
|
tiffset - set or unset a field in a TIFF header
|
tiffset [ options ] filename.tif
|
-d dirnumber Change the current directory (starting at 0). -s tagnumber [ count ] value ⊠Set the value of the named tag to the value or values specified. -sd diroffset Change the current directory by offset. -sf tagnumber filename Set the value of the tag to the contents of filename. This option is supported for ASCII tags only. -u tagnumber Unset the tag.
|
The following example sets the image description tag (270) of a.tif to the contents of the file descrip: tiffset -sf 270 descrip a.tif The following example sets the artist tag (315) of a.tif to the string Anonymous: tiffset -s 315 Anonymous a.tif This example sets the resolution of the file a.tif to 300 dpi: tiffset -s 296 2 a.tif tiffset -s 282 300.0 a.tif tiffset -s 283 300.0 a.tif Set the photometric interpretation of the third page of a.tif to min-is-black (ie. inverts it): tiffset -d 2 -s 262 1 a.tif SEE ALSO tiffdump (1), tiffinfo (1), tiffcp (1), libtiff (3tiff) AUTHOR LibTIFF contributors COPYRIGHT 1988-2022, LibTIFF contributors 4.6 September 8, 2023 TIFFSET(1)
|
local_tone_map
| null | null | null | null | null |
automake-1.16
|
Generate Makefile.in for configure from Makefile.am. Operation modes: --help print this help, then exit --version print version number, then exit -v, --verbose verbosely list files processed --no-force only update Makefile.in's that are out of date -W, --warnings=CATEGORY report the warnings falling in CATEGORY Dependency tracking: -i, --ignore-deps disable dependency tracking code --include-deps enable dependency tracking code Flavors: --foreign set strictness to foreign --gnits set strictness to gnits --gnu set strictness to gnu Library files: -a, --add-missing add missing standard files to package --libdir=DIR set directory storing library files --print-libdir print directory storing library files -c, --copy with -a, copy missing files (default is symlink) -f, --force-missing force update of standard files Warning categories include: cross cross compilation issues gnu GNU coding standards (default in gnu and gnits modes) obsolete obsolete features or constructions (default) override user redefinitions of Automake rules or variables portability portability issues (default in gnu and gnits modes) portability-recursive nested Make variables (default with -Wportability) extra-portability extra portability issues related to obscure tools syntax dubious syntactic constructs (default) unsupported unsupported or incomplete features (default) all all the warnings no-CATEGORY turn off warnings in CATEGORY none turn off all the warnings error treat warnings as errors Files automatically distributed if found (always): ABOUT-GNU TODO install-sh mdate-sh ABOUT-NLS ar-lib libversion.in missing BACKLOG compile ltcf-c.sh mkinstalldirs COPYING config.guess ltcf-cxx.sh py-compile COPYING.DOC config.rpath ltcf-gcj.sh texinfo.tex COPYING.LESSER config.sub ltconfig ylwrap COPYING.LIB depcomp ltmain.sh Files automatically distributed if found (as .md if needed): AUTHORS[.md] INSTALL[.md] README[.md] THANKS[.md] ChangeLog[.md] NEWS[.md] Files automatically distributed if found (under certain conditions): README-alpha[.md] config.h.bot configure configure.in acconfig.h config.h.top configure.ac stamp-vti aclocal.m4 AUTHOR Written by Tom Tromey <tromey@redhat.com> and Alexandre Duret-Lutz <adl@gnu.org>. REPORTING BUGS Report bugs to <bug-automake@gnu.org>. GNU Automake home page: <https://www.gnu.org/software/automake/>. General help using GNU software: <https://www.gnu.org/gethelp/>. COPYRIGHT Copyright © 2021 Free Software Foundation, Inc. License GPLv2+: GNU GPL version 2 or later <https://gnu.org/licenses/gpl-2.0.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO The full documentation for automake is maintained as a Texinfo manual. If the info and automake programs are properly installed at your site, the command info automake should give you access to the complete manual. GNU automake 1.16.5 October 2021 AUTOMAKE(1)
|
automake - manual page for automake 1.16.5
|
automake-1.16 [OPTION]... [Makefile]...
| null | null |
ssl_client1
| null | null | null | null | null |
rtmpsrv
| null | null | null | null | null |
pip
| null | null | null | null | null |
2to3-3.10
| null | null | null | null | null |
redis-check-aof
| null | null | null | null | null |
xyb_range
| null | null | null | null | null |
gnutls-certtool
|
Tool to parse and generate X.509 certificates, requests and private keys. It can be used interactively or non interactively by specifying the template command line option. The tool accepts files or supported URIs via the --infile option. In case PIN is required for URI access you can provide it using the environment variables GNUTLS_PIN and GNUTLS_SO_PIN.
|
certtool - GnuTLS certificate tool
|
certtool [-flags] [-flag [value]] [--option-name[[=| ]value]] All arguments must be options.
|
-d num, --debug=num Enable debugging. This option takes an integer number as its argument. The value of num is constrained to being: in the range 0 through 9999 Specifies the debug level. -V, --verbose More verbose output. --infile=file Input file. --outfile=str Output file. --attime=timestamp Perform validation at the timestamp instead of the system time. timestamp is an instance in time encoded as Unix time or in a human readable timestring such as "29 Feb 2004", "2004-02-29". Full documentation available at <https://www.gnu.org/software/coreutils/manual/html_node/Date-input-formats.html> or locally via info '(coreutils) date invocation'. Certificate related options -i, --certificate-info Print information on the given certificate. --pubkey-info Print information on a public key. The option combined with --load-request, --load-pubkey, --load-privkey and --load-certificate will extract the public key of the object in question. -s, --generate-self-signed Generate a self-signed certificate. -c, --generate-certificate Generate a signed certificate. --generate-proxy Generates a proxy certificate. -u, --update-certificate Update a signed certificate. --fingerprint Print the fingerprint of the given certificate. This is a simple hash of the DER encoding of the certificate. It can be combined with the --hash parameter. However, it is recommended for identification to use the key-id which depends only on the certificate's key. --key-id Print the key ID of the given certificate. This is a hash of the public key of the given certificate. It identifies the key uniquely, remains the same on a certificate renewal and depends only on signed fields of the certificate. --certificate-pubkey Print certificate's public key. This option is deprecated as a duplicate of --pubkey-info NOTE: THIS OPTION IS DEPRECATED --v1 Generate an X.509 version 1 certificate (with no extensions). --sign-params=str Sign a certificate with a specific signature algorithm. This option can be combined with --generate-certificate, to sign the certificate with a specific signature algorithm variant. The only option supported is 'RSA-PSS', and should be specified when the signer does not have a certificate which is marked for RSA-PSS use only. Certificate request related options --crq-info Print information on the given certificate request. -q, --generate-request Generate a PKCS #10 certificate request. This option must not appear in combination with any of the following options: infile. Will generate a PKCS #10 certificate request. To specify a private key use --load-privkey. --no-crq-extensions Do not use extensions in certificate requests. PKCS#12 file related options --p12-info Print information on a PKCS #12 structure. This option will dump the contents and print the metadata of the provided PKCS #12 structure. --p12-name=str The PKCS #12 friendly name to use. The name to be used for the primary certificate and private key in a PKCS #12 file. --to-p12 Generate a PKCS #12 structure. It requires a certificate, a private key and possibly a CA certificate to be specified. Private key related options -k, --key-info Print information on a private key. --p8-info Print information on a PKCS #8 structure. This option will print information about encrypted PKCS #8 structures. That option does not require the decryption of the structure. --to-rsa Convert an RSA-PSS key to raw RSA format. It requires an RSA-PSS key as input and will output a raw RSA key. This command is necessary for compatibility with applications that cannot read RSA-PSS keys. -p, --generate-privkey Generate a private key. When generating RSA-PSS or RSA-OAEP private keys, the --hash option will restrict the allowed hash for the key; For RSA-PSS keys the --salt-size option is also acceptable. --key-type=str Specify the key type to use on key generation. This option can be combined with --generate-privkey, to specify the key type to be generated. Valid options are, 'rsa', 'rsa-pss', 'rsa-oaep', 'dsa', 'ecdsa', 'ed25519, 'ed448', 'x25519', and 'x448'.'. When combined with certificate generation it can be used to specify an RSA-PSS certificate when an RSA key is given. --bits=num Specify the number of bits for key generation. This option takes an integer number as its argument. --curve=str Specify the curve used for EC key generation. Supported values are secp192r1, secp224r1, secp256r1, secp384r1 and secp521r1. --sec-param=security parameter Specify the security level [low, legacy, medium, high, ultra]. This is alternative to the bits option. --to-p8 Convert a given key to a PKCS #8 structure. This needs to be combined with --load-privkey. -8, --pkcs8 Use PKCS #8 format for private keys. --provable Generate a private key or parameters from a seed using a provable method. This will use the FIPS PUB186-4 algorithms (i.e., Shawe-Taylor) for provable key generation. When specified the private keys or parameters will be generated from a seed, and can be later validated with --verify-provable-privkey to be correctly generated from the seed. You may specify --seed or allow GnuTLS to generate one (recommended). This option can be combined with --generate-privkey or --generate-dh-params. That option applies to RSA and DSA keys. On the DSA keys the PQG parameters are generated using the seed, and on RSA the two primes. --verify-provable-privkey Verify a private key generated from a seed using a provable method. This will use the FIPS-186-4 algorithms for provable key generation. You may specify --seed or use the seed stored in the private key structure. --seed=str When generating a private key use the given hex-encoded seed. The seed acts as a security parameter for the private key, and thus a seed size which corresponds to the security level of the private key should be provided (e.g., 256-bits seed). CRL related options -l, --crl-info Print information on the given CRL structure. --generate-crl Generate a CRL. This option generates a Certificate Revocation List. When combined with --load-crl it would use the loaded CRL as base for the generated (i.e., all revoked certificates in the base will be copied to the new CRL). To add new certificates to the CRL use --load-certificate. --verify-crl Verify a Certificate Revocation List using a trusted list. This option must appear in combination with the following options: load-ca-certificate. The trusted certificate list must be loaded with --load-ca-certificate. Certificate verification related options -e, --verify-chain Verify a PEM encoded certificate chain. Verifies the validity of a certificate chain. That is, an ordered set of certificates where each one is the issuer of the previous, and the first is the end-certificate to be validated. In a proper chain the last certificate is a self signed one. It can be combined with --verify-purpose or --verify-hostname. --verify Verify a PEM encoded certificate (chain) against a trusted set. The trusted certificate list can be loaded with --load-ca-certificate. If no certificate list is provided, then the system's trusted certificate list is used. Note that during verification multiple paths may be explored. On a successful verification the successful path will be the last one. It can be combined with --verify-purpose or --verify-hostname. --verify-hostname=str Specify a hostname to be used for certificate chain verification. This is to be combined with one of the verify certificate options. --verify-email=str Specify a email to be used for certificate chain verification. This option must not appear in combination with any of the following options: verify-hostname. This is to be combined with one of the verify certificate options. --verify-purpose=str Specify a purpose OID to be used for certificate chain verification. This object identifier restricts the purpose of the certificates to be verified. Example purposes are 1.3.6.1.5.5.7.3.1 (TLS WWW), 1.3.6.1.5.5.7.3.4 (EMAIL) etc. Note that a CA certificate without a purpose set (extended key usage) is valid for any purpose. --verify-allow-broken Allow broken algorithms, such as MD5 for verification. This can be combined with --p7-verify, --verify or --verify-chain. --verify-profile=str Specify a security level profile to be used for verification. This option can be used to specify a certificate verification profile. Certificate verification profiles correspond to the security level. This should be one of 'none', 'very weak', 'low', 'legacy', 'medium', 'high', 'ultra', 'future'. Note that by default no profile is applied, unless one is set as minimum in the gnutls configuration file. PKCS#7 structure options --p7-generate Generate a PKCS #7 structure. This option generates a PKCS #7 certificate container structure. To add certificates in the structure use --load-certificate and --load-crl. --p7-sign Signs using a PKCS #7 structure. This option generates a PKCS #7 structure containing a signature for the provided data from infile. The data are stored within the structure. The signer certificate has to be specified using --load-certificate and --load-privkey. The input to --load-certificate can be a list of certificates. In case of a list, the first certificate is used for signing and the other certificates are included in the structure. --p7-detached-sign Signs using a detached PKCS #7 structure. This option generates a PKCS #7 structure containing a signature for the provided data from infile. The signer certificate has to be specified using --load-certificate and --load-privkey. The input to --load-certificate can be a list of certificates. In case of a list, the first certificate is used for signing and the other certificates are included in the structure. --p7-include-cert, --no-p7-include-cert The signer's certificate will be included in the cert list. The no-p7-include-cert form will disable the option. This option is enabled by default. This options works with --p7-sign or --p7-detached-sign and will include or exclude the signer's certificate into the generated signature. --p7-time, --no-p7-time Will include a timestamp in the PKCS #7 structure. The no-p7-time form will disable the option. This option will include a timestamp in the generated signature --p7-show-data, --no-p7-show-data Will show the embedded data in the PKCS #7 structure. The no-p7-show-data form will disable the option. This option can be combined with --p7-verify or --p7-info and will display the embedded signed data in the PKCS #7 structure. --p7-info Print information on a PKCS #7 structure. --p7-verify Verify the provided PKCS #7 structure. This option verifies the signed PKCS #7 structure. The certificate list to use for verification can be specified with --load-ca-certificate. When no certificate list is provided, then the system's certificate list is used. Alternatively a direct signer can be provided using --load-certificate. A key purpose can be enforced with the --verify-purpose option, and the --load-data option will utilize detached data. --smime-to-p7 Convert S/MIME to PKCS #7 structure. Other options --generate-dh-params Generate PKCS #3 encoded Diffie-Hellman parameters. The will generate random parameters to be used with Diffie-Hellman key exchange. The output parameters will be in PKCS #3 format. Note that it is recommended to use the --get-dh-params option instead. NOTE: THIS OPTION IS DEPRECATED --get-dh-params List the included PKCS #3 encoded Diffie-Hellman parameters. Returns stored DH parameters in GnuTLS. Those parameters returned are defined in RFC7919, and can be considered standard parameters for a TLS key exchange. This option is provided for old applications which require DH parameters to be specified; modern GnuTLS applications should not require them. --dh-info Print information PKCS #3 encoded Diffie-Hellman parameters. --load-privkey=str Loads a private key file. This can be either a file or a PKCS #11 URL --load-pubkey=str Loads a public key file. This can be either a file or a PKCS #11 URL --load-request=str Loads a certificate request file. This option can be used with a file --load-certificate=str Loads a certificate file. This option can be used with a file --load-ca-privkey=str Loads the certificate authority's private key file. This can be either a file or a PKCS #11 URL --load-ca-certificate=str Loads the certificate authority's certificate file. This can be either a file or a PKCS #11 URL --load-crl=str Loads the provided CRL. This option can be used with a file --load-data=str Loads auxiliary data. This option can be used with a file --password=str Password to use. You can use this option to specify the password in the command line instead of reading it from the tty. Note, that the command line arguments are available for view in others in the system. Specifying password as '' is the same as specifying no password. --null-password Enforce a NULL password. This option enforces a NULL password. This is different than the empty or no password in schemas like PKCS #8. --empty-password Enforce an empty password. This option enforces an empty password. This is different than the NULL or no password in schemas like PKCS #8. --hex-numbers Print big number in an easier format to parse. --cprint In certain operations it prints the information in C-friendly format. In certain operations it prints the information in C-friendly format, suitable for including into C programs. --rsa Generate RSA key. When combined with --generate-privkey generates an RSA private key. NOTE: THIS OPTION IS DEPRECATED --dsa Generate DSA key. When combined with --generate-privkey generates a DSA private key. NOTE: THIS OPTION IS DEPRECATED --ecc Generate ECC (ECDSA) key. When combined with --generate-privkey generates an elliptic curve private key to be used with ECDSA. NOTE: THIS OPTION IS DEPRECATED --ecdsa This is an alias for the --ecc option. NOTE: THIS OPTION IS DEPRECATED --hash=str Hash algorithm to use for signing. Available hash functions are SHA1, RMD160, SHA256, SHA384, SHA512, SHA3-224, SHA3-256, SHA3-384, SHA3-512. --salt-size=num Specify the RSA-PSS key default salt size. This option takes an integer number as its argument. Typical keys shouldn't set or restrict this option. --label=str Specify the RSA-OAEP label, encoded in hexadecimal. Typical keys shouldn't set or restrict this option. --inder, --no-inder Use DER format for input certificates, private keys, and DH parameters . The no-inder form will disable the option. The input files will be assumed to be in DER or RAW format. Unlike options that in PEM input would allow multiple input data (e.g. multiple certificates), when reading in DER format a single data structure is read. --inraw This is an alias for the --inder option. --outder, --no-outder Use DER format for output certificates, private keys, and DH parameters. The no-outder form will disable the option. The output will be in DER or RAW format. --outraw This is an alias for the --outder option. --disable-quick-random No effect. NOTE: THIS OPTION IS DEPRECATED --template=str Template file to use for non-interactive operation. --stdout-info Print information to stdout instead of stderr. --ask-pass Enable interaction for entering password when in batch mode. This option will enable interaction to enter password when in batch mode. That is useful when the template option has been specified. --pkcs-cipher=cipher Cipher to use for PKCS #8 and #12 operations. Cipher may be one of 3des, 3des-pkcs12, aes-128, aes-192, aes-256, rc2-40, arcfour. --provider=str Specify the PKCS #11 provider library. This will override the default options in /etc/gnutls/pkcs11.conf --text, --no-text Output textual information before PEM-encoded certificates, private keys, etc. The no-text form will disable the option. This option is enabled by default. Output textual information before PEM-encoded data -v arg, --version=arg Output version of program and exit. The default mode is `v', a simple version. The `c' mode will print copyright information and `n' will print the full copyright notice. -h, --help Display usage information and exit. -!, --more-help Pass the extended usage information through a pager. FILES Certtool's template file format A template file can be used to avoid the interactive questions of certtool. Initially create a file named 'cert.cfg' that contains the information about the certificate. The template can be used as below: $ certtool --generate-certificate --load-privkey key.pem --template cert.cfg --outfile cert.pem --load-ca-certificate ca-cert.pem --load-ca-privkey ca-key.pem An example certtool template file that can be used to generate a certificate request or a self signed certificate follows. # X.509 Certificate options # # DN options # The organization of the subject. organization = "Koko inc." # The organizational unit of the subject. unit = "sleeping dept." # The locality of the subject. # locality = # The state of the certificate owner. state = "Attiki" # The country of the subject. Two letter code. country = GR # The common name of the certificate owner. cn = "Cindy Lauper" # A user id of the certificate owner. #uid = "clauper" # Set domain components #dc = "name" #dc = "domain" # If the supported DN OIDs are not adequate you can set # any OID here. # For example set the X.520 Title and the X.520 Pseudonym # by using OID and string pairs. #dn_oid = "2.5.4.12 Dr." #dn_oid = "2.5.4.65 jackal" # This is deprecated and should not be used in new # certificates. # pkcs9_email = "none@none.org" # An alternative way to set the certificate's distinguished name directly # is with the "dn" option. The attribute names allowed are: # C (country), street, O (organization), OU (unit), title, CN (common name), # L (locality), ST (state), placeOfBirth, gender, countryOfCitizenship, # countryOfResidence, serialNumber, telephoneNumber, surName, initials, # generationQualifier, givenName, pseudonym, dnQualifier, postalCode, name, # businessCategory, DC, UID, jurisdictionOfIncorporationLocalityName, # jurisdictionOfIncorporationStateOrProvinceName, # jurisdictionOfIncorporationCountryName, XmppAddr, and numeric OIDs. #dn = "cn = Nikos,st = New Something,C=GR,surName=Mavrogiannopoulos,2.5.4.9=Arkadias" # The serial number of the certificate # The value is in decimal (i.e. 1963) or hex (i.e. 0x07ab). # Comment the field for a random serial number. serial = 007 # In how many days, counting from today, this certificate will expire. # Use -1 if there is no expiration date. expiration_days = 700 # Alternatively you may set concrete dates and time. The GNU date string # formats are accepted. See: # https://www.gnu.org/software/tar/manual/html_node/Date-input-formats.html #activation_date = "2004-02-29 16:21:42" #expiration_date = "2025-02-29 16:24:41" # X.509 v3 extensions # A dnsname in case of a WWW server. #dns_name = "www.none.org" #dns_name = "www.morethanone.org" # An othername defined by an OID and a hex encoded string #other_name = "1.3.6.1.5.2.2 302ca00d1b0b56414e5245494e2e4f5247a11b3019a006020400000002a10f300d1b047269636b1b0561646d696e" #other_name_utf8 = "1.2.4.5.6 A UTF8 string" #other_name_octet = "1.2.4.5.6 A string that will be encoded as ASN.1 octet string" # Allows writing an XmppAddr Identifier #xmpp_name = juliet@im.example.com # Names used in PKINIT #krb5_principal = user@REALM.COM #krb5_principal = HTTP/user@REALM.COM # A subject alternative name URI #uri = "https://www.example.com" # An IP address in case of a server. #ip_address = "192.168.1.1" # An email in case of a person email = "none@none.org" # TLS feature (rfc7633) extension. That can is used to indicate mandatory TLS # extension features to be provided by the server. In practice this is used # to require the Status Request (extid: 5) extension from the server. That is, # to require the server holding this certificate to provide a stapled OCSP response. # You can have multiple lines for multiple TLS features. # To ask for OCSP status request use: #tls_feature = 5 # Challenge password used in certificate requests challenge_password = 123456 # Password when encrypting a private key #password = secret # An URL that has CRLs (certificate revocation lists) # available. Needed in CA certificates. #crl_dist_points = "https://www.getcrl.crl/getcrl/" # Whether this is a CA certificate or not #ca # Subject Unique ID (in hex) #subject_unique_id = 00153224 # Issuer Unique ID (in hex) #issuer_unique_id = 00153225 #### Key usage # The following key usage flags are used by CAs and end certificates # Whether this certificate will be used to sign data (needed # in TLS DHE ciphersuites). This is the digitalSignature flag # in RFC5280 terminology. signing_key # Whether this certificate will be used to encrypt data (needed # in TLS RSA ciphersuites). Note that it is preferred to use different # keys for encryption and signing. This is the keyEncipherment flag # in RFC5280 terminology. encryption_key # Whether this key will be used to sign other certificates. The # keyCertSign flag in RFC5280 terminology. #cert_signing_key # Whether this key will be used to sign CRLs. The # cRLSign flag in RFC5280 terminology. #crl_signing_key # The keyAgreement flag of RFC5280. Its purpose is loosely # defined. Not use it unless required by a protocol. #key_agreement # The dataEncipherment flag of RFC5280. Its purpose is loosely # defined. Not use it unless required by a protocol. #data_encipherment # The nonRepudiation flag of RFC5280. Its purpose is loosely # defined. Not use it unless required by a protocol. #non_repudiation #### Extended key usage (key purposes) # The following extensions are used in an end certificate # to clarify its purpose. Some CAs also use it to indicate # the types of certificates they are purposed to sign. # Whether this certificate will be used for a TLS client; # this sets the id-kp-clientAuth (1.3.6.1.5.5.7.3.2) of # extended key usage. #tls_www_client # Whether this certificate will be used for a TLS server; # this sets the id-kp-serverAuth (1.3.6.1.5.5.7.3.1) of # extended key usage. #tls_www_server # Whether this key will be used to sign code. This sets the # id-kp-codeSigning (1.3.6.1.5.5.7.3.3) of extended key usage # extension. #code_signing_key # Whether this key will be used to sign OCSP data. This sets the # id-kp-OCSPSigning (1.3.6.1.5.5.7.3.9) of extended key usage extension. #ocsp_signing_key # Whether this key will be used for time stamping. This sets the # id-kp-timeStamping (1.3.6.1.5.5.7.3.8) of extended key usage extension. #time_stamping_key # Whether this key will be used for email protection. This sets the # id-kp-emailProtection (1.3.6.1.5.5.7.3.4) of extended key usage extension. #email_protection_key # Whether this key will be used for IPsec IKE operations (1.3.6.1.5.5.7.3.17). #ipsec_ike_key ## adding custom key purpose OIDs # for microsoft smart card logon # key_purpose_oid = 1.3.6.1.4.1.311.20.2.2 # for email protection # key_purpose_oid = 1.3.6.1.5.5.7.3.4 # for any purpose (must not be used in intermediate CA certificates) # key_purpose_oid = 2.5.29.37.0 ### end of key purpose OIDs ### Adding arbitrary extensions # This requires to provide the extension OIDs, as well as the extension data in # hex format. The following two options are available since GnuTLS 3.5.3. #add_extension = "1.2.3.4 0x0AAB01ACFE" # As above but encode the data as an octet string #add_extension = "1.2.3.4 octet_string(0x0AAB01ACFE)" # For portability critical extensions shouldn't be set to certificates. #add_critical_extension = "5.6.7.8 0x1AAB01ACFE" # When generating a certificate from a certificate # request, then honor the extensions stored in the request # and store them in the real certificate. #honor_crq_extensions # Alternatively only specific extensions can be copied. #honor_crq_ext = 2.5.29.17 #honor_crq_ext = 2.5.29.15 # Path length constraint. Sets the maximum number of # certificates that can be used to certify this certificate. # (i.e. the certificate chain length) #path_len = -1 #path_len = 2 # OCSP URI # ocsp_uri = https://my.ocsp.server/ocsp # CA issuers URI # ca_issuers_uri = https://my.ca.issuer # Certificate policies #policy1 = 1.3.6.1.4.1.5484.1.10.99.1.0 #policy1_txt = "This is a long policy to summarize" #policy1_url = https://www.example.com/a-policy-to-read #policy2 = 1.3.6.1.4.1.5484.1.10.99.1.1 #policy2_txt = "This is a short policy" #policy2_url = https://www.example.com/another-policy-to-read # The number of additional certificates that may appear in a # path before the anyPolicy is no longer acceptable. #inhibit_anypolicy_skip_certs 1 # Name constraints # DNS #nc_permit_dns = example.com #nc_exclude_dns = test.example.com # EMAIL #nc_permit_email = "nmav@ex.net" # Exclude subdomains of example.com #nc_exclude_email = .example.com # Exclude all e-mail addresses of example.com #nc_exclude_email = example.com # IP #nc_permit_ip = 192.168.0.0/16 #nc_exclude_ip = 192.168.5.0/24 #nc_permit_ip = fc0a:eef2:e7e7:a56e::/64 # Options for proxy certificates #proxy_policy_language = 1.3.6.1.5.5.7.21.1 # Options for generating a CRL # The number of days the next CRL update will be due. # next CRL update will be in 43 days #crl_next_update = 43 # this is the 5th CRL by this CA # The value is in decimal (i.e. 1963) or hex (i.e. 0x07ab). # Comment the field for a time-based number. # Time-based CRL numbers generated in GnuTLS 3.6.3 and later # are significantly larger than those generated in previous # versions. Since CRL numbers need to be monotonic, you need # to specify the CRL number here manually if you intend to # downgrade to an earlier version than 3.6.3 after publishing # the CRL as it is not possible to specify CRL numbers greater # than 2**63-2 using hex notation in those versions. #crl_number = 5 # Specify the update dates more precisely. #crl_this_update_date = "2004-02-29 16:21:42" #crl_next_update_date = "2025-02-29 16:24:41" # The date that the certificates will be made seen as # being revoked. #crl_revocation_date = "2025-02-29 16:24:41"
|
Generating private keys To create an RSA private key, run: $ certtool --generate-privkey --outfile key.pem --rsa To create a DSA or elliptic curves (ECDSA) private key use the above command combined with 'dsa' or 'ecc' options. Generating certificate requests To create a certificate request (needed when the certificate is issued by another party), run: certtool --generate-request --load-privkey key.pem --outfile request.pem If the private key is stored in a smart card you can generate a request by specifying the private key object URL. $ ./certtool --generate-request --load-privkey "pkcs11:..." --load-pubkey "pkcs11:..." --outfile request.pem Generating a self-signed certificate To create a self signed certificate, use the command: $ certtool --generate-privkey --outfile ca-key.pem $ certtool --generate-self-signed --load-privkey ca-key.pem --outfile ca-cert.pem Note that a self-signed certificate usually belongs to a certificate authority, that signs other certificates. Generating a certificate To generate a certificate using the previous request, use the command: $ certtool --generate-certificate --load-request request.pem --outfile cert.pem --load-ca-certificate ca-cert.pem --load-ca-privkey ca-key.pem To generate a certificate using the private key only, use the command: $ certtool --generate-certificate --load-privkey key.pem --outfile cert.pem --load-ca-certificate ca-cert.pem --load-ca-privkey ca-key.pem Certificate information To view the certificate information, use: $ certtool --certificate-info --infile cert.pem Changing the certificate format To convert the certificate from PEM to DER format, use: $ certtool --certificate-info --infile cert.pem --outder --outfile cert.der PKCS #12 structure generation To generate a PKCS #12 structure using the previous key and certificate, use the command: $ certtool --load-certificate cert.pem --load-privkey key.pem --to-p12 --outder --outfile key.p12 Some tools (reportedly web browsers) have problems with that file because it does not contain the CA certificate for the certificate. To work around that problem in the tool, you can use the --load-ca-certificate parameter as follows: $ certtool --load-ca-certificate ca.pem --load-certificate cert.pem --load-privkey key.pem --to-p12 --outder --outfile key.p12 Obtaining Diffie-Hellman parameters To obtain the RFC7919 parameters for Diffie-Hellman key exchange, use the command: $ certtool --get-dh-params --outfile dh.pem --sec-param medium Verifying a certificate To verify a certificate in a file against the system's CA trust store use the following command: $ certtool --verify --infile cert.pem It is also possible to simulate hostname verification with the following options: $ certtool --verify --verify-hostname www.example.com --infile cert.pem Proxy certificate generation Proxy certificate can be used to delegate your credential to a temporary, typically short-lived, certificate. To create one from the previously created certificate, first create a temporary key and then generate a proxy certificate for it, using the commands: $ certtool --generate-privkey > proxy-key.pem $ certtool --generate-proxy --load-ca-privkey key.pem --load-privkey proxy-key.pem --load-certificate cert.pem --outfile proxy-cert.pem Certificate revocation list generation To create an empty Certificate Revocation List (CRL) do: $ certtool --generate-crl --load-ca-privkey x509-ca-key.pem --load-ca-certificate x509-ca.pem To create a CRL that contains some revoked certificates, place the certificates in a file and use --load-certificate as follows: $ certtool --generate-crl --load-ca-privkey x509-ca-key.pem --load-ca-certificate x509-ca.pem --load-certificate revoked-certs.pem To verify a Certificate Revocation List (CRL) do: $ certtool --verify-crl --load-ca-certificate x509-ca.pem < crl.pem EXIT STATUS One of the following exit values will be returned: 0 (EXIT_SUCCESS) Successful program execution. 1 (EXIT_FAILURE) The operation failed or the command syntax was not valid. SEE ALSO p11tool (1), psktool (1), srptool (1) AUTHORS COPYRIGHT Copyright (C) 2020-2023 Free Software Foundation, and others all rights reserved. This program is released under the terms of the GNU General Public License, version 3 or later BUGS Please send bug reports to: bugs@gnutls.org 3.8.4 19 Mar 2024 certtool(1)
|
giftogd2
| null | null | null | null | null |
osql
|
osql is a diagnostic tool provided as part of FreeTDS. It is a Bourne shell script that checks and reports on your configuration files. If everything checks out OK, it invokes isql. osql works only with the isql that comes with unixODBC.
|
osql â utility to test FreeTDS connections and queries
|
osql -S dsn -U username -P password [-I ini_directory]
|
-S dsn the Data Source Name to which to connect, as known to odbc.ini. -U username database login name. -P password database password. -I ini_dir override odbc.ini file location. EXAMPLE If you have an odbc.ini with a section like this: [myDSN] servername = myserver TDS_Version = 5.0 You would invoke osql as: osql -S myDSN [...] FILES odbc.ini freetds.conf NOTES If you can connect with âosql -S servername -U user -P passwdâ,your FreeTDS ODBC installation is working. osql guesses where unixODBC might look for its odbc.ini by examining the binary. This is not always an effective approach. If it doesn't work, you'll receive a report of candidate strings. Kindly pass along the output to help improve the guessing. If osql cannot intuit your odbc.ini directory, you can force the issue with the -I option. However, you're then instructing osql what to test, not where unixODBC will eventually look. Your override is therefore only as good as you are. Look carefully at the error output before overriding. If you have suggestions for ways to make osql more useful as a diagnostic tool, please post them to the FreeTDS mailing list. HISTORY osql first appeared in FreeTDS 0.65. AUTHORS The osql utility was written by James K. Lowden. FreeTDS 1.4.21 April 26, 2012 FreeTDS 1.4.21
| null |
imagetops
| null | null | null | null | null |
lto-dump-13
|
lto-dump is a tool you can use in conjunction with GCC to dump link time optimization object files.
|
lto-dump - Tool for dumping LTO object files
|
lto-dump [-list] [-demangle] [-defined-only] [-print-value] [-name-sort] [-size-sort] [-reverse-sort] [-no-sort] [-symbol=] [-objects] [-type-stats] [-tree-stats] [-gimple-stats] [-dump-level=] [-dump-body=] [-help] lto-dump
|
-list Dumps list of details of functions and variables. -demangle Dump the demangled output. -defined-only Dump only the defined symbols. -print-value Dump initial values of the variables. -name-sort Sort the symbols alphabetically. -size-sort Sort the symbols according to size. -reverse-sort Dump the symbols in reverse order. -no-sort Dump the symbols in order of occurrence. -symbol= Dump the details of specific symbol. -objects Dump the details of LTO objects. -type-stats Dump the statistics of tree types. -tree-stats Dump the statistics of trees. -gimple-stats Dump the statistics of gimple statements. -dump-level= For deciding the optimization level of body. -dump-body= Dump the specific gimple body. -help Display the dump tool help. COPYRIGHT Copyright (c) 2017-2023 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with the Invariant Sections being "GNU General Public License" and "Funding Free Software", the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the gfdl(7) man page. (a) The FSF's Front-Cover Text is: A GNU Manual (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. gcc-13.2.0 2023-07-27 LTO-DUMP(1)
| null |
wheel3.12
| null | null | null | null | null |
pango-view
| null | null | null | null | null |
aomdec
| null | null | null | null | null |
multinit
| null | null | null | null | null |
key_ladder_demo.sh
| null | null | null | null | null |
flutter
| null | null | null | null | null |
gnice
|
Run COMMAND with an adjusted niceness, which affects process scheduling. With no COMMAND, print the current niceness. Niceness values range from -20 (most favorable to the process) to 19 (least favorable to the process). Mandatory arguments to long options are mandatory for short options too. -n, --adjustment=N add integer N to the niceness (default 10) --help display this help and exit --version output version information and exit NOTE: your shell may have its own version of nice, which usually supersedes the version described here. Please refer to your shell's documentation for details about the options it supports. Exit status: 125 if the nice command itself fails 126 if COMMAND is found but cannot be invoked 127 if COMMAND cannot be found - the exit status of COMMAND otherwise AUTHOR Written by David MacKenzie. REPORTING BUGS GNU coreutils online help: <https://www.gnu.org/software/coreutils/> Report any translation bugs to <https://translationproject.org/team/> COPYRIGHT Copyright © 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO nice(2), renice(1) Full documentation <https://www.gnu.org/software/coreutils/nice> or available locally via: info '(coreutils) nice invocation' GNU coreutils 9.3 April 2023 NICE(1)
|
nice - run a program with modified scheduling priority
|
nice [OPTION] [COMMAND [ARG]...]
| null | null |
python-build
| null | null | null | null | null |
gecho
|
Echo the STRING(s) to standard output. -n do not output the trailing newline -e enable interpretation of backslash escapes -E disable interpretation of backslash escapes (default) --help display this help and exit --version output version information and exit If -e is in effect, the following sequences are recognized: \\ backslash \a alert (BEL) \b backspace \c produce no further output \e escape \f form feed \n new line \r carriage return \t horizontal tab \v vertical tab \0NNN byte with octal value NNN (1 to 3 digits) \xHH byte with hexadecimal value HH (1 to 2 digits) NOTE: your shell may have its own version of echo, which usually supersedes the version described here. Please refer to your shell's documentation for details about the options it supports. NOTE: printf(1) is a preferred alternative, which does not have issues outputting option-like strings. AUTHOR Written by Brian Fox and Chet Ramey. REPORTING BUGS GNU coreutils online help: <https://www.gnu.org/software/coreutils/> Report any translation bugs to <https://translationproject.org/team/> COPYRIGHT Copyright © 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO printf(1) Full documentation <https://www.gnu.org/software/coreutils/echo> or available locally via: info '(coreutils) echo invocation' GNU coreutils 9.3 April 2023 ECHO(1)
|
echo - display a line of text
|
echo [SHORT-OPTION]... [STRING]... echo LONG-OPTION
| null | null |
perlthanks
|
This program is designed to help you generate bug reports (and thank- you notes) about perl5 and the modules which ship with it. In most cases, you can just run it interactively from a command line without any special arguments and follow the prompts. If you have found a bug with a non-standard port (one that was not part of the standard distribution), a binary distribution, or a non-core module (such as Tk, DBI, etc), then please see the documentation that came with that distribution to determine the correct place to report bugs. Bug reports should be submitted to the GitHub issue tracker at <https://github.com/Perl/perl5/issues>. The perlbug@perl.org address no longer automatically opens tickets. You can use this tool to compose your report and save it to a file which you can then submit to the issue tracker. In extreme cases, perlbug may not work well enough on your system to guide you through composing a bug report. In those cases, you may be able to use perlbug -d or perl -V to get system configuration information to include in your issue report. When reporting a bug, please run through this checklist: What version of Perl you are running? Type "perl -v" at the command line to find out. Are you running the latest released version of perl? Look at <http://www.perl.org/> to find out. If you are not using the latest released version, please try to replicate your bug on the latest stable release. Note that reports about bugs in old versions of Perl, especially those which indicate you haven't also tested the current stable release of Perl, are likely to receive less attention from the volunteers who build and maintain Perl than reports about bugs in the current release. Are you sure what you have is a bug? A significant number of the bug reports we get turn out to be documented features in Perl. Make sure the issue you've run into isn't intentional by glancing through the documentation that comes with the Perl distribution. Given the sheer volume of Perl documentation, this isn't a trivial undertaking, but if you can point to documentation that suggests the behaviour you're seeing is wrong, your issue is likely to receive more attention. You may want to start with perldoc perltrap for pointers to common traps that new (and experienced) Perl programmers run into. If you're unsure of the meaning of an error message you've run across, perldoc perldiag for an explanation. If the message isn't in perldiag, it probably isn't generated by Perl. You may have luck consulting your operating system documentation instead. If you are on a non-UNIX platform perldoc perlport, as some features may be unimplemented or work differently. You may be able to figure out what's going wrong using the Perl debugger. For information about how to use the debugger perldoc perldebug. Do you have a proper test case? The easier it is to reproduce your bug, the more likely it will be fixed -- if nobody can duplicate your problem, it probably won't be addressed. A good test case has most of these attributes: short, simple code; few dependencies on external commands, modules, or libraries; no platform-dependent code (unless it's a platform-specific bug); clear, simple documentation. A good test case is almost always a good candidate to be included in Perl's test suite. If you have the time, consider writing your test case so that it can be easily included into the standard test suite. Have you included all relevant information? Be sure to include the exact error messages, if any. "Perl gave an error" is not an exact error message. If you get a core dump (or equivalent), you may use a debugger (dbx, gdb, etc) to produce a stack trace to include in the bug report. NOTE: unless your Perl has been compiled with debug info (often -g), the stack trace is likely to be somewhat hard to use because it will most probably contain only the function names and not their arguments. If possible, recompile your Perl with debug info and reproduce the crash and the stack trace. Can you describe the bug in plain English? The easier it is to understand a reproducible bug, the more likely it will be fixed. Any insight you can provide into the problem will help a great deal. In other words, try to analyze the problem (to the extent you can) and report your discoveries. Can you fix the bug yourself? If so, that's great news; bug reports with patches are likely to receive significantly more attention and interest than those without patches. Please submit your patch via the GitHub Pull Request workflow as described in perldoc perlhack. You may also send patches to perl5-porters@perl.org. When sending a patch, create it using "git format-patch" if possible, though a unified diff created with "diff -pu" will do nearly as well. Your patch may be returned with requests for changes, or requests for more detailed explanations about your fix. Here are a few hints for creating high-quality patches: Make sure the patch is not reversed (the first argument to diff is typically the original file, the second argument your changed file). Make sure you test your patch by applying it with "git am" or the "patch" program before you send it on its way. Try to follow the same style as the code you are trying to patch. Make sure your patch really does work ("make test", if the thing you're patching is covered by Perl's test suite). Can you use "perlbug" to submit a thank-you note? Yes, you can do this by either using the "-T" option, or by invoking the program as "perlthanks". Thank-you notes are good. It makes people smile. Please make your issue title informative. "a bug" is not informative. Neither is "perl crashes" nor is "HELP!!!". These don't help. A compact description of what's wrong is fine. Having done your bit, please be prepared to wait, to be told the bug is in your code, or possibly to get no reply at all. The volunteers who maintain Perl are busy folks, so if your problem is an obvious bug in your own code, is difficult to understand or is a duplicate of an existing report, you may not receive a personal reply. If it is important to you that your bug be fixed, do monitor the issue tracker (you will be subscribed to notifications for issues you submit or comment on) and the commit logs to development versions of Perl, and encourage the maintainers with kind words or offers of frosty beverages. (Please do be kind to the maintainers. Harassing or flaming them is likely to have the opposite effect of the one you want.) Feel free to update the ticket about your bug on <https://github.com/Perl/perl5/issues> if a new version of Perl is released and your bug is still present.
|
perlbug - how to submit bug reports on Perl
|
perlbug perlbug [ -v ] [ -a address ] [ -s subject ] [ -b body | -f inputfile ] [ -F outputfile ] [ -r returnaddress ] [ -e editor ] [ -c adminaddress | -C ] [ -S ] [ -t ] [ -d ] [ -h ] [ -T ] perlbug [ -v ] [ -r returnaddress ] [ -ok | -okay | -nok | -nokay ] perlthanks
|
-a Address to send the report to instead of saving to a file. -b Body of the report. If not included on the command line, or in a file with -f, you will get a chance to edit the report. -C Don't send copy to administrator when sending report by mail. -c Address to send copy of report to when sending report by mail. Defaults to the address of the local perl administrator (recorded when perl was built). -d Data mode (the default if you redirect or pipe output). This prints out your configuration data, without saving or mailing anything. You can use this with -v to get more complete data. -e Editor to use. -f File containing the body of the report. Use this to quickly send a prepared report. -F File to output the results to. Defaults to perlbug.rep. -h Prints a brief summary of the options. -ok Report successful build on this system to perl porters. Forces -S and -C. Forces and supplies values for -s and -b. Only prompts for a return address if it cannot guess it (for use with make). Honors return address specified with -r. You can use this with -v to get more complete data. Only makes a report if this system is less than 60 days old. -okay As -ok except it will report on older systems. -nok Report unsuccessful build on this system. Forces -C. Forces and supplies a value for -s, then requires you to edit the report and say what went wrong. Alternatively, a prepared report may be supplied using -f. Only prompts for a return address if it cannot guess it (for use with make). Honors return address specified with -r. You can use this with -v to get more complete data. Only makes a report if this system is less than 60 days old. -nokay As -nok except it will report on older systems. -p The names of one or more patch files or other text attachments to be included with the report. Multiple files must be separated with commas. -r Your return address. The program will ask you to confirm its default if you don't use this option. -S Save or send the report without asking for confirmation. -s Subject to include with the report. You will be prompted if you don't supply one on the command line. -t Test mode. Makes it possible to command perlbug from a pipe or file, for testing purposes. -T Send a thank-you note instead of a bug report. -v Include verbose configuration data in the report. AUTHORS Kenneth Albanowski (<kjahds@kjahds.com>), subsequently doctored by Gurusamy Sarathy (<gsar@activestate.com>), Tom Christiansen (<tchrist@perl.com>), Nathan Torkington (<gnat@frii.com>), Charles F. Randall (<cfr@pobox.com>), Mike Guy (<mjtg@cam.ac.uk>), Dominic Dunlop (<domo@computer.org>), Hugo van der Sanden (<hv@crypt.org>), Jarkko Hietaniemi (<jhi@iki.fi>), Chris Nandor (<pudge@pobox.com>), Jon Orwant (<orwant@media.mit.edu>, Richard Foley (<richard.foley@rfi.net>), Jesse Vincent (<jesse@bestpractical.com>), and Craig A. Berry (<craigberry@mac.com>). SEE ALSO perl(1), perldebug(1), perldiag(1), perlport(1), perltrap(1), diff(1), patch(1), dbx(1), gdb(1) BUGS None known (guess what must have been used to report them?) perl v5.38.2 2023-11-28 PERLBUG(1)
| null |
perror
|
perror displays the error message for MySQL or operating system error codes. Invoke perror like this: perror [options] errorcode ... perror attempts to be flexible in understanding its arguments. For example, for the ER_WRONG_VALUE_FOR_VAR error, perror understands any of these arguments: 1231, 001231, MY-1231, or MY-001231, or ER_WRONG_VALUE_FOR_VAR. $> perror 1231 MySQL error code MY-001231 (ER_WRONG_VALUE_FOR_VAR): Variable '%-.64s' can't be set to the value of '%-.200s' If an error number is in the range where MySQL and operating system errors overlap, perror displays both error messages: $> perror 1 13 OS error code 1: Operation not permitted MySQL error code MY-000001: Can't create/write to file '%s' (OS errno %d - %s) OS error code 13: Permission denied MySQL error code MY-000013: Can't get stat of '%s' (OS errno %d - %s) To obtain the error message for a MySQL Cluster error code, use the ndb_perror utility. The meaning of system error messages may be dependent on your operating system. A given error code may mean different things on different operating systems. perror supports the following options. ⢠--help, --info, -I, -? Display a help message and exit. ⢠--ndb Print the error message for a MySQL Cluster error code. This option was removed in MySQL 8.0.13. Use the ndb_perror utility instead. ⢠--silent, -s Silent mode. Print only the error message. ⢠--verbose, -v Verbose mode. Print error code and message. This is the default behavior. ⢠--version, -V Display version information and exit. COPYRIGHT Copyright © 1997, 2023, Oracle and/or its affiliates. This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see http://www.gnu.org/licenses/. SEE ALSO For more information, please refer to the MySQL Reference Manual, which may already be installed locally and which is also available online at http://dev.mysql.com/doc/. AUTHOR Oracle Corporation (http://dev.mysql.com/). MySQL 8.3 11/23/2023 PERROR(1)
|
perror - display MySQL error message information
|
perror [options] errorcode ...
| null | null |
gdu
|
Summarize device usage of the set of FILEs, recursively for directories. Mandatory arguments to long options are mandatory for short options too. -0, --null end each output line with NUL, not newline -a, --all write counts for all files, not just directories --apparent-size print apparent sizes rather than device usage; although the apparent size is usually smaller, it may be larger due to holes in ('sparse') files, internal fragmentation, indirect blocks, and the like -B, --block-size=SIZE scale sizes by SIZE before printing them; e.g., '-BM' prints sizes in units of 1,048,576 bytes; see SIZE format below -b, --bytes equivalent to '--apparent-size --block-size=1' -c, --total produce a grand total -D, --dereference-args dereference only symlinks that are listed on the command line -d, --max-depth=N print the total for a directory (or file, with --all) only if it is N or fewer levels below the command line argument; --max-depth=0 is the same as --summarize --files0-from=F summarize device usage of the NUL-terminated file names specified in file F; if F is -, then read names from standard input -H equivalent to --dereference-args (-D) -h, --human-readable print sizes in human readable format (e.g., 1K 234M 2G) --inodes list inode usage information instead of block usage -k like --block-size=1K -L, --dereference dereference all symbolic links -l, --count-links count sizes many times if hard linked -m like --block-size=1M -P, --no-dereference don't follow any symbolic links (this is the default) -S, --separate-dirs for directories do not include size of subdirectories --si like -h, but use powers of 1000 not 1024 -s, --summarize display only a total for each argument -t, --threshold=SIZE exclude entries smaller than SIZE if positive, or entries greater than SIZE if negative --time show time of the last modification of any file in the directory, or any of its subdirectories --time=WORD show time as WORD instead of modification time: atime, access, use, ctime or status --time-style=STYLE show times using STYLE, which can be: full-iso, long-iso, iso, or +FORMAT; FORMAT is interpreted like in 'date' -X, --exclude-from=FILE exclude files that match any pattern in FILE --exclude=PATTERN exclude files that match PATTERN -x, --one-file-system skip directories on different file systems --help display this help and exit --version output version information and exit Display values are in units of the first available SIZE from --block-size, and the DU_BLOCK_SIZE, BLOCK_SIZE and BLOCKSIZE environment variables. Otherwise, units default to 1024 bytes (or 512 if POSIXLY_CORRECT is set). The SIZE argument is an integer and optional unit (example: 10K is 10*1024). Units are K,M,G,T,P,E,Z,Y,R,Q (powers of 1024) or KB,MB,... (powers of 1000). Binary prefixes can be used, too: KiB=K, MiB=M, and so on. PATTERNS PATTERN is a shell pattern (not a regular expression). The pattern ? matches any one character, whereas * matches any string (composed of zero, one or multiple characters). For example, *.o will match any files whose names end in .o. Therefore, the command du --exclude='*.o' will skip all files and subdirectories ending in .o (including the file .o itself). AUTHOR Written by Torbjorn Granlund, David MacKenzie, Paul Eggert, and Jim Meyering. REPORTING BUGS GNU coreutils online help: <https://www.gnu.org/software/coreutils/> Report any translation bugs to <https://translationproject.org/team/> COPYRIGHT Copyright © 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO Full documentation <https://www.gnu.org/software/coreutils/du> or available locally via: info '(coreutils) du invocation' GNU coreutils 9.3 April 2023 DU(1)
|
du - estimate file space usage
|
du [OPTION]... [FILE]... du [OPTION]... --files0-from=F
| null | null |
futurize
| null | null | null | null | null |
gb2sum
|
Print or check BLAKE2b (512-bit) checksums. With no FILE, or when FILE is -, read standard input. Mandatory arguments to long options are mandatory for short options too. -b, --binary read in binary mode -c, --check read checksums from the FILEs and check them -l, --length=BITS digest length in bits; must not exceed the max for the blake2 algorithm and must be a multiple of 8 --tag create a BSD-style checksum -t, --text read in text mode (default) -z, --zero end each output line with NUL, not newline, and disable file name escaping The following five options are useful only when verifying checksums: --ignore-missing don't fail or report status for missing files --quiet don't print OK for each successfully verified file --status don't output anything, status code shows success --strict exit non-zero for improperly formatted checksum lines -w, --warn warn about improperly formatted checksum lines --help display this help and exit --version output version information and exit The sums are computed as described in RFC 7693. When checking, the input should be a former output of this program. The default mode is to print a line with: checksum, a space, a character indicating input mode ('*' for binary, ' ' for text or where binary is insignificant), and name for each FILE. Note: There is no difference between binary mode and text mode on GNU systems. AUTHOR Written by Padraig Brady and Samuel Neves. REPORTING BUGS GNU coreutils online help: <https://www.gnu.org/software/coreutils/> Report any translation bugs to <https://translationproject.org/team/> COPYRIGHT Copyright © 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO cksum(1) Full documentation <https://www.gnu.org/software/coreutils/b2sum> or available locally via: info '(coreutils) b2sum invocation' GNU coreutils 9.3 April 2023 B2SUM(1)
|
b2sum - compute and check BLAKE2 message digest
|
b2sum [OPTION]... [FILE]...
| null | null |
env_parallel.sh
| null | null | null | null | null |
fipstest
| null | null | null | null | null |
zmqshell.py
| null | null | null | null | null |
py7zr
| null | null | null | null | null |
httpx
| null | null | null | null | null |
ssl_fork_server
| null | null | null | null | null |
libassuan-config
| null | null | null | null | null |
pango-list
| null | null | null | null | null |
vterm-dump
| null | null | null | null | null |
hb-ot-shape-closure
| null | null | null | null | null |
exrmanifest
| null | null | null | null | null |
gtouch
|
Update the access and modification times of each FILE to the current time. A FILE argument that does not exist is created empty, unless -c or -h is supplied. A FILE argument string of - is handled specially and causes touch to change the times of the file associated with standard output. Mandatory arguments to long options are mandatory for short options too. -a change only the access time -c, --no-create do not create any files -d, --date=STRING parse STRING and use it instead of current time -f (ignored) -h, --no-dereference affect each symbolic link instead of any referenced file (useful only on systems that can change the timestamps of a symlink) -m change only the modification time -r, --reference=FILE use this file's times instead of current time -t STAMP use [[CC]YY]MMDDhhmm[.ss] instead of current time --time=WORD change the specified time: WORD is access, atime, or use: equivalent to -a WORD is modify or mtime: equivalent to -m --help display this help and exit --version output version information and exit Note that the -d and -t options accept different time-date formats. DATE STRING The --date=STRING is a mostly free format human readable date string such as "Sun, 29 Feb 2004 16:21:42 -0800" or "2004-02-29 16:21:42" or even "next Thursday". A date string may contain items indicating calendar date, time of day, time zone, day of week, relative time, relative date, and numbers. An empty string indicates the beginning of the day. The date string format is more complex than is easily documented here but is fully described in the info documentation. AUTHOR Written by Paul Rubin, Arnold Robbins, Jim Kingdon, David MacKenzie, and Randy Smith. REPORTING BUGS GNU coreutils online help: <https://www.gnu.org/software/coreutils/> Report any translation bugs to <https://translationproject.org/team/> COPYRIGHT Copyright © 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO Full documentation <https://www.gnu.org/software/coreutils/touch> or available locally via: info '(coreutils) touch invocation' GNU coreutils 9.3 April 2023 TOUCH(1)
|
touch - change file timestamps
|
touch [OPTION]... FILE...
| null | null |
gpgsm
|
gpgsm is a tool similar to gpg to provide digital encryption and signing services on X.509 certificates and the CMS protocol. It is mainly used as a backend for S/MIME mail processing. gpgsm includes a full featured certificate management and complies with all rules defined for the German Sphinx project. COMMANDS Commands are not distinguished from options except for the fact that only one command is allowed. Commands not specific to the function --version Print the program version and licensing information. Note that you cannot abbreviate this command. --help, -h Print a usage message summarizing the most useful command-line options. Note that you cannot abbreviate this command. --warranty Print warranty information. Note that you cannot abbreviate this command. --dump-options Print a list of all available options and commands. Note that you cannot abbreviate this command. Commands to select the type of operation --encrypt Perform an encryption. The keys the data is encrypted to must be set using the option --recipient. --decrypt Perform a decryption; the type of input is automatically determined. It may either be in binary form or PEM encoded; automatic determination of base-64 encoding is not done. --sign Create a digital signature. The key used is either the fist one found in the keybox or those set with the --local-user option. --verify Check a signature file for validity. Depending on the arguments a detached signature may also be checked. --server Run in server mode and wait for commands on the stdin. --call-dirmngr command [args] Behave as a Dirmngr client issuing the request command with the optional list of args. The output of the Dirmngr is printed stdout. Please note that file names given as arguments should have an absolute file name (i.e. commencing with /) because they are passed verbatim to the Dirmngr and the working directory of the Dirmngr might not be the same as the one of this client. Currently it is not possible to pass data via stdin to the Dirmngr. command should not contain spaces. This is command is required for certain maintaining tasks of the dirmngr where a dirmngr must be able to call back to gpgsm. See the Dirmngr manual for details. --call-protect-tool arguments Certain maintenance operations are done by an external program call gpg-protect-tool; this is usually not installed in a directory listed in the PATH variable. This command provides a simple wrapper to access this tool. arguments are passed verbatim to this command; use â--helpâ to get a list of supported operations. How to manage the certificates and keys --generate-key --gen-key This command allows the creation of a certificate signing request or a self-signed certificate. It is commonly used along with the --output option to save the created CSR or certificate into a file. If used with the --batch a parameter file is used to create the CSR or certificate and it is further possible to create non-self-signed certificates. --list-keys -k List all available certificates stored in the local key database. Note that the displayed data might be reformatted for better human readability and illegal characters are replaced by safe substitutes. --list-secret-keys -K List all available certificates for which a corresponding a secret key is available. --list-external-keys pattern List certificates matching pattern using an external server. This utilizes the dirmngr service. --list-chain Same as --list-keys but also prints all keys making up the chain. --dump-cert --dump-keys List all available certificates stored in the local key database using a format useful mainly for debugging. --dump-chain Same as --dump-keys but also prints all keys making up the chain. --dump-secret-keys List all available certificates for which a corresponding a secret key is available using a format useful mainly for debugging. --dump-external-keys pattern List certificates matching pattern using an external server. This utilizes the dirmngr service. It uses a format useful mainly for debugging. --show-certs [files] This command takes certificate files as input and prints information about them in the same format as --dump-cert does. Each file may either contain a single binary certificate or several PEM encoded certificates. If no files are given, the input is taken from stdin. Please note that the listing format may be changed in future releases and that the option --with-colons has currently no effect. --keydb-clear-some-cert-flags This is a debugging aid to reset certain flags in the key database which are used to cache certain certificate statuses. It is especially useful if a bad CRL or a weird running OCSP responder did accidentally revoke certificate. There is no security issue with this command because gpgsm always make sure that the validity of a certificate is checked right before it is used. --delete-keys pattern Delete the keys matching pattern. Note that there is no command to delete the secret part of the key directly. In case you need to do this, you should run the command gpgsm --dump-secret-keys KEYID before you delete the key, copy the string of hex-digits in the ``keygrip'' line and delete the file consisting of these hex-digits and the suffix .key from the âprivate-keys-v1.dâ directory below our GnuPG home directory (usually â~/.gnupgâ). --export [pattern] Export all certificates stored in the Keybox or those specified by the optional pattern. Those pattern consist of a list of user ids (see: [how-to-specify-a-user-id]). When used along with the --armor option a few informational lines are prepended before each block. There is one limitation: As there is no commonly agreed upon way to pack more than one certificate into an ASN.1 structure, the binary export (i.e. without using armor) works only for the export of one certificate. Thus it is required to specify a pattern which yields exactly one certificate. Ephemeral certificate are only exported if all pattern are given as fingerprints or keygrips. --export-secret-key-p12 key-id Export the private key and the certificate identified by key-id using the PKCS#12 format. When used with the --armor option a few informational lines are prepended to the output. Note, that the PKCS#12 format is not very secure and proper transport security should be used to convey the exported key. (See: [option --p12-charset].) --export-secret-key-p8 key-id --export-secret-key-raw key-id Export the private key of the certificate identified by key-id with any encryption stripped. The ...-raw command exports in PKCS#1 format; the ...-p8 command exports in PKCS#8 format. When used with the --armor option a few informational lines are prepended to the output. These commands are useful to prepare a key for use on a TLS server. --import [files] Import the certificates from the PEM or binary encoded files as well as from signed-only messages. This command may also be used to import a secret key from a PKCS#12 file. --learn-card Read information about the private keys from the smartcard and import the certificates from there. This command utilizes the gpg-agent and in turn the scdaemon. --change-passphrase user_id --passwd user_id Change the passphrase of the private key belonging to the certificate specified as user_id. Note, that changing the passphrase/PIN of a smartcard is not yet supported.
|
gpgsm - CMS encryption and signing tool
|
gpgsm [--homedir dir] [--options file] [options] command [args]
|
GPGSM features a bunch of options to control the exact behaviour and to change the default configuration. How to change the configuration These options are used to change the configuration and are usually found in the option file. --options file Reads configuration from file instead of from the default per- user configuration file. The default configuration file is named âgpgsm.confâ and expected in the â.gnupgâ directory directly below the home directory of the user. --homedir dir Set the name of the home directory to dir. If this option is not used, the home directory defaults to â~/.gnupgâ. It is only recognized when given on the command line. It also overrides any home directory stated through the environment variable âGNUPGHOMEâ or (on Windows systems) by means of the Registry entry HKCU\Software\GNU\GnuPG:HomeDir. On Windows systems it is possible to install GnuPG as a portable application. In this case only this command line option is considered, all other ways to set a home directory are ignored. -v --verbose Outputs additional information while running. You can increase the verbosity by giving several verbose commands to gpgsm, such as â-vvâ. --keyserver string This is a deprecated option. It was used to add an LDAP server to use for X.509 certificate and CRL lookup. The alias --ldapserver existed from version 2.2.28 to 2.2.33 and 2.3.2 to 2.3.4 but is now entirely ignored. LDAP servers must be given in the configuration for dirmngr. --policy-file filename Change the default name of the policy file to filename. The default name is âpolicies.txtâ. --agent-program file Specify an agent program to be used for secret key operations. The default value is determined by running the command gpgconf. Note that the pipe symbol (|) is used for a regression test suite hack and may thus not be used in the file name. --dirmngr-program file Specify a dirmngr program to be used for CRL checks. The default value is â/opt/homebrew/Cellar/gnupg/2.4.5/bin/dirmngrâ. --prefer-system-dirmngr This option is obsolete and ignored. --disable-dirmngr Entirely disable the use of the Dirmngr. --no-autostart Do not start the gpg-agent or the dirmngr if it has not yet been started and its service is required. This option is mostly useful on machines where the connection to gpg-agent has been redirected to another machines. If dirmngr is required on the remote machine, it may be started manually using gpgconf --launch dirmngr. --no-secmem-warning Do not print a warning when the so called "secure memory" cannot be used. --log-file file When running in server mode, append all logging output to file. Use âsocket://â to log to socket. --log-time Prefix all log output with a timestamp even if no log file is used. Certificate related options --enable-policy-checks --disable-policy-checks By default policy checks are enabled. These options may be used to change it. --enable-crl-checks --disable-crl-checks By default the CRL checks are enabled and the DirMngr is used to check for revoked certificates. The disable option is most useful with an off-line network connection to suppress this check and also to avoid that new certificates introduce a web bug by including a certificate specific CRL DP. The disable option also disables an issuer certificate lookup via the authorityInfoAccess property of the certificate; the --enable-issuer-key-retrieve can be used to make use of that property anyway. --enable-trusted-cert-crl-check --disable-trusted-cert-crl-check By default the CRL for trusted root certificates are checked like for any other certificates. This allows a CA to revoke its own certificates voluntary without the need of putting all ever issued certificates into a CRL. The disable option may be used to switch this extra check off. Due to the caching done by the Dirmngr, there will not be any noticeable performance gain. Note, that this also disables possible OCSP checks for trusted root certificates. A more specific way of disabling this check is by adding the ``relax'' keyword to the root CA line of the âtrustlist.txtâ --force-crl-refresh Tell the dirmngr to reload the CRL for each request. For better performance, the dirmngr will actually optimize this by suppressing the loading for short time intervals (e.g. 30 minutes). This option is useful to make sure that a fresh CRL is available for certificates hold in the keybox. The suggested way of doing this is by using it along with the option --with-validation for a key listing command. This option should not be used in a configuration file. --enable-issuer-based-crl-check Run a CRL check even for certificates which do not have any CRL distribution point. This requires that a suitable LDAP server has been configured in Dirmngr and that the CRL can be found using the issuer. This option reverts to what GnuPG did up to version 2.2.20. This option is in general not useful. --enable-ocsp --disable-ocsp By default OCSP checks are disabled. The enable option may be used to enable OCSP checks via Dirmngr. If CRL checks are also enabled, CRLs will be used as a fallback if for some reason an OCSP request will not succeed. Note, that you have to allow OCSP requests in Dirmngr's configuration too (option --allow-ocsp) and configure Dirmngr properly. If you do not do so you will get the error code âNot supportedâ. --auto-issuer-key-retrieve If a required certificate is missing while validating the chain of certificates, try to load that certificate from an external location. This usually means that Dirmngr is employed to search for the certificate. Note that this option makes a "web bug" like behavior possible. LDAP server operators can see which keys you request, so by sending you a message signed by a brand new key (which you naturally will not have on your local keybox), the operator can tell both your IP address and the time when you verified the signature. Note that if CRL checking is not disabled issuer certificates are retrieved in any case using the caIssuers authorityInfoAccess method. --validation-model name This option changes the default validation model. The only possible values are "shell" (which is the default), "chain" which forces the use of the chain model and "steed" for a new simplified model. The chain model is also used if an option in the âtrustlist.txtâ or an attribute of the certificate requests it. However the standard model (shell) is in that case always tried first. --ignore-cert-extension oid Add oid to the list of ignored certificate extensions. The oid is expected to be in dotted decimal form, like 2.5.29.3. This option may be used more than once. Critical flagged certificate extensions matching one of the OIDs in the list are treated as if they are actually handled and thus the certificate will not be rejected due to an unknown critical extension. Use this option with care because extensions are usually flagged as critical for a reason. Input and Output --armor -a Create PEM encoded output. Default is binary output. --base64 Create Base-64 encoded output; i.e. PEM without the header lines. --assume-armor Assume the input data is PEM encoded. Default is to autodetect the encoding but this is may fail. --assume-base64 Assume the input data is plain base-64 encoded. --assume-binary Assume the input data is binary encoded. --input-size-hint n This option can be used to tell GPGSM the size of the input data in bytes. n must be a positive base-10 number. It is used by the --status-fd line ``PROGRESS'' to provide a value for ``total'' if that is not available by other means. --p12-charset name gpgsm uses the UTF-8 encoding when encoding passphrases for PKCS#12 files. This option may be used to force the passphrase to be encoded in the specified encoding name. This is useful if the application used to import the key uses a different encoding and thus will not be able to import a file generated by gpgsm. Commonly used values for name are Latin1 and CP850. Note that gpgsm itself automagically imports any file with a passphrase encoded to the most commonly used encodings. --default-key user_id Use user_id as the standard key for signing. This key is used if no other key has been defined as a signing key. Note, that the first --local-users option also sets this key if it has not yet been set; however --default-key always overrides this. --local-user user_id -u user_id Set the user(s) to be used for signing. The default is the first secret key found in the database. --recipient name -r Encrypt to the user id name. There are several ways a user id may be given (see: [how-to-specify-a-user-id]). --output file -o file Write output to file. The default is to write it to stdout. --with-key-data Displays extra information with the --list-keys commands. Especially a line tagged grp is printed which tells you the keygrip of a key. This string is for example used as the file name of the secret key. Implies --with-colons. --with-validation When doing a key listing, do a full validation check for each key and print the result. This is usually a slow operation because it requires a CRL lookup and other operations. When used along with --import, a validation of the certificate to import is done and only imported if it succeeds the test. Note that this does not affect an already available certificate in the DB. This option is therefore useful to simply verify a certificate. --with-md5-fingerprint For standard key listings, also print the MD5 fingerprint of the certificate. --with-keygrip Include the keygrip in standard key listings. Note that the keygrip is always listed in --with-colons mode. --with-secret Include info about the presence of a secret key in public key listings done with --with-colons. --no-pretty-dn By default gpgsm prints distinguished names (DNs) like the Issuer or Subject in a more readable format (e.g. using a well defined order of the parts). However, this format can't be used as input strings. This option reverts printing to standard RFC-2253 format and thus avoids the need to use --dump-cert or --with-colons to get the ``real'' name. How to change how the CMS is created --include-certs n Using n of -2 includes all certificate except for the root cert, -1 includes all certs, 0 does not include any certs, 1 includes only the signers cert and all other positive values include up to n certificates starting with the signer cert. The default is -2. --cipher-algo oid Use the cipher algorithm with the ASN.1 object identifier oid for encryption. For convenience the strings 3DES, AES and AES256 may be used instead of their OIDs. The default is AES (2.16.840.1.101.3.4.1.2). --digest-algo name Use name as the message digest algorithm. Usually this algorithm is deduced from the respective signing certificate. This option forces the use of the given algorithm and may lead to severe interoperability problems. Doing things one usually do not want to do --chuid uid Change the current user to uid which may either be a number or a name. This can be used from the root account to run gpgsm for another user. If uid is not the current UID a standard PATH is set and the envvar GNUPGHOME is unset. To override the latter the option --homedir can be used. This option has only an effect when used on the command line. This option has currently no effect at all on Windows. --extra-digest-algo name Sometimes signatures are broken in that they announce a different digest algorithm than actually used. gpgsm uses a one-pass data processing model and thus needs to rely on the announced digest algorithms to properly hash the data. As a workaround this option may be used to tell gpgsm to also hash the data using the algorithm name; this slows processing down a little bit but allows verification of such broken signatures. If gpgsm prints an error like ``digest algo 8 has not been enabled'' you may want to try this option, with âSHA256â for name. --compliance string Set the compliance mode. Valid values are shown when using "help" for string. --min-rsa-length n This option adjusts the compliance mode "de-vs" for stricter key size requirements. For example, a value of 3000 turns rsa2048 and dsa2048 keys into non-VS-NfD compliant keys. --require-compliance To check that data has been encrypted according to the rules of the current compliance mode, a gpgsm user needs to evaluate the status lines. This is allows frontends to handle compliance check in a more flexible way. However, for scripted use the required evaluation of the status-line requires quite some effort; this option can be used instead to make sure that the gpgsm process exits with a failure if the compliance rules are not fulfilled. Note that this option has currently an effect only in "de-vs" mode. --always-trust Force encryption to the specified certificates without any validation of the certificate chain. The only requirement is that the certificate is capable of encryption. Note that this option is ineffective if --require-compliance is used. --ignore-cert-with-oid oid Add oid to the list of OIDs to be checked while reading certificates from smartcards. The oid is expected to be in dotted decimal form, like 2.5.29.3. This option may be used more than once. As of now certificates with an extended key usage matching one of those OIDs are ignored during a --learn-card operation and not imported. This option can help to keep the local key database clear of unneeded certificates stored on smartcards. --faked-system-time epoch This option is only useful for testing; it sets the system time back or forth to epoch which is the number of seconds elapsed since the year 1970. Alternatively epoch may be given as a full ISO time string (e.g. "20070924T154812"). --with-ephemeral-keys Include ephemeral flagged keys in the output of key listings. Note that they are included anyway if the key specification for a listing is given as fingerprint or keygrip. --compatibility-flags flags Set compatibility flags to work around problems due to non- compliant certificates or data. The flags are given as a comma separated list of flag names and are OR-ed together. The special flag "none" clears the list and allows one to start over with an empty list. To get a list of available flags the sole word "help" can be used. --debug-level level Select the debug level for investigating problems. level may be a numeric value or by a keyword: none No debugging at all. A value of less than 1 may be used instead of the keyword. basic Some basic debug messages. A value between 1 and 2 may be used instead of the keyword. advanced More verbose debug messages. A value between 3 and 5 may be used instead of the keyword. expert Even more detailed messages. A value between 6 and 8 may be used instead of the keyword. guru All of the debug messages you can get. A value greater than 8 may be used instead of the keyword. The creation of hash tracing files is only enabled if the keyword is used. How these messages are mapped to the actual debugging flags is not specified and may change with newer releases of this program. They are however carefully selected to best aid in debugging. --debug flags Set debug flags. All flags are or-ed and flags may be given in C syntax (e.g. 0x0042) or as a comma separated list of flag names. To get a list of all supported flags the single word "help" can be used. This option is only useful for debugging and the behavior may change at any time without notice. Note, that all flags set using this option may get overridden by --debug-level. --debug-all Same as --debug=0xffffffff --debug-allow-core-dump Usually gpgsm tries to avoid dumping core by well written code and by disabling core dumps for security reasons. However, bugs are pretty durable beasts and to squash them it is sometimes useful to have a core dump. This option enables core dumps unless the Bad Thing happened before the option parsing. --debug-no-chain-validation This is actually not a debugging option but only useful as such. It lets gpgsm bypass all certificate chain validation checks. --debug-ignore-expiration This is actually not a debugging option but only useful as such. It lets gpgsm ignore all notAfter dates, this is used by the regression tests. --passphrase-fd n Read the passphrase from file descriptor n. Only the first line will be read from file descriptor n. If you use 0 for n, the passphrase will be read from STDIN. This can only be used if only one passphrase is supplied. Note that this passphrase is only used if the option --batch has also been given. --pinentry-mode mode Set the pinentry mode to mode. Allowed values for mode are: default Use the default of the agent, which is ask. ask Force the use of the Pinentry. cancel Emulate use of Pinentry's cancel button. error Return a Pinentry error (``No Pinentry''). loopback Redirect Pinentry queries to the caller. Note that in contrast to Pinentry the user is not prompted again if he enters a bad password. --request-origin origin Tell gpgsm to assume that the operation ultimately originated at origin. Depending on the origin certain restrictions are applied and the Pinentry may include an extra note on the origin. Supported values for origin are: local which is the default, remote to indicate a remote origin or browser for an operation requested by a web browser. --no-common-certs-import Suppress the import of common certificates on keybox creation. All the long options may also be given in the configuration file after stripping off the two leading dashes. HOW TO SPECIFY A USER ID There are different ways to specify a user ID to GnuPG. Some of them are only valid for gpg others are only good for gpgsm. Here is the entire list of ways to specify a key: By key Id. This format is deduced from the length of the string and its content or 0x prefix. The key Id of an X.509 certificate are the low 64 bits of its SHA-1 fingerprint. The use of key Ids is just a shortcut, for all automated processing the fingerprint should be used. When using gpg an exclamation mark (!) may be appended to force using the specified primary or secondary key and not to try and calculate which primary or secondary key to use. The last four lines of the example give the key ID in their long form as internally used by the OpenPGP protocol. You can see the long key ID using the option --with-colons. 234567C4 0F34E556E 01347A56A 0xAB123456 234AABBCC34567C4 0F323456784E56EAB 01AB3FED1347A5612 0x234AABBCC34567C4 By fingerprint. This format is deduced from the length of the string and its content or the 0x prefix. Note, that only the 20 byte version fingerprint is available with gpgsm (i.e. the SHA-1 hash of the certificate). When using gpg an exclamation mark (!) may be appended to force using the specified primary or secondary key and not to try and calculate which primary or secondary key to use. The best way to specify a key Id is by using the fingerprint. This avoids any ambiguities in case that there are duplicated key IDs. 1234343434343434C434343434343434 123434343434343C3434343434343734349A3434 0E12343434343434343434EAB3484343434343434 0xE12343434343434343434EAB3484343434343434 gpgsm also accepts colons between each pair of hexadecimal digits because this is the de-facto standard on how to present X.509 fingerprints. gpg also allows the use of the space separated SHA-1 fingerprint as printed by the key listing commands. By exact match on OpenPGP user ID. This is denoted by a leading equal sign. It does not make sense for X.509 certificates. =Heinrich Heine <heinrichh@uni-duesseldorf.de> By exact match on an email address. This is indicated by enclosing the email address in the usual way with left and right angles. <heinrichh@uni-duesseldorf.de> By partial match on an email address. This is indicated by prefixing the search string with an @. This uses a substring search but considers only the mail address (i.e. inside the angle brackets). @heinrichh By exact match on the subject's DN. This is indicated by a leading slash, directly followed by the RFC-2253 encoded DN of the subject. Note that you can't use the string printed by gpgsm --list-keys because that one has been reordered and modified for better readability; use --with-colons to print the raw (but standard escaped) RFC-2253 string. /CN=Heinrich Heine,O=Poets,L=Paris,C=FR By exact match on the issuer's DN. This is indicated by a leading hash mark, directly followed by a slash and then directly followed by the RFC-2253 encoded DN of the issuer. This should return the Root cert of the issuer. See note above. #/CN=Root Cert,O=Poets,L=Paris,C=FR By exact match on serial number and issuer's DN. This is indicated by a hash mark, followed by the hexadecimal representation of the serial number, then followed by a slash and the RFC-2253 encoded DN of the issuer. See note above. #4F03/CN=Root Cert,O=Poets,L=Paris,C=FR By keygrip. This is indicated by an ampersand followed by the 40 hex digits of a keygrip. gpgsm prints the keygrip when using the command --dump-cert. &D75F22C3F86E355877348498CDC92BD21010A480 By substring match. This is the default mode but applications may want to explicitly indicate this by putting the asterisk in front. Match is not case sensitive. Heine *Heine . and + prefixes These prefixes are reserved for looking up mails anchored at the end and for a word search mode. They are not yet implemented and using them is undefined. Please note that we have reused the hash mark identifier which was used in old GnuPG versions to indicate the so called local- id. It is not anymore used and there should be no conflict when used with X.509 stuff. Using the RFC-2253 format of DNs has the drawback that it is not possible to map them back to the original encoding, however we don't have to do this because our key database stores this encoding as meta data.
|
$ gpgsm -er goo@bar.net <plaintext >ciphertext FILES There are a few configuration files to control certain aspects of gpgsm's operation. Unless noted, they are expected in the current home directory (see: [option --homedir]). gpgsm.conf This is the standard configuration file read by gpgsm on startup. It may contain any valid long option; the leading two dashes may not be entered and the option may not be abbreviated. This default name may be changed on the command line (see: [gpgsm-option --options]). You should backup this file. common.conf This is an optional configuration file read by gpgsm on startup. It may contain options pertaining to all components of GnuPG. Its current main use is for the "use-keyboxd" option. policies.txt This is a list of allowed CA policies. This file should list the object identifiers of the policies line by line. Empty lines and lines starting with a hash mark are ignored. Policies missing in this file and not marked as critical in the certificate will print only a warning; certificates with policies marked as critical and not listed in this file will fail the signature verification. You should backup this file. For example, to allow only the policy 2.289.9.9, the file should look like this: # Allowed policies 2.289.9.9 qualified.txt This is the list of root certificates used for qualified certificates. They are defined as certificates capable of creating legally binding signatures in the same way as handwritten signatures are. Comments start with a hash mark and empty lines are ignored. Lines do have a length limit but this is not a serious limitation as the format of the entries is fixed and checked by gpgsm: A non-comment line starts with optional whitespace, followed by exactly 40 hex characters, white space and a lowercased 2 letter country code. Additional data delimited with by a white space is current ignored but might late be used for other purposes. Note that even if a certificate is listed in this file, this does not mean that the certificate is trusted; in general the certificates listed in this file need to be listed also in âtrustlist.txtâ. This is a global file an installed in the sysconf directory (e.g. â/opt/homebrew/etc/gnupg/qualified.txtâ). Every time gpgsm uses a certificate for signing or verification this file will be consulted to check whether the certificate under question has ultimately been issued by one of these CAs. If this is the case the user will be informed that the verified signature represents a legally binding (``qualified'') signature. When creating a signature using such a certificate an extra prompt will be issued to let the user confirm that such a legally binding signature shall really be created. Because this software has not yet been approved for use with such certificates, appropriate notices will be shown to indicate this fact. help.txt This is plain text file with a few help entries used with pinentry as well as a large list of help items for gpg and gpgsm. The standard file has English help texts; to install localized versions use filenames like âhelp.LL.txtâ with LL denoting the locale. GnuPG comes with a set of predefined help files in the data directory (e.g. â/opt/homebrew/Cellar/gnupg/2.4.5/share/gnupg/gnupg/help.de.txtâ) and allows overriding of any help item by help files stored in the system configuration directory (e.g. â/opt/homebrew/etc/gnupg/help.de.txtâ). For a reference of the help file's syntax, please see the installed âhelp.txtâ file. com-certs.pem This file is a collection of common certificates used to populated a newly created âpubring.kbxâ. An administrator may replace this file with a custom one. The format is a concatenation of PEM encoded X.509 certificates. This global file is installed in the data directory (e.g. â/opt/homebrew/Cellar/gnupg/2.4.5/share/gnupg/com-certs.pemâ). Note that on larger installations, it is useful to put predefined files into the directory â/etc/skel/.gnupg/â so that newly created users start up with a working configuration. For existing users a small helper script is provided to create these files (see: [addgnupghome]). For internal purposes gpgsm creates and maintains a few other files; they all live in the current home directory (see: [option --homedir]). Only gpgsm may modify these files. pubring.kbx This a database file storing the certificates as well as meta information. For debugging purposes the tool kbxutil may be used to show the internal structure of this file. You should backup this file. random_seed This content of this file is used to maintain the internal state of the random number generator across invocations. The same file is used by other programs of this software too. S.gpg-agent If this file exists gpgsm will first try to connect to this socket for accessing gpg-agent before starting a new gpg-agent instance. Under Windows this socket (which in reality be a plain file describing a regular TCP listening port) is the standard way of connecting the gpg-agent. SEE ALSO gpg(1), gpg-agent(1) The full documentation for this tool is maintained as a Texinfo manual. If GnuPG and the info program are properly installed at your site, the command info gnupg should give you access to the complete manual including a menu structure and an index. GnuPG 2.4.5 2024-03-04 GPGSM(1)
|
ziptool
|
ziptool modifies the zip archive zip-archive according to the commands given. Supported options: -c Check zip archive consistency when opening it. -e Error if archive already exists (only useful with -n). -g Guess file name encoding (for stat command). -h Display help. -l length Only read length bytes of archive. See also -o. -n Create archive if it doesn't exist. See also -e. -o offset Start reading input archive from offset. See also -l. -r Print raw file name encoding without translation (for stat command). -s Follow file name convention strictly (for stat command). -t Disregard current file contents, if any. Note: use this with care, it deletes all existing file contents when you modify the archive. Commands For all commands below, the index is zero-based. In other words, the first entry in the zip archive has index 0. Supported commands and arguments are: add name content Add file called name using the string content from the command line as data. add_dir name Add directory name. add_file name file_to_add offset len Add file name to archive, using len bytes from the file file_to_add as input data, starting at offset. add_from_zip name archivename index offset len Add file called name to archive using data from another zip archive archivename using the entry with index index and reading len bytes from offset. cat index Output file contents for entry index to stdout. count_extra index flags Print the number of extra fields for archive entry index using flags. count_extra_by_id index extra_id flags Print number of extra fields of type extra_id for archive entry index using flags. delete index Remove entry at index from zip archive. delete_extra index extra_idx flags Remove extra field number extra_idx from archive entry index using flags. delete_extra_by_id index extra_id extra_index flags Remove extra field number extra_index of type extra_id from archive entry index using flags. get_archive_comment Print archive comment. get_archive_flag flag Print state of archive flag flag. get_extra index extra_index flags Print extra field extra_index for archive entry index using flags. get_extra_by_id index extra_id extra_index flags Print extra field extra_index of type extra_id for archive entry index using flags. get_file_comment index Get file comment for archive entry index. get_num_entries flags Print number of entries in archive using flags. name_locate name flags Find entry in archive with the filename name using flags and print its index. rename index name Rename archive entry index to name. replace_file_contents index data Replace file contents for archive entry index with the string data. set_archive_comment comment Set archive comment to comment. get_archive_flag flag value Set archive flag flag to value. set_extra index extra_id extra_index flags value Set extra field number extra_index of type extra_id for archive entry index using flags to value. set_file_comment index comment Set file comment for archive entry index to string comment. set_file_compression index method compression_flags Set file compression method for archive entry index to method using compression_flags. Note: Currently, compression_flags are ignored. set_file_encryption index method password Set file encryption method for archive entry index to method with password password. set_file_mtime index timestamp Set file modification time for archive entry index to UNIX mtime timestamp. set_file_mtime_all timestamp Set file modification time for all archive entries to UNIX mtime timestamp. set_password password Set default password for encryption/decryption to password. stat index Print information about archive entry index. Flags Some commands take flag arguments. Each character in the argument sets the corresponding flag. Use 0 or the empty string for no flags. Supported flags are: 4 ZIP_FL_ENC_CP437 8 ZIP_FL_ENC_UTF_8 C ZIP_FL_NOCASE c ZIP_FL_CENTRAL d ZIP_FL_NODIR l ZIP_FL_LOCAL r ZIP_FL_ENC_RAW s ZIP_FL_ENC_STRICT u ZIP_FL_UNCHANGED Archive flags get_archive_flag and set_archive_flag work on the following flags: ⢠create-or-keep-empty-file-for-archive ⢠is-torrentzip ⢠rdonly ⢠want-torrentzip Compression Methods Some commands take compression method arguments. Supported methods are: ⢠default ⢠deflate ⢠store Encryption Methods Some commands take encryption method arguments. Supported methods are: ⢠none ⢠AES-128 ⢠AES-192 ⢠AES-256 EXIT STATUS The ziptool utility exits 0 on success, and >0 if an error occurs.
|
ziptool â modify zip archives
|
ziptool [-ceghnrst] [-l length] [-o offset] zip-archive command [command-args ...] [command [command-args ...] ...]
| null |
Add a file called teststring.txt to the zip archive testbuffer.zip with data âThis is a test.\nâ where â\nâ is replaced with a newline character: ziptool testbuffer.zip add teststring.txt \"This is a test.\n\" Delete the first file from the zip archive testfile.zip: ziptool testfile.zip delete 0 SEE ALSO zipcmp(1), zipmerge(1), libzip(3) HISTORY ziptool was added in libzip 1.1. AUTHORS Dieter Baron <dillo@nih.at> and Thomas Klausner <tk@giga.or.at> macOS 14.5 January 23, 2023 macOS 14.5
|
hwloc-patch
|
hwloc-patch loads the difference between two topologies from a XML file (or from the standard input) and applies it to an existing topology, generating a new, modified one. The XML difference may have been computed earlier with hwloc-diff or hwloc-compress-dir. If <output.xml> is given, the new, modified topology is stored in that new file. Otherwise, <topology.xml> is modified in place. If refname is given instead of <topology.xml>, the input topology filename is automatically guessed by reading the refname field of the XML diff file. By default hwloc-diff generates XML diffs with the right reference topology filename (without any path prefix). If - is given instead of <diff.xml>, the topology difference is read from the standard input. NOTE: If some application-specific userdata were been exported to the input XMLs, they will be ignored and discarded from the output because hwloc has no way to understand and patch them. NOTE: It is highly recommended that you read the hwloc(7) overview page before reading this man page. Most of the concepts described in hwloc(7) directly apply to the hwloc-patch utility.
|
hwloc-patch - Apply a topology difference to an existing XML topology
|
hwloc-patch [options] [<topology.xml> | refname] [<diff.xml> | -] <output.xml> hwloc-patch [options] [<topology.xml> | refname] [<diff.xml> | -]
|
-R --reverse Reverse the sense the difference file. --version Report version and exit. -h --help Display help message and exit.
|
hwloc-patch's operation is best described through several examples. Apply a XML topology difference file to an existing topology: $ hwloc-patch fourmi023.xml diff.xml fourmi023-new.xml Apply a XML topology difference file whole refname field contains the right input topology: $ hwloc-patch refname diff.xml fourmi023-new.xml Apply a XML topology from the standard intput: $ cat diff.xml | hwloc-patch fourmi023.xml - fourmi023-new.xml Directly compute the difference between two topologies and apply it to another one, in place: $ hwloc-diff fourmi023.xml fourmi024.xml | hwloc-patch fourmi025.xml - RETURN VALUE Upon successful execution, hwloc-patch outputs the modified topology. The return value is 0. hwloc-patch also returns nonzero if any kind of error occurs, such as (but not limited to) failure to parse the command line. SEE ALSO hwloc(7), lstopo(1), hwloc-diff(1), hwloc-compress-dir(1) 2.10.0 December 4, 2023 HWLOC-PATCH(1)
|
httpserv
| null | null | null | null | null |
giffix
|
A program that attempts to fix broken GIF images. Currently will "fix" images terminated prematurely by filling the rest of the image with the darkest color found in the image. If no GIF file is given, giffix will try to read a GIF file from stdin. The fixed file is dumped to stdout.
|
giffix - attempt to fix up broken GIFs
|
giffix [-v] [-h] [gif-file]
|
-t Verbose mode (show progress). Enables printout of running scan lines. -h Print one line of command line help, similar to Usage above. AUTHOR Gershon Elber. GIFLIB 2 May 2012 GIFFIX(1)
| null |
zlib_decompress
|
The zlib_decompress utility decompresses mysqlpump output that was created using ZLIB compression. Note If MySQL was configured with the -DWITH_ZLIB=system option, zlib_decompress is not built. In this case, the system openssl zlib command can be used instead. Invoke zlib_decompress like this: zlib_decompress input_file output_file Example: mysqlpump --compress-output=ZLIB > dump.zlib zlib_decompress dump.zlib dump.txt To see a help message, invoke zlib_decompress with no arguments. To decompress mysqlpump LZ4-compressed output, use lz4_decompress. See lz4_decompress(1). COPYRIGHT Copyright © 1997, 2023, Oracle and/or its affiliates. This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see http://www.gnu.org/licenses/. SEE ALSO For more information, please refer to the MySQL Reference Manual, which may already be installed locally and which is also available online at http://dev.mysql.com/doc/. AUTHOR Oracle Corporation (http://dev.mysql.com/). MySQL 8.3 11/23/2023 ZLIB_DECOMPRESS(1)
|
zlib_decompress - decompress mysqlpump ZLIB-compressed output
|
zlib_decompress input_file output_file
| null | null |
gmkfifo
|
Create named pipes (FIFOs) with the given NAMEs. Mandatory arguments to long options are mandatory for short options too. -m, --mode=MODE set file permission bits to MODE, not a=rw - umask -Z set the SELinux security context to default type --context[=CTX] like -Z, or if CTX is specified then set the SELinux or SMACK security context to CTX --help display this help and exit --version output version information and exit AUTHOR Written by David MacKenzie. REPORTING BUGS GNU coreutils online help: <https://www.gnu.org/software/coreutils/> Report any translation bugs to <https://translationproject.org/team/> COPYRIGHT Copyright © 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO mkfifo(3) Full documentation <https://www.gnu.org/software/coreutils/mkfifo> or available locally via: info '(coreutils) mkfifo invocation' GNU coreutils 9.3 April 2023 MKFIFO(1)
|
mkfifo - make FIFOs (named pipes)
|
mkfifo [OPTION]... NAME...
| null | null |
lzless
|
xzless is a filter that displays text from compressed files to a terminal. Files supported by xz(1) are decompressed; other files are assumed to be in uncompressed form already. If no files are given, xzless reads from standard input. xzless uses less(1) to present its output. Unlike xzmore, its choice of pager cannot be altered by setting an environment variable. Commands are based on both more(1) and vi(1) and allow back and forth movement and searching. See the less(1) manual for more information. The command named lzless is provided for backward compatibility with LZMA Utils. ENVIRONMENT LESSMETACHARS A list of characters special to the shell. Set by xzless unless it is already set in the environment. LESSOPEN Set to a command line to invoke the xz(1) decompressor for preprocessing the input files to less(1). SEE ALSO less(1), xz(1), xzmore(1), zless(1) Tukaani 2024-02-12 XZLESS(1)
|
xzless, lzless - view xz or lzma compressed (text) files
|
xzless [file...] lzless [file...]
| null | null |
pk1sign
| null | null | null | null | null |
query_included_headers
| null | null | null | null | null |
rsa_genkey
| null | null | null | null | null |
xsubpp
|
This compiler is typically run by the makefiles created by ExtUtils::MakeMaker or by Module::Build or other Perl module build tools. xsubpp will compile XS code into C code by embedding the constructs necessary to let C functions manipulate Perl values and creates the glue necessary to let Perl access those functions. The compiler uses typemaps to determine how to map C function parameters and variables to Perl values. The compiler will search for typemap files called typemap. It will use the following search path to find default typemaps, with the rightmost typemap taking precedence. ../../../typemap:../../typemap:../typemap:typemap It will also use a default typemap installed as "ExtUtils::typemap".
|
xsubpp - compiler to convert Perl XS code into C code
|
xsubpp [-v] [-except] [-s pattern] [-prototypes] [-noversioncheck] [-nolinenumbers] [-nooptimize] [-typemap typemap] [-output filename]... file.xs
|
Note that the "XSOPT" MakeMaker option may be used to add these options to any makefiles generated by MakeMaker. -hiertype Retains '::' in type names so that C++ hierarchical types can be mapped. -except Adds exception handling stubs to the C code. -typemap typemap Indicates that a user-supplied typemap should take precedence over the default typemaps. This option may be used multiple times, with the last typemap having the highest precedence. -output filename Specifies the name of the output file to generate. If no file is specified, output will be written to standard output. -v Prints the xsubpp version number to standard output, then exits. -prototypes By default xsubpp will not automatically generate prototype code for all xsubs. This flag will enable prototypes. -noversioncheck Disables the run time test that determines if the object file (derived from the ".xs" file) and the ".pm" files have the same version number. -nolinenumbers Prevents the inclusion of '#line' directives in the output. -nooptimize Disables certain optimizations. The only optimization that is currently affected is the use of targets by the output C code (see perlguts). This may significantly slow down the generated code, but this is the way xsubpp of 5.005 and earlier operated. -noinout Disable recognition of "IN", "OUT_LIST" and "INOUT_LIST" declarations. -noargtypes Disable recognition of ANSI-like descriptions of function signature. -C++ Currently doesn't do anything at all. This flag has been a no-op for many versions of perl, at least as far back as perl5.003_07. It's allowed here for backwards compatibility. -s=... or -strip=... This option is obscure and discouraged. If specified, the given string will be stripped off from the beginning of the C function name in the generated XS functions (if it starts with that prefix). This only applies to XSUBs without "CODE" or "PPCODE" blocks. For example, the XS: void foo_bar(int i); when "xsubpp" is invoked with "-s foo_" will install a "foo_bar" function in Perl, but really call bar(i) in C. Most of the time, this is the opposite of what you want and failure modes are somewhat obscure, so please avoid this option where possible. ENVIRONMENT No environment variables are used. AUTHOR Originally by Larry Wall. Turned into the "ExtUtils::ParseXS" module by Ken Williams. MODIFICATION HISTORY See the file Changes. SEE ALSO perl(1), perlxs(1), perlxstut(1), ExtUtils::ParseXS perl v5.38.2 2023-11-28 XSUBPP(1)
| null |
gpgme-json
| null | null | null | null | null |
gdf
|
This manual page documents the GNU version of df. df displays the amount of space available on the file system containing each file name argument. If no file name is given, the space available on all currently mounted file systems is shown. Space is shown in 1K blocks by default, unless the environment variable POSIXLY_CORRECT is set, in which case 512-byte blocks are used. If an argument is the absolute file name of a device node containing a mounted file system, df shows the space available on that file system rather than on the file system containing the device node. This version of df cannot show the space available on unmounted file systems, because on most kinds of systems doing so requires very nonportable intimate knowledge of file system structures.
|
df - report file system space usage
|
df [OPTION]... [FILE]...
|
Show information about the file system on which each FILE resides, or all file systems by default. Mandatory arguments to long options are mandatory for short options too. -a, --all include pseudo, duplicate, inaccessible file systems -B, --block-size=SIZE scale sizes by SIZE before printing them; e.g., '-BM' prints sizes in units of 1,048,576 bytes; see SIZE format below -h, --human-readable print sizes in powers of 1024 (e.g., 1023M) -H, --si print sizes in powers of 1000 (e.g., 1.1G) -i, --inodes list inode information instead of block usage -k like --block-size=1K -l, --local limit listing to local file systems --no-sync do not invoke sync before getting usage info (default) --output[=FIELD_LIST] use the output format defined by FIELD_LIST, or print all fields if FIELD_LIST is omitted. -P, --portability use the POSIX output format --sync invoke sync before getting usage info --total elide all entries insignificant to available space, and produce a grand total -t, --type=TYPE limit listing to file systems of type TYPE -T, --print-type print file system type -x, --exclude-type=TYPE limit listing to file systems not of type TYPE -v (ignored) --help display this help and exit --version output version information and exit Display values are in units of the first available SIZE from --block-size, and the DF_BLOCK_SIZE, BLOCK_SIZE and BLOCKSIZE environment variables. Otherwise, units default to 1024 bytes (or 512 if POSIXLY_CORRECT is set). The SIZE argument is an integer and optional unit (example: 10K is 10*1024). Units are K,M,G,T,P,E,Z,Y,R,Q (powers of 1024) or KB,MB,... (powers of 1000). Binary prefixes can be used, too: KiB=K, MiB=M, and so on. FIELD_LIST is a comma-separated list of columns to be included. Valid field names are: 'source', 'fstype', 'itotal', 'iused', 'iavail', 'ipcent', 'size', 'used', 'avail', 'pcent', 'file' and 'target' (see info page). AUTHOR Written by Torbjorn Granlund, David MacKenzie, and Paul Eggert. REPORTING BUGS GNU coreutils online help: <https://www.gnu.org/software/coreutils/> Report any translation bugs to <https://translationproject.org/team/> COPYRIGHT Copyright © 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO Full documentation <https://www.gnu.org/software/coreutils/df> or available locally via: info '(coreutils) df invocation' GNU coreutils 9.3 April 2023 DF(1)
| null |
mysql_client_test
| null | null | null | null | null |
tidy
|
Tidy reads HTML, XHTML, and XML files and writes cleaned-up markup. For HTML variants, it detects, reports, and corrects many common coding errors and strives to produce visually equivalent markup that is both conformant to the HTML specifications and that works in most browsers. A common use of Tidy is to convert plain HTML to XHTML. For generic XML files, Tidy is limited to correcting basic well-formedness errors and pretty printing. If no input file is specified, Tidy reads the standard input. If no output file is specified, Tidy writes the tidied markup to the standard output. If no error file is specified, Tidy writes messages to the standard error.
|
tidy - check, correct, and pretty-print HTML(5) files
|
tidy [options] [file ...] [options] [file ...] ...
|
Tidy supports two different kinds of options. Purely command-line options, starting with a single dash '-', can only be used on the command-line, not in configuration files. They are listed in the first part of this section. Configuration options, on the other hand, can either be passed on the command line, starting with two dashes --, or specified in a configuration file, using the option name, followed by a colon :, plus the value, without the starting dashes. They are listed in the second part of this section, with a sample config file. For command-line options that expect a numerical argument, a default is assumed if no meaningful value can be found. On the other hand, configuration options cannot be used without a value; a configuration option without a value is simply discarded and reported as an error. Using a command-line option is sometimes equivalent to setting the value of a configuration option. The equivalent option and value are shown in parentheses in the list below, as they would appear in a configuration file. For example, -quiet, -q (quiet: yes) means that using the command-line option -quiet or -q is equivalent to setting the configuration option quiet to yes. Single-letter command-line options without an associated value can be combined; for example '-i', '-m' and '-u' may be combined as '-imu'. File manipulation -output <file>, -o <file> (output-file: <file>) write output to the specified <file> -config <file> set configuration options from the specified <file> -file <file>, -f <file> (error-file: <file>) write errors and warnings to the specified <file> -modify, -m (write-back: yes) modify the original input files Processing directives -indent, -i (indent: auto) indent element content -wrap <column>, -w <column> (wrap: <column>) wrap text at the specified <column>. 0 is assumed if <column> is missing. When this option is omitted, the default of the configuration option 'wrap' applies. -upper, -u (uppercase-tags: yes) force tags to upper case -clean, -c (clean: yes) replace FONT, NOBR and CENTER tags with CSS -bare, -b (bare: yes) strip out smart quotes and em dashes, etc. -gdoc, -g (gdoc: yes) produce clean version of html exported by Google Docs -numeric, -n (numeric-entities: yes) output numeric rather than named entities -errors, -e (markup: no) show only errors and warnings -quiet, -q (quiet: yes) suppress nonessential output -omit (omit-optional-tags: yes) omit optional start tags and end tags -xml (input-xml: yes) specify the input is well formed XML -asxml, -asxhtml (output-xhtml: yes) convert HTML to well formed XHTML -ashtml (output-html: yes) force XHTML to well formed HTML -access <level> (accessibility-check: <level>) do additional accessibility checks (<level> = 0, 1, 2, 3). 0 is assumed if <level> is missing. Character encodings -raw output values above 127 without conversion to entities -ascii use ISO-8859-1 for input, US-ASCII for output -latin0 use ISO-8859-15 for input, US-ASCII for output -latin1 use ISO-8859-1 for both input and output -iso2022 use ISO-2022 for both input and output -utf8 use UTF-8 for both input and output -mac use MacRoman for input, US-ASCII for output -win1252 use Windows-1252 for input, US-ASCII for output -ibm858 use IBM-858 (CP850+Euro) for input, US-ASCII for output -utf16le use UTF-16LE for both input and output -utf16be use UTF-16BE for both input and output -utf16 use UTF-16 for both input and output -big5 use Big5 for both input and output -shiftjis use Shift_JIS for both input and output Miscellaneous -version, -v show the version of Tidy -help, -h, -? list the command line options -help-config list all configuration options -help-env show information about the environment and runtime configuration -show-config list the current configuration settings -export-config list the current configuration settings, suitable for a config file -export-default-config list the default configuration settings, suitable for a config file -help-option <option> show a description of the <option> -language <lang> (language: <lang>) set Tidy's output language to <lang>. Specify '-language help' for more help. Use before output-causing arguments to ensure the language takes effect, e.g.,`tidy -lang es -lang help`. XML -xml-help list the command line options in XML format -xml-config list all configuration options in XML format -xml-strings output all of Tidy's strings in XML format -xml-error-strings output error constants and strings in XML format -xml-options-strings output option descriptions in XML format Configuration Options General Configuration options can be specified by preceding each option with -- at the command line, followed by its desired value, OR by placing the options and values in a configuration file, and telling tidy to read that file with the -config option: tidy --option1 value1 --option2 value2 ... tidy -config config-file ... Configuration options can be conveniently grouped in a single config file. A Tidy configuration file is simply a text file, where each option is listed on a separate line in the form option1: value1 option2: value2 etc. The permissible values for a given option depend on the option's Type. There are five Types: Boolean, AutoBool, DocType, Enum, and String. Boolean Types allow any of yes/no, y/n, true/false, t/f, 1/0. AutoBools allow auto in addition to the values allowed by Booleans. Integer Types take non-negative integers. String Types generally have no defaults, and you should provide them in non-quoted form (unless you wish the output to contain the literal quotes). Enum, Encoding, and DocType Types have a fixed repertoire of items, which are listed in the Supported values sections below. You only need to provide options and values for those whose defaults you wish to override, although you may wish to include some already- defaulted options and values for the sake of documentation and explicitness. Here is a sample config file, with at least one example of each of the five Types: // sample Tidy configuration options output-xhtml: yes add-xml-decl: no doctype: strict char-encoding: ascii indent: auto wrap: 76 repeated-attributes: keep-last error-file: errs.txt Below is a summary and brief description of each of the options. They are listed alphabetically within each category. Document Display options --gnu-emacs Boolean (no if unset) This option specifies that Tidy should change the format for reporting errors and warnings to a format that is more easily parsed by GNU Emacs or some other program. It changes them from the default line <line number> column <column number> - (Error|Warning): <message> to a form which includes the input filename: <filename>:<line number>:<column number>: (Error|Warning): <message> See also: --show-filename --markup Boolean (yes if unset) This option specifies if Tidy should generate a pretty printed version of the markup. Note that Tidy won't generate a pretty printed version if it finds significant errors (see force- output). --mute String Use this option to prevent Tidy from displaying certain types of report output, for example, for conditions that you wish to ignore. This option takes a list of one or more keys indicating the message type to mute. You can discover these message keys by using the mute-id configuration option and examining Tidy's output. See also: --mute-id --mute-id Boolean (no if unset) This option indicates whether or not Tidy should display message ID's with each of its error reports. This could be useful if you wanted to use the mute configuration option in order to filter out certain report messages. See also: --mute --quiet Boolean (no if unset) When enabled, this option limits Tidy's non-document output to report only document warnings and errors. --show-body-only Enum (no if unset) Supported values: no, yes, auto This option specifies if Tidy should print only the contents of the body tag as an HTML fragment. If set to auto, this is performed only if the body tag has been inferred. Useful for incorporating existing whole pages as a portion of another page. This option has no effect if XML output is requested. --show-errors Integer (6 if unset) This option specifies the number Tidy uses to determine if further errors should be shown. If set to 0, then no errors are shown. --show-filename Boolean (no if unset) This option specifies if Tidy should show the filename in messages. eg: tidy -q -e --show-filename yes index.html index.html: line 43 column 3 - Warning: replacing invalid UTF-8 bytes (char. code U+00A9) See also: --gnu-emacs --show-info Boolean (yes if unset) This option specifies if Tidy should display info-level messages. --show-warnings Boolean (yes if unset) This option specifies if Tidy should suppress warnings. This can be useful when a few errors are hidden in a flurry of warnings. Document In and Out options --add-meta-charset Boolean (no if unset) This option, when enabled, adds a <meta> element and sets the charset attribute to the encoding of the document. Set this option to yes to enable it. --add-xml-decl Boolean (no if unset) This option specifies if Tidy should add the XML declaration when outputting XML or XHTML. Note that if the input already includes an <?xml ... ?> declaration then this option will be ignored. If the encoding for the output is different from ascii, one of the utf* encodings, or raw, then the declaration is always added as required by the XML standard. See also: --char-encoding, --output-encoding --add-xml-space Boolean (no if unset) This option specifies if Tidy should add xml:space="preserve" to elements such as <pre>, <style> and <script> when generating XML. This is needed if the whitespace in such elements is to be parsed appropriately without having access to the DTD. --doctype String (auto if unset) This option specifies the DOCTYPE declaration generated by Tidy. If set to omit the output won't contain a DOCTYPE declaration. Note this this also implies numeric-entities is set to yes. If set to html5 the DOCTYPE is set to <!DOCTYPE html>. If set to auto (the default) Tidy will use an educated guess based upon the contents of the document. Note that selecting this option will not change the current document's DOCTYPE on output. If set to strict, Tidy will set the DOCTYPE to the HTML4 or XHTML1 strict DTD. If set to loose, the DOCTYPE is set to the HTML4 or XHTML1 loose (transitional) DTD. Alternatively, you can supply a string for the formal public identifier (FPI). For example: doctype: "-//ACME//DTD HTML 3.14159//EN" If you specify the FPI for an XHTML document, Tidy will set the system identifier to an empty string. For an HTML document, Tidy adds a system identifier only if one was already present in order to preserve the processing mode of some browsers. Tidy leaves the DOCTYPE for generic XML documents unchanged. This option does not offer a validation of document conformance. --input-xml Boolean (no if unset) This option specifies if Tidy should use the XML parser rather than the error correcting HTML parser. --output-html Boolean (no if unset) This option specifies if Tidy should generate pretty printed output, writing it as HTML. --output-xhtml Boolean (no if unset) This option specifies if Tidy should generate pretty printed output, writing it as extensible HTML. This option causes Tidy to set the DOCTYPE and default namespace as appropriate to XHTML, and will use the corrected value in output regardless of other sources. For XHTML, entities can be written as named or numeric entities according to the setting of numeric-entities. The original case of tags and attributes will be preserved, regardless of other options. --output-xml Boolean (no if unset) This option specifies if Tidy should pretty print output, writing it as well-formed XML. Any entities not defined in XML 1.0 will be written as numeric entities to allow them to be parsed by an XML parser. The original case of tags and attributes will be preserved, regardless of other options. File Input-Output options --error-file String This option specifies the error file Tidy uses for errors and warnings. Normally errors and warnings are output to stderr. See also: --output-file --keep-time Boolean (no if unset) This option specifies if Tidy should keep the original modification time of files that Tidy modifies in place. Setting the option to yes allows you to tidy files without changing the file modification date, which may be useful with certain tools that use the modification date for things such as automatic server deployment. Note this feature is not supported on some platforms. --output-file String This option specifies the output file Tidy uses for markup. Normally markup is written to stdout. See also: --error-file --write-back Boolean (no if unset) This option specifies if Tidy should write back the tidied markup to the same file it read from. You are advised to keep copies of important files before tidying them, as on rare occasions the result may not be what you expect. Diagnostics options --accessibility-check Enum (0 (Tidy Classic) if unset) Supported values: 0 (Tidy Classic), 1 (Priority 1 Checks), 2 (Priority 2 Checks), 3 (Priority 3 Checks) This option specifies what level of accessibility checking, if any, that Tidy should perform. Level 0 (Tidy Classic) performs no additional accessibility checking. Level 1 (Priority 1 Checks) performs the Priority Level 1 checks. Level 2 (Priority 2 Checks) performs the Priority Level 1 and 2 checks. Level 3 (Priority 3 Checks) performs the Priority Level 1, 2, and 3 checks. For more information on Tidy's accessibility checking, including the specific checks that are made for each Priority Level, please visit Tidy's Accessibility Page at http://www.html- tidy.org/accessibility/. --force-output Boolean (no if unset) This option specifies if Tidy should produce output even if errors are encountered. Use this option with care; if Tidy reports an error, this means Tidy was not able to (or is not sure how to) fix the error, so the resulting output may not reflect your intention. --show-meta-change Boolean (no if unset) This option enables a message whenever Tidy changes the content attribute of a meta charset declaration to match the encoding of the document. Set this option to yes to enable it. --warn-proprietary-attributes Boolean (yes if unset) This option specifies if Tidy should warn on proprietary attributes. Encoding options --char-encoding Encoding (utf8 if unset) Supported values: raw, ascii, latin0, latin1, utf8, iso2022, mac, win1252, ibm858, utf16le, utf16be, utf16, big5, shiftjis This option specifies the character encoding Tidy uses for input, and when set, automatically chooses an appropriate character encoding to be used for output. The output encoding Tidy chooses may be different from the input encoding. For ascii, latin0, ibm858, mac, and win1252 input encodings, the output-encoding option will automatically be set to ascii. You can set output-encoding manually to override this. For other input encodings, the output-encoding option will automatically be set to the the same value. Regardless of the preset value, you can set output-encoding manually to override this. Tidy is not an encoding converter. Although the Latin and UTF encodings can be mixed freely, it is not possible to convert Asian encodings to Latin encodings with Tidy. See also: --input-encoding, --output-encoding --input-encoding Encoding (utf8 if unset) Supported values: raw, ascii, latin0, latin1, utf8, iso2022, mac, win1252, ibm858, utf16le, utf16be, utf16, big5, shiftjis This option specifies the character encoding Tidy uses for input. Tidy makes certain assumptions about some of the input encodings. For ascii, Tidy will accept Latin-1 (ISO-8859-1) character values and convert them to entities as necessary. For raw, Tidy will make no assumptions about the character values and will pass them unchanged to output. For mac and win1252, vendor specific characters values will be accepted and converted to entities as necessary. Asian encodings such as iso2022 will be handled appropriately assuming the corresponding output-encoding is also specified. Tidy is not an encoding converter. Although the Latin and UTF encodings can be mixed freely, it is not possible to convert Asian encodings to Latin encodings with Tidy. See also: --char-encoding --newline Enum (LF if unset) Supported values: LF, CRLF, CR The default is appropriate to the current platform. Genrally CRLF on PC-DOS, Windows and OS/2; CR on Classic Mac OS; and LF everywhere else (Linux, macOS, and Unix). --output-bom Enum (auto if unset) Supported values: no, yes, auto This option specifies if Tidy should write a Unicode Byte Order Mark character (BOM; also known as Zero Width No-Break Space; has value of U+FEFF) to the beginning of the output, and only applies to UTF-8 and UTF-16 output encodings. If set to auto this option causes Tidy to write a BOM to the output only if a BOM was present at the beginning of the input. A BOM is always written for XML/XHTML output using UTF-16 output encodings. --output-encoding Encoding (utf8 if unset) Supported values: raw, ascii, latin0, latin1, utf8, iso2022, mac, win1252, ibm858, utf16le, utf16be, utf16, big5, shiftjis This option specifies the character encoding Tidy uses for output. Some of the output encodings affect whether or not some characters are translated to entities, although in all cases, some entities will be written according to other Tidy configuration options. For ascii, mac, and win1252 output encodings, entities will be used for all characters with values over 127. For raw output, Tidy will write values above 127 without translating them to entities. Output using latin1 will cause Tidy to write character values higher than 255 as entities. The UTF family such as utf8 will write output in the respective UTF encoding. Asian output encodings such as iso2022 will write output in the specified encoding, assuming a corresponding input-encoding was specified. Tidy is not an encoding converter. Although the Latin and UTF encodings can be mixed freely, it is not possible to convert Asian encodings to Latin encodings with Tidy. See also: --char-encoding Cleanup options --bare Boolean (no if unset) This option specifies if Tidy should replace smart quotes and em dashes with ASCII, and output spaces rather than non-breaking spaces, where they exist in the input. --clean Boolean (no if unset) This option specifies if Tidy should perform cleaning of some legacy presentational tags (currently <i>, <b>, <center> when enclosed within appropriate inline tags, and <font>). If set to yes, then the legacy tags will be replaced with CSS <style> tags and structural markup as appropriate. --drop-empty-elements Boolean (yes if unset) This option specifies if Tidy should discard empty elements. --drop-empty-paras Boolean (yes if unset) This option specifies if Tidy should discard empty paragraphs. --drop-proprietary-attributes Boolean (no if unset) This option specifies if Tidy should strip out proprietary attributes, such as Microsoft data binding attributes. Additionally attributes that aren't permitted in the output version of HTML will be dropped if used with strict-tags- attributes. --gdoc Boolean (no if unset) This option specifies if Tidy should enable specific behavior for cleaning up HTML exported from Google Docs. --logical-emphasis Boolean (no if unset) This option specifies if Tidy should replace any occurrence of <i> with <em> and any occurrence of <b> with <strong>. Any attributes are preserved unchanged. This option can be set independently of the clean option. --merge-divs Enum (auto if unset) Supported values: no, yes, auto This option can be used to modify the behavior of clean when set to yes. This option specifies if Tidy should merge nested <div> such as <div><div>...</div></div>. If set to auto the attributes of the inner <div> are moved to the outer one. Nested <div> with id attributes are not merged. If set to yes the attributes of the inner <div> are discarded with the exception of class and style. See also: --clean, --merge-spans --merge-spans Enum (auto if unset) Supported values: no, yes, auto This option can be used to modify the behavior of clean when set to yes. This option specifies if Tidy should merge nested <span> such as <span><span>...</span></span>. The algorithm is identical to the one used by merge-divs. See also: --clean, --merge-divs --word-2000 Boolean (no if unset) This option specifies if Tidy should go to great pains to strip out all the surplus stuff Microsoft Word 2000 inserts when you save Word documents as "Web pages". It doesn't handle embedded images or VML. You should consider saving using Word's Save As..., and choosing Web Page, Filtered. Entities options --ascii-chars Boolean (no if unset) Can be used to modify behavior of the clean option when set to yes. If set to yes when using clean, &emdash;, ”, and other named character entities are downgraded to their closest ASCII equivalents. See also: --clean --ncr Boolean (yes if unset) This option specifies if Tidy should allow numeric character references. --numeric-entities Boolean (no if unset) This option specifies if Tidy should output entities other than the built-in HTML entities (&, <, >, and ") in the numeric rather than the named entity form. Only entities compatible with the DOCTYPE declaration generated are used. Entities that can be represented in the output encoding are translated correspondingly. See also: --doctype, --preserve-entities --preserve-entities Boolean (no if unset) This option specifies if Tidy should preserve well-formed entities as found in the input. --quote-ampersand Boolean (yes if unset) This option specifies if Tidy should output unadorned & characters as &, in legacy doctypes only. --quote-marks Boolean (no if unset) This option specifies if Tidy should output " characters as " as is preferred by some editing environments. The apostrophe character ' is written out as ' since many web browsers don't yet support '. --quote-nbsp Boolean (yes if unset) This option specifies if Tidy should output non-breaking space characters as entities, rather than as the Unicode character value 160 (decimal). Repair options --alt-text String This option specifies the default alt= text Tidy uses for <img> attributes when the alt= attribute is missing. Use with care, as it is your responsibility to make your documents accessible to people who cannot see the images. --anchor-as-name Boolean (yes if unset) This option controls the deletion or addition of the name attribute in elements where it can serve as anchor. If set to yes a name attribute, if not already existing, is added along an existing id attribute if the DTD allows it. If set to no any existing name attribute is removed if an id attribute exists or has been added. --assume-xml-procins Boolean (no if unset) This option specifies if Tidy should change the parsing of processing instructions to require ?> as the terminator rather than >. This option is automatically set if the input is in XML. --coerce-endtags Boolean (yes if unset) This option specifies if Tidy should coerce a start tag into an end tag in cases where it looks like an end tag was probably intended; for example, given <span>foo <b>bar<b> baz</span> Tidy will output <span>foo <b>bar</b> baz</span> --css-prefix String (c if unset) This option specifies the prefix that Tidy uses for styles rules. By default, c will be used. --custom-tags Enum (no if unset) Supported values: no, blocklevel, empty, inline, pre This option enables the use of tags for autonomous custom elements, e.g. <flag-icon> with Tidy. Custom tags are disabled if this value is no. Other settings - blocklevel, empty, inline, and pre will treat all detected custom tags accordingly. The use of new-blocklevel-tags, new-empty-tags, new-inline-tags, or new-pre-tags will override the treatment of custom tags by this configuration option. This may be useful if you have different types of custom tags. When enabled these tags are determined during the processing of your document using opening tags; matching closing tags will be recognized accordingly, and unknown closing tags will be discarded. See also: --new-blocklevel-tags, --new-empty-tags, --new-inline- tags, --new-pre-tags --enclose-block-text Boolean (no if unset) This option specifies if Tidy should insert a <p> element to enclose any text it finds in any element that allows mixed content for HTML transitional but not HTML strict. --enclose-text Boolean (no if unset) This option specifies if Tidy should enclose any text it finds in the body element within a <p> element. This is useful when you want to take existing HTML and use it with a style sheet. --escape-scripts Boolean (yes if unset) This option causes items that look like closing tags, like </g to be escaped to <\/g. Set this option to no if you do not want this. --fix-backslash Boolean (yes if unset) This option specifies if Tidy should replace backslash characters \ in URLs with forward slashes /. --fix-bad-comments Enum (auto if unset) Supported values: no, yes, auto This option specifies if Tidy should replace unexpected hyphens with = characters when it comes across adjacent hyphens. The default is auto will which will act as no for HTML5 document types, and yes for all other document types. HTML has abandoned SGML comment syntax, and allows adjacent hyphens for all versions of HTML, although XML and XHTML do not. If you plan to support older browsers that require SGML comment syntax, then consider setting this value to yes. --fix-style-tags Boolean (yes if unset) This option specifies if Tidy should move all style tags to the head of the document. --fix-uri Boolean (yes if unset) This option specifies if Tidy should check attribute values that carry URIs for illegal characters and if such are found, escape them as HTML4 recommends. --literal-attributes Boolean (no if unset) This option specifies how Tidy deals with whitespace characters within attribute values. If the value is no Tidy normalizes attribute values by replacing any newline or tab with a single space, and further by replacing any contiguous whitespace with a single space. To force Tidy to preserve the original, literal values of all attributes and ensure that whitespace within attribute values is passed through unchanged, set this option to yes. --lower-literals Boolean (yes if unset) This option specifies if Tidy should convert the value of an attribute that takes a list of predefined values to lower case. This is required for XHTML documents. --repeated-attributes Enum (keep-last if unset) Supported values: keep-first, keep-last This option specifies if Tidy should keep the first or last attribute, if an attribute is repeated, e.g. has two align attributes. See also: --join-classes, --join-styles --skip-nested Boolean (yes if unset) This option specifies that Tidy should skip nested tags when parsing script and style data. --strict-tags-attributes Boolean (no if unset) This options ensures that tags and attributes are applicable for the version of HTML that Tidy outputs. When set to yes and the output document type is a strict doctype, then Tidy will report errors. If the output document type is a loose or transitional doctype, then Tidy will report warnings. Additionally if drop-proprietary-attributes is enabled, then not applicable attributes will be dropped, too. When set to no, these checks are not performed. --uppercase-attributes Enum (no if unset) Supported values: no, yes, preserve This option specifies if Tidy should output attribute names in upper case. When set to no, attribute names will be written in lower case. Specifying yes will output attribute names in upper case, and preserve can used to leave attribute names untouched. When using XML input, the original case is always preserved. --uppercase-tags Boolean (no if unset) This option specifies if Tidy should output tag names in upper case. The default is no which results in lower case tag names, except for XML input where the original case is preserved. Transformation options --decorate-inferred-ul Boolean (no if unset) This option specifies if Tidy should decorate inferred <ul> elements with some CSS markup to avoid indentation to the right. --escape-cdata Boolean (no if unset) This option specifies if Tidy should convert <![CDATA[]]> sections to normal text. --hide-comments Boolean (no if unset) This option specifies if Tidy should not print out comments. --join-classes Boolean (no if unset) This option specifies if Tidy should combine class names to generate a single, new class name if multiple class assignments are detected on an element. --join-styles Boolean (yes if unset) This option specifies if Tidy should combine styles to generate a single, new style if multiple style values are detected on an element. --merge-emphasis Boolean (yes if unset) This option specifies if Tidy should merge nested <b> and <i> elements; for example, for the case <b class="rtop-2">foo <b class="r2-2">bar</b> baz</b>, Tidy will output <b class="rtop-2">foo bar baz</b>. --replace-color Boolean (no if unset) This option specifies if Tidy should replace numeric values in color attributes with HTML/XHTML color names where defined, e.g. replace #ffffff with white. Teaching Tidy options --new-blocklevel-tags Tag Names Supported values: tagX, tagY, ... This option specifies new block-level tags. This option takes a space or comma separated list of tag names. Unless you declare new tags, Tidy will refuse to generate a tidied file if the input includes previously unknown tags. Note you can't change the content model for elements such as <table>, <ul>, <ol> and <dl>. This option is ignored in XML mode. See also: --new-empty-tags, --new-inline-tags, --new-pre-tags, --custom-tags --new-empty-tags Tag Names Supported values: tagX, tagY, ... This option specifies new empty inline tags. This option takes a space or comma separated list of tag names. Unless you declare new tags, Tidy will refuse to generate a tidied file if the input includes previously unknown tags. Remember to also declare empty tags as either inline or blocklevel. This option is ignored in XML mode. See also: --new-blocklevel-tags, --new-inline-tags, --new-pre- tags, --custom-tags --new-inline-tags Tag Names Supported values: tagX, tagY, ... This option specifies new non-empty inline tags. This option takes a space or comma separated list of tag names. Unless you declare new tags, Tidy will refuse to generate a tidied file if the input includes previously unknown tags. This option is ignored in XML mode. See also: --new-blocklevel-tags, --new-empty-tags, --new-pre- tags, --custom-tags --new-pre-tags Tag Names Supported values: tagX, tagY, ... This option specifies new tags that are to be processed in exactly the same way as HTML's <pre> element. This option takes a space or comma separated list of tag names. Unless you declare new tags, Tidy will refuse to generate a tidied file if the input includes previously unknown tags. Note you cannot as yet add new CDATA elements. This option is ignored in XML mode. See also: --new-blocklevel-tags, --new-empty-tags, --new-inline- tags, --custom-tags Pretty Print options --break-before-br Boolean (no if unset) This option specifies if Tidy should output a line break before each <br> element. --indent Enum (no if unset) Supported values: no, yes, auto This option specifies if Tidy should indent block-level tags. If set to auto Tidy will decide whether or not to indent the content of tags such as <title>, <h1>-<h6>, <li>, <td>, or <p> based on the content including a block-level element. Setting indent to yes can expose layout bugs in some browsers. Use the option indent-spaces to control the number of spaces or tabs output per level of indent, and indent-with-tabs to specify whether spaces or tabs are used. See also: --indent-spaces --indent-attributes Boolean (no if unset) This option specifies if Tidy should begin each attribute on a new line. --indent-cdata Boolean (no if unset) This option specifies if Tidy should indent <![CDATA[]]> sections. --indent-spaces Integer (2 if unset) This option specifies the number of spaces or tabs that Tidy uses to indent content when indent is enabled. Note that the default value for this option is dependent upon the value of indent-with-tabs (see also). See also: --indent --indent-with-tabs Boolean (no if unset) This option specifies if Tidy should indent with tabs instead of spaces, assuming indent is yes. Set it to yes to indent using tabs instead of the default spaces. Use the option indent-spaces to control the number of tabs output per level of indent. Note that when indent-with-tabs is enabled the default value of indent-spaces is reset to 1. Note tab-size controls converting input tabs to spaces. Set it to zero to retain input tabs. --keep-tabs Boolean (no if unset) With the default no Tidy will replace all source tabs with spaces, controlled by the option tab-size, and the current line offset. Of course, except in the special blocks/elements enumerated below, this will later be reduced to just one space. If set yes this option specifies Tidy should keep certain tabs found in the source, but only in preformatted blocks like <pre>, and other CDATA elements like <script>, <style>, and other pseudo elements like <?php ... ?>. As always, all other tabs, or sequences of tabs, in the source will continue to be replaced with a space. --omit-optional-tags Boolean (no if unset) This option specifies if Tidy should omit optional start tags and end tags when generating output. Setting this option causes all tags for the <html>, <head>, and <body> elements to be omitted from output, as well as such end tags as </p>, </li>, </dt>, </dd>, </option>, </tr>, </td>, and </th>. This option is ignored for XML output. --priority-attributes Attributes Names Supported values: attributeX, attributeY, ... This option allows prioritizing the writing of attributes in tidied documents, allowing them to written before the other attributes of an element. For example, you might specify that id and name are written before every other attribute. This option takes a space or comma separated list of attribute names. --punctuation-wrap Boolean (no if unset) This option specifies if Tidy should line wrap after some Unicode or Chinese punctuation characters. --sort-attributes Enum (none if unset) Supported values: none, alpha This option specifies that Tidy should sort attributes within an element using the specified sort algorithm. If set to alpha, the algorithm is an ascending alphabetic sort. When used while sorting with priority-attributes, any attribute sorting will take place after the priority attributes have been output. See also: --priority-attributes --tab-size Integer (8 if unset) This option specifies the number of columns that Tidy uses between successive tab stops. It is used to map tabs to spaces when reading the input. --tidy-mark Boolean (yes if unset) This option specifies if Tidy should add a meta element to the document head to indicate that the document has been tidied. Tidy won't add a meta element if one is already present. --vertical-space Enum (no if unset) Supported values: no, yes, auto This option specifies if Tidy should add some extra empty lines for readability. The default is no. If set to auto Tidy will eliminate nearly all newline characters. --wrap Integer (68 if unset) This option specifies the right margin Tidy uses for line wrapping. Tidy tries to wrap lines so that they do not exceed this length. Set wrap to 0 (zero) if you want to disable line wrapping. --wrap-asp Boolean (yes if unset) This option specifies if Tidy should line wrap text contained within ASP pseudo elements, which look like: <% ... %>. --wrap-attributes Boolean (no if unset) This option specifies if Tidy should line-wrap attribute values, meaning that if the value of an attribute causes a line to exceed the width specified by wrap, Tidy will add one or more line breaks to the value, causing it to be wrapped into multiple lines. Note that this option can be set independently of wrap-script- literals. By default Tidy replaces any newline or tab with a single space and replaces any sequences of whitespace with a single space. To force Tidy to preserve the original, literal values of all attributes, and ensure that whitespace characters within attribute values are passed through unchanged, set literal- attributes to yes. See also: --wrap-script-literals, --literal-attributes --wrap-jste Boolean (yes if unset) This option specifies if Tidy should line wrap text contained within JSTE pseudo elements, which look like: <# ... #>. --wrap-php Boolean (no if unset) This option specifies if Tidy should add a new line after a PHP pseudo elements, which look like: <?php ... ?>. --wrap-script-literals Boolean (no if unset) This option specifies if Tidy should line wrap string literals assigned to element event handler attributes, such as element.onmouseover(). See also: --wrap-attributes --wrap-sections Boolean (yes if unset) This option specifies if Tidy should line wrap text contained within <![ ... ]> section tags. ENVIRONMENT HTML_TIDY Name of the default configuration file. This should be an absolute path, since you will probably invoke tidy from different directories. The value of HTML_TIDY will be parsed after the compiled-in default (defined with -DTIDY_CONFIG_FILE), but before any of the files specified using -config. RUNTIME CONFIGURATION FILES You can also specify runtime configuration files from which tidy will attempt to load a configuration automatically. The system runtime configuration file (/etc/tidy.conf), if it exists will be loaded and applied first, followed by the user runtime configuration file (~/.tidyrc). Subsequent usage of a specific option will override any previous usage. Note that if you use the HTML_TIDY environment variable, then the user runtime configuration file will not be used. This is a feature, not a bug. EXIT STATUS 0 All input files were processed successfully. 1 There were warnings. 2 There were errors. SEE ALSO For more information about HTML Tidy: http://www.html-tidy.org/ For more information on HTML: HTML: Edition for Web Authors (the latest HTML specification) http://dev.w3.org/html5/spec-author-view HTML: The Markup Language (an HTML language reference) http://dev.w3.org/html5/markup/ For bug reports and comments: https://github.com/htacg/tidy-html5/issues/ Or send questions and comments to public-htacg@w3.org. Validate your HTML documents using the W3C Nu Markup Validator: http://validator.w3.org/nu/ AUTHOR Tidy was written by Dave Raggett <dsr@w3.org>, and subsequently maintained by a team at http://tidy.sourceforge.net/, and now maintained by HTACG (http://www.htacg.org). The sources for HTML Tidy are available at https://github.com/htacg/tidy-html5/ under the MIT Licence. HTML Tidy 5.8.0 TIDY(1)
| null |
pydoc3.11
| null | null | null | null | null |
streamzip
|
This program will read data from "stdin", compress it into a zip container and, by default, write a streamed zip file to "stdout". No temporary files are created. The zip container written to "stdout" is, by necessity, written in streaming format. Most programs that read Zip files can cope with a streamed zip file, but if interoperability is important, and your workflow allows you to write the zip file directly to disk you can create a non-streamed zip file using the "zipfile" option.
|
streamzip - create a zip file from stdin
|
producer | streamzip [opts] | consumer producer | streamzip [opts] -zipfile=output.zip
|
-zip64 Create a Zip64-compliant zip container. Use this option if the input is greater than 4Gig. Default is disabled. -zipfile=F Write zip container to the filename "F". Use the "Stream" option to force the creation of a streamed zip file. -member-name=M This option is used to name the "file" in the zip container. Default is '-'. -stream Ignored when writing to "stdout". If the "zipfile" option is specified, including this option will trigger the creation of a streamed zip file. Default: Always enabled when writing to "stdout", otherwise disabled. -method=M Compress using method "M". Valid method names are * store Store without compression * deflate Use Deflate compression [Deflault] * bzip2 Use Bzip2 compression * lzma Use LZMA compression * xz Use xz compression * zstd Use Zstandard compression Note that Lzma compress needs "IO::Compress::Lzma" to be installed. Note that Zstd compress needs "IO::Compress::Zstd" to be installed. Default is "deflate". -0, -1, -2, -3, -4, -5, -6, -7, -8, -9 Sets the compression level for "deflate". Ignored for all other compression methods. -0 means no compression and -9 for maximum compression. Default is 6 -version Display version number -help Display help
|
Create a zip file bt reading daa from stdin $ echo Lorem ipsum dolor sit | perl ./bin/streamzip >abcd.zip Check the contents of "abcd,zip" with the standard "unzip" utility Archive: abcd.zip Length Date Time Name --------- ---------- ----- ---- 22 2021-01-08 19:45 - --------- ------- 22 1 file Notice how the "Name" is set to "-". That is the default for a few zip utilities whwre the member name is not given. If you want to explicitly name the file, use the "-member-name" option as follows $ echo Lorem ipsum dolor sit | perl ./bin/streamzip -member-name latin >abcd.zip $ unzip -l abcd.zip Archive: abcd.zip Length Date Time Name --------- ---------- ----- ---- 22 2021-01-08 19:47 latin --------- ------- 22 1 file When to write a Streamed Zip File A Streamed Zip File is useful in situations where you cannot seek backwards/forwards in the file. A good examples is when you are serving dynamic content from a Web Server straight into a socket without needing to create a temporary zip file in the filesystsm. Similarly if your workfow uses a Linux pipelined commands. SUPPORT General feedback/questions/bug reports should be sent to <https://github.com/pmqs/IO-Compress/issues> (preferred) or <https://rt.cpan.org/Public/Dist/Display.html?Name=IO-Compress>. AUTHOR Paul Marquess pmqs@cpan.org. COPYRIGHT Copyright (c) 2019-2022 Paul Marquess. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.38.2 2023-11-28 STREAMZIP(1)
|
fileinfo
| null | null | null | null | null |
protoc-gen-upb_minitable
| null | null | null | null | null |
gjoin
|
For each pair of input lines with identical join fields, write a line to standard output. The default join field is the first, delimited by blanks. When FILE1 or FILE2 (not both) is -, read standard input. -a FILENUM also print unpairable lines from file FILENUM, where FILENUM is 1 or 2, corresponding to FILE1 or FILE2 -e STRING replace missing (empty) input fields with STRING; I.e., missing fields specified with '-12jo' options -i, --ignore-case ignore differences in case when comparing fields -j FIELD equivalent to '-1 FIELD -2 FIELD' -o FORMAT obey FORMAT while constructing output line -t CHAR use CHAR as input and output field separator -v FILENUM like -a FILENUM, but suppress joined output lines -1 FIELD join on this FIELD of file 1 -2 FIELD join on this FIELD of file 2 --check-order check that the input is correctly sorted, even if all input lines are pairable --nocheck-order do not check that the input is correctly sorted --header treat the first line in each file as field headers, print them without trying to pair them -z, --zero-terminated line delimiter is NUL, not newline --help display this help and exit --version output version information and exit Unless -t CHAR is given, leading blanks separate fields and are ignored, else fields are separated by CHAR. Any FIELD is a field number counted from 1. FORMAT is one or more comma or blank separated specifications, each being 'FILENUM.FIELD' or '0'. Default FORMAT outputs the join field, the remaining fields from FILE1, the remaining fields from FILE2, all separated by CHAR. If FORMAT is the keyword 'auto', then the first line of each file determines the number of fields output for each line. Important: FILE1 and FILE2 must be sorted on the join fields. E.g., use "sort -k 1b,1" if 'join' has no options, or use "join -t ''" if 'sort' has no options. Note, comparisons honor the rules specified by 'LC_COLLATE'. If the input is not sorted and some lines cannot be joined, a warning message will be given. AUTHOR Written by Mike Haertel. REPORTING BUGS GNU coreutils online help: <https://www.gnu.org/software/coreutils/> Report any translation bugs to <https://translationproject.org/team/> COPYRIGHT Copyright © 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO comm(1), uniq(1) Full documentation <https://www.gnu.org/software/coreutils/join> or available locally via: info '(coreutils) join invocation' GNU coreutils 9.3 April 2023 JOIN(1)
|
join - join lines of two files on a common field
|
join [OPTION]... FILE1 FILE2
| null | null |
md_hmac_demo
| null | null | null | null | null |
tiffinfo
|
tiffinfo displays information about files created according to the Tag Image File Format, Revision 6.0. By default, the contents of each TIFF directory in each file are displayed, with the value of each tag shown symbolically (where sensible).
|
tiffinfo - print information about TIFF files
|
tiffinfo [ options ] input.tif âŠ
|
-c Display the colormap and color/gray response curves, if present. -D In addition to displaying the directory tags, read and decompress all the data in each image (but not display it). -d In addition to displaying the directory tags, print each byte of decompressed data in hexadecimal. -j Display any JPEG-related tags that are present. -o Set the initial TIFF directory according to the specified file offset. The file offset may be specified using the usual C-style syntax; i.e. a leading 0x for hexadecimal and a leading 0 for octal. -s Display the offsets and byte counts for each data strip in a directory. -z Enable strip chopping when reading image data. -# Set the initial TIFF directory to #. SEE ALSO tiffdump, libtiff AUTHOR LibTIFF contributors COPYRIGHT 1988-2022, LibTIFF contributors 4.6 September 8, 2023 TIFFINFO(1)
| null |
accelerate-launch
| null | null | null | null | null |
mysqlshow
|
The mysqlshow client can be used to quickly see which databases exist, their tables, or a table's columns or indexes. mysqlshow provides a command-line interface to several SQL SHOW statements. See Section 13.7.7, âSHOW Statementsâ. The same information can be obtained by using those statements directly. For example, you can issue them from the mysql client program. Invoke mysqlshow like this: mysqlshow [options] [db_name [tbl_name [col_name]]] ⢠If no database is given, a list of database names is shown. ⢠If no table is given, all matching tables in the database are shown. ⢠If no column is given, all matching columns and column types in the table are shown. The output displays only the names of those databases, tables, or columns for which you have some privileges. If the last argument contains shell or SQL wildcard characters (*, ?, %, or _), only those names that are matched by the wildcard are shown. If a database name contains any underscores, those should be escaped with a backslash (some Unix shells require two) to get a list of the proper tables or columns. * and ? characters are converted into SQL % and _ wildcard characters. This might cause some confusion when you try to display the columns for a table with a _ in the name, because in this case, mysqlshow shows you only the table names that match the pattern. This is easily fixed by adding an extra % last on the command line as a separate argument. mysqlshow supports the following options, which can be specified on the command line or in the [mysqlshow] and [client] groups of an option file. For information about option files used by MySQL programs, see Section 4.2.2.2, âUsing Option Filesâ. ⢠--help, -? ââââââââââââââââââââââ¬âââââââââ âCommand-Line Format â --help â ââââââââââââââââââââââŽâââââââââ Display a help message and exit. ⢠--bind-address=ip_address ââââââââââââââââââââââ¬ââââââââââââââââââââââââââââ âCommand-Line Format â --bind-address=ip_address â ââââââââââââââââââââââŽââââââââââââââââââââââââââââ On a computer having multiple network interfaces, use this option to select which interface to use for connecting to the MySQL server. ⢠--character-sets-dir=dir_name ââââââââââââââââââââââ¬ââââââââââââââââââââââââââââ âCommand-Line Format â --character-sets-dir=path â ââââââââââââââââââââââŒâââââââââââââââââââââââââââ†âType â String â ââââââââââââââââââââââŒâââââââââââââââââââââââââââ†âDefault Value â [none] â ââââââââââââââââââââââŽââââââââââââââââââââââââââââ The directory where character sets are installed. See Section 10.15, âCharacter Set Configurationâ. ⢠--compress, -C ââââââââââââââââââââââ¬ââââââââââââââââââââââââ âCommand-Line Format â --compress[={OFF|ON}] â ââââââââââââââââââââââŒâââââââââââââââââââââââ†âDeprecated â Yes â ââââââââââââââââââââââŒâââââââââââââââââââââââ†âType â Boolean â ââââââââââââââââââââââŒâââââââââââââââââââââââ†âDefault Value â OFF â ââââââââââââââââââââââŽââââââââââââââââââââââââ Compress all information sent between the client and the server if possible. See Section 4.2.8, âConnection Compression Controlâ. This option is deprecated. Expect it to be removed in a future version of MySQL. See the section called âConfiguring Legacy Connection Compressionâ. ⢠--compression-algorithms=value ââââââââââââââââââââââ¬âââââââââââââââââââââââââââââââââ âCommand-Line Format â --compression-algorithms=value â ââââââââââââââââââââââŒââââââââââââââââââââââââââââââââ†âType â Set â ââââââââââââââââââââââŒââââââââââââââââââââââââââââââââ†âDefault Value â uncompressed â ââââââââââââââââââââââŒââââââââââââââââââââââââââââââââ†âValid Values â zlib zstd uncompressed â ââââââââââââââââââââââŽâââââââââââââââââââââââââââââââââ The permitted compression algorithms for connections to the server. The available algorithms are the same as for the protocol_compression_algorithms system variable. The default value is uncompressed. For more information, see Section 4.2.8, âConnection Compression Controlâ. ⢠--count ââââââââââââââââââââââ¬ââââââââââ âCommand-Line Format â --count â ââââââââââââââââââââââŽââââââââââ Show the number of rows per table. This can be slow for non-MyISAM tables. ⢠--debug[=debug_options], -# [debug_options] ââââââââââââââââââââââ¬ââââââââââââââââââââââââââ âCommand-Line Format â --debug[=debug_options] â ââââââââââââââââââââââŒâââââââââââââââââââââââââ†âType â String â ââââââââââââââââââââââŒâââââââââââââââââââââââââ†âDefault Value â d:t:o â ââââââââââââââââââââââŽââââââââââââââââââââââââââ Write a debugging log. A typical debug_options string is d:t:o,file_name. The default is d:t:o. This option is available only if MySQL was built using WITH_DEBUG. MySQL release binaries provided by Oracle are not built using this option. ⢠--debug-check ââââââââââââââââââââââ¬ââââââââââââââââ âCommand-Line Format â --debug-check â ââââââââââââââââââââââŒâââââââââââââââ†âType â Boolean â ââââââââââââââââââââââŒâââââââââââââââ†âDefault Value â FALSE â ââââââââââââââââââââââŽââââââââââââââââ Print some debugging information when the program exits. This option is available only if MySQL was built using WITH_DEBUG. MySQL release binaries provided by Oracle are not built using this option. ⢠--debug-info ââââââââââââââââââââââ¬âââââââââââââââ âCommand-Line Format â --debug-info â ââââââââââââââââââââââŒââââââââââââââ†âType â Boolean â ââââââââââââââââââââââŒââââââââââââââ†âDefault Value â FALSE â ââââââââââââââââââââââŽâââââââââââââââ Print debugging information and memory and CPU usage statistics when the program exits. This option is available only if MySQL was built using WITH_DEBUG. MySQL release binaries provided by Oracle are not built using this option. ⢠--default-character-set=charset_name ââââââââââââââââââââââ¬âââââââââââââââââââââââââââââââââââââââ âCommand-Line Format â --default-character-set=charset_name â ââââââââââââââââââââââŒââââââââââââââââââââââââââââââââââââââ†âType â String â ââââââââââââââââââââââŽâââââââââââââââââââââââââââââââââââââââ Use charset_name as the default character set. See Section 10.15, âCharacter Set Configurationâ. ⢠--default-auth=plugin ââââââââââââââââââââââ¬ââââââââââââââââââââââââ âCommand-Line Format â --default-auth=plugin â ââââââââââââââââââââââŒâââââââââââââââââââââââ†âType â String â ââââââââââââââââââââââŽââââââââââââââââââââââââ A hint about which client-side authentication plugin to use. See Section 6.2.17, âPluggable Authenticationâ. ⢠--defaults-extra-file=file_name ââââââââââââââââââââââ¬ââââââââââââââââââââââââââââââââââ âCommand-Line Format â --defaults-extra-file=file_name â ââââââââââââââââââââââŒâââââââââââââââââââââââââââââââââ†âType â File name â ââââââââââââââââââââââŽââââââââââââââââââââââââââââââââââ Read this option file after the global option file but (on Unix) before the user option file. If the file does not exist or is otherwise inaccessible, an error occurs. If file_name is not an absolute path name, it is interpreted relative to the current directory. For additional information about this and other option-file options, see Section 4.2.2.3, âCommand-Line Options that Affect Option-File Handlingâ. ⢠--defaults-file=file_name ââââââââââââââââââââââ¬ââââââââââââââââââââââââââââ âCommand-Line Format â --defaults-file=file_name â ââââââââââââââââââââââŒâââââââââââââââââââââââââââ†âType â File name â ââââââââââââââââââââââŽââââââââââââââââââââââââââââ Use only the given option file. If the file does not exist or is otherwise inaccessible, an error occurs. If file_name is not an absolute path name, it is interpreted relative to the current directory. Exception: Even with --defaults-file, client programs read .mylogin.cnf. For additional information about this and other option-file options, see Section 4.2.2.3, âCommand-Line Options that Affect Option-File Handlingâ. ⢠--defaults-group-suffix=str ââââââââââââââââââââââ¬ââââââââââââââââââââââââââââââ âCommand-Line Format â --defaults-group-suffix=str â ââââââââââââââââââââââŒâââââââââââââââââââââââââââââ†âType â String â ââââââââââââââââââââââŽââââââââââââââââââââââââââââââ Read not only the usual option groups, but also groups with the usual names and a suffix of str. For example, mysqlshow normally reads the [client] and [mysqlshow] groups. If this option is given as --defaults-group-suffix=_other, mysqlshow also reads the [client_other] and [mysqlshow_other] groups. For additional information about this and other option-file options, see Section 4.2.2.3, âCommand-Line Options that Affect Option-File Handlingâ. ⢠--enable-cleartext-plugin ââââââââââââââââââââââ¬ââââââââââââââââââââââââââââ âCommand-Line Format â --enable-cleartext-plugin â ââââââââââââââââââââââŒâââââââââââââââââââââââââââ†âType â Boolean â ââââââââââââââââââââââŒâââââââââââââââââââââââââââ†âDefault Value â FALSE â ââââââââââââââââââââââŽââââââââââââââââââââââââââââ Enable the mysql_clear_password cleartext authentication plugin. (See Section 6.4.1.4, âClient-Side Cleartext Pluggable Authenticationâ.) ⢠--get-server-public-key ââââââââââââââââââââââ¬ââââââââââââââââââââââââââ âCommand-Line Format â --get-server-public-key â ââââââââââââââââââââââŒâââââââââââââââââââââââââ†âType â Boolean â ââââââââââââââââââââââŽââââââââââââââââââââââââââ Request from the server the RSA public key that it uses for key pair-based password exchange. This option applies to clients that connect to the server using an account that authenticates with the caching_sha2_password authentication plugin. For connections by such accounts, the server does not send the public key to the client unless requested. The option is ignored for accounts that do not authenticate with that plugin. It is also ignored if RSA-based password exchange is not needed, as is the case when the client connects to the server using a secure connection. If --server-public-key-path=file_name is given and specifies a valid public key file, it takes precedence over --get-server-public-key. For information about the caching_sha2_password plugin, see Section 6.4.1.2, âCaching SHA-2 Pluggable Authenticationâ. ⢠--host=host_name, -h host_name ââââââââââââââââââââââ¬âââââââââââââââââââ âCommand-Line Format â --host=host_name â ââââââââââââââââââââââŒââââââââââââââââââ†âType â String â ââââââââââââââââââââââŒââââââââââââââââââ†âDefault Value â localhost â ââââââââââââââââââââââŽâââââââââââââââââââ Connect to the MySQL server on the given host. ⢠--keys, -k ââââââââââââââââââââââ¬âââââââââ âCommand-Line Format â --keys â ââââââââââââââââââââââŽâââââââââ Show table indexes. ⢠--login-path=name ââââââââââââââââââââââ¬ââââââââââââââââââââ âCommand-Line Format â --login-path=name â ââââââââââââââââââââââŒâââââââââââââââââââ†âType â String â ââââââââââââââââââââââŽââââââââââââââââââââ Read options from the named login path in the .mylogin.cnf login path file. A âlogin pathâ is an option group containing options that specify which MySQL server to connect to and which account to authenticate as. To create or modify a login path file, use the mysql_config_editor utility. See mysql_config_editor(1). For additional information about this and other option-file options, see Section 4.2.2.3, âCommand-Line Options that Affect Option-File Handlingâ. ⢠--no-login-paths ââââââââââââââââââââââ¬âââââââââââââââââââ âCommand-Line Format â --no-login-paths â ââââââââââââââââââââââŽâââââââââââââââââââ Skips reading options from the login path file. See --login-path for related information. For additional information about this and other option-file options, see Section 4.2.2.3, âCommand-Line Options that Affect Option-File Handlingâ. ⢠--no-defaults ââââââââââââââââââââââ¬ââââââââââââââââ âCommand-Line Format â --no-defaults â ââââââââââââââââââââââŽââââââââââââââââ Do not read any option files. If program startup fails due to reading unknown options from an option file, --no-defaults can be used to prevent them from being read. The exception is that the .mylogin.cnf file is read in all cases, if it exists. This permits passwords to be specified in a safer way than on the command line even when --no-defaults is used. To create .mylogin.cnf, use the mysql_config_editor utility. See mysql_config_editor(1). For additional information about this and other option-file options, see Section 4.2.2.3, âCommand-Line Options that Affect Option-File Handlingâ. ⢠--password[=password], -p[password] ââââââââââââââââââââââ¬ââââââââââââââââââââââââ âCommand-Line Format â --password[=password] â ââââââââââââââââââââââŒâââââââââââââââââââââââ†âType â String â ââââââââââââââââââââââŽââââââââââââââââââââââââ The password of the MySQL account used for connecting to the server. The password value is optional. If not given, mysqlshow prompts for one. If given, there must be no space between --password= or -p and the password following it. If no password option is specified, the default is to send no password. Specifying a password on the command line should be considered insecure. To avoid giving the password on the command line, use an option file. See Section 6.1.2.1, âEnd-User Guidelines for Password Securityâ. To explicitly specify that there is no password and that mysqlshow should not prompt for one, use the --skip-password option. ⢠--password1[=pass_val] The password for multifactor authentication factor 1 of the MySQL account used for connecting to the server. The password value is optional. If not given, mysqlshow prompts for one. If given, there must be no space between --password1= and the password following it. If no password option is specified, the default is to send no password. Specifying a password on the command line should be considered insecure. To avoid giving the password on the command line, use an option file. See Section 6.1.2.1, âEnd-User Guidelines for Password Securityâ. To explicitly specify that there is no password and that mysqlshow should not prompt for one, use the --skip-password1 option. --password1 and --password are synonymous, as are --skip-password1 and --skip-password. ⢠--password2[=pass_val] The password for multifactor authentication factor 2 of the MySQL account used for connecting to the server. The semantics of this option are similar to the semantics for --password1; see the description of that option for details. ⢠--password3[=pass_val] The password for multifactor authentication factor 3 of the MySQL account used for connecting to the server. The semantics of this option are similar to the semantics for --password1; see the description of that option for details. ⢠--pipe, -W ââââââââââââââââââââââ¬âââââââââ âCommand-Line Format â --pipe â ââââââââââââââââââââââŒââââââââ†âType â String â ââââââââââââââââââââââŽâââââââââ On Windows, connect to the server using a named pipe. This option applies only if the server was started with the named_pipe system variable enabled to support named-pipe connections. In addition, the user making the connection must be a member of the Windows group specified by the named_pipe_full_access_group system variable. ⢠--plugin-dir=dir_name ââââââââââââââââââââââ¬ââââââââââââââââââââââââ âCommand-Line Format â --plugin-dir=dir_name â ââââââââââââââââââââââŒâââââââââââââââââââââââ†âType â Directory name â ââââââââââââââââââââââŽââââââââââââââââââââââââ The directory in which to look for plugins. Specify this option if the --default-auth option is used to specify an authentication plugin but mysqlshow does not find it. See Section 6.2.17, âPluggable Authenticationâ. ⢠--port=port_num, -P port_num ââââââââââââââââââââââ¬ââââââââââââââââââ âCommand-Line Format â --port=port_num â ââââââââââââââââââââââŒâââââââââââââââââ†âType â Numeric â ââââââââââââââââââââââŒâââââââââââââââââ†âDefault Value â 3306 â ââââââââââââââââââââââŽââââââââââââââââââ For TCP/IP connections, the port number to use. ⢠--print-defaults ââââââââââââââââââââââ¬âââââââââââââââââââ âCommand-Line Format â --print-defaults â ââââââââââââââââââââââŽâââââââââââââââââââ Print the program name and all options that it gets from option files. For additional information about this and other option-file options, see Section 4.2.2.3, âCommand-Line Options that Affect Option-File Handlingâ. ⢠--protocol={TCP|SOCKET|PIPE|MEMORY} ââââââââââââââââââââââ¬âââââââââââââââââââââââââ âCommand-Line Format â --protocol=type â ââââââââââââââââââââââŒââââââââââââââââââââââââ†âType â String â ââââââââââââââââââââââŒââââââââââââââââââââââââ†âDefault Value â [see text] â ââââââââââââââââââââââŒââââââââââââââââââââââââ†âValid Values â TCP SOCKET PIPE â â â MEMORY â ââââââââââââââââââââââŽâââââââââââââââââââââââââ The transport protocol to use for connecting to the server. It is useful when the other connection parameters normally result in use of a protocol other than the one you want. For details on the permissible values, see Section 4.2.7, âConnection Transport Protocolsâ. ⢠--server-public-key-path=file_name ââââââââââââââââââââââ¬âââââââââââââââââââââââââââââââââââââ âCommand-Line Format â --server-public-key-path=file_name â ââââââââââââââââââââââŒââââââââââââââââââââââââââââââââââââ†âType â File name â ââââââââââââââââââââââŽâââââââââââââââââââââââââââââââââââââ The path name to a file in PEM format containing a client-side copy of the public key required by the server for RSA key pair-based password exchange. This option applies to clients that authenticate with the sha256_password or caching_sha2_password authentication plugin. This option is ignored for accounts that do not authenticate with one of those plugins. It is also ignored if RSA-based password exchange is not used, as is the case when the client connects to the server using a secure connection. If --server-public-key-path=file_name is given and specifies a valid public key file, it takes precedence over --get-server-public-key. For sha256_password, this option applies only if MySQL was built using OpenSSL. For information about the sha256_password and caching_sha2_password plugins, see Section 6.4.1.3, âSHA-256 Pluggable Authenticationâ, and Section 6.4.1.2, âCaching SHA-2 Pluggable Authenticationâ. ⢠--shared-memory-base-name=name ââââââââââââââââââââââ¬âââââââââââââââââââââââââââââââââ âCommand-Line Format â --shared-memory-base-name=name â ââââââââââââââââââââââŒââââââââââââââââââââââââââââââââ†âPlatform Specific â Windows â ââââââââââââââââââââââŽâââââââââââââââââââââââââââââââââ On Windows, the shared-memory name to use for connections made using shared memory to a local server. The default value is MYSQL. The shared-memory name is case-sensitive. This option applies only if the server was started with the shared_memory system variable enabled to support shared-memory connections. ⢠--show-table-type, -t ââââââââââââââââââââââ¬ââââââââââââââââââââ âCommand-Line Format â --show-table-type â ââââââââââââââââââââââŽââââââââââââââââââââ Show a column indicating the table type, as in SHOW FULL TABLES. The type is BASE TABLE or VIEW. ⢠--socket=path, -S path ââââââââââââââââââââââ¬âââââââââââââââââââââââââââââââââ âCommand-Line Format â --socket={file_name|pipe_name} â ââââââââââââââââââââââŒââââââââââââââââââââââââââââââââ†âType â String â ââââââââââââââââââââââŽâââââââââââââââââââââââââââââââââ For connections to localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use. On Windows, this option applies only if the server was started with the named_pipe system variable enabled to support named-pipe connections. In addition, the user making the connection must be a member of the Windows group specified by the named_pipe_full_access_group system variable. ⢠--ssl* Options that begin with --ssl specify whether to connect to the server using encryption and indicate where to find SSL keys and certificates. See the section called âCommand Options for Encrypted Connectionsâ. ⢠--ssl-fips-mode={OFF|ON|STRICT} ââââââââââââââââââââââ¬ââââââââââââââââââââââââââââââââââ âCommand-Line Format â --ssl-fips-mode={OFF|ON|STRICT} â ââââââââââââââââââââââŒâââââââââââââââââââââââââââââââââ†âDeprecated â Yes â ââââââââââââââââââââââŒâââââââââââââââââââââââââââââââââ†âType â Enumeration â ââââââââââââââââââââââŒâââââââââââââââââââââââââââââââââ†âDefault Value â OFF â ââââââââââââââââââââââŒâââââââââââââââââââââââââââââââââ†âValid Values â OFF ON STRICT â ââââââââââââââââââââââŽââââââââââââââââââââââââââââââââââ Controls whether to enable FIPS mode on the client side. The --ssl-fips-mode option differs from other --ssl-xxx options in that it is not used to establish encrypted connections, but rather to affect which cryptographic operations to permit. See Section 6.8, âFIPS Supportâ. These --ssl-fips-mode values are permitted: ⢠OFF: Disable FIPS mode. ⢠ON: Enable FIPS mode. ⢠STRICT: Enable âstrictâ FIPS mode. Note If the OpenSSL FIPS Object Module is not available, the only permitted value for --ssl-fips-mode is OFF. In this case, setting --ssl-fips-mode to ON or STRICT causes the client to produce a warning at startup and to operate in non-FIPS mode. This option is deprecated. Expect it to be removed in a future version of MySQL. ⢠--status, -i ââââââââââââââââââââââ¬âââââââââââ âCommand-Line Format â --status â ââââââââââââââââââââââŽâââââââââââ Display extra information about each table. ⢠--tls-ciphersuites=ciphersuite_list ââââââââââââââââââââââ¬ââââââââââââââââââââââââââââââââââââââ âCommand-Line Format â --tls-ciphersuites=ciphersuite_list â ââââââââââââââââââââââŒâââââââââââââââââââââââââââââââââââââ†âType â String â ââââââââââââââââââââââŽââââââââââââââââââââââââââââââââââââââ The permissible ciphersuites for encrypted connections that use TLSv1.3. The value is a list of one or more colon-separated ciphersuite names. The ciphersuites that can be named for this option depend on the SSL library used to compile MySQL. For details, see Section 6.3.2, âEncrypted Connection TLS Protocols and Ciphersâ. ⢠--tls-sni-servername=server_name ââââââââââââââââââââââ¬âââââââââââââââââââââââââââââââââââ âCommand-Line Format â --tls-sni-servername=server_name â ââââââââââââââââââââââŒââââââââââââââââââââââââââââââââââ†âType â String â ââââââââââââââââââââââŽâââââââââââââââââââââââââââââââââââ When specified, the name is passed to the libmysqlclient C API library using the MYSQL_OPT_TLS_SNI_SERVERNAME option of mysql_options(). The server name is not case-sensitive. To show which server name the client specified for the current session, if any, check the Tls_sni_server_name status variable. Server Name Indication (SNI) is an extension to the TLS protocol (OpenSSL must be compiled using TLS extensions for this option to function). The MySQL implementation of SNI represents the client-side only. ⢠--tls-version=protocol_list ââââââââââââââââââââââ¬ââââââââââââââââââââââââââââââââ âCommand-Line Format â --tls-version=protocol_list â ââââââââââââââââââââââŒâââââââââââââââââââââââââââââââ†âType â String â ââââââââââââââââââââââŒâââââââââââââââââââââââââââââââ†âDefault Value â TLSv1,TLSv1.1,TLSv1.2,TLSv1.3 â â â (OpenSSL 1.1.1 or higher) â â â TLSv1,TLSv1.1,TLSv1.2 â â â (otherwise) â ââââââââââââââââââââââŽââââââââââââââââââââââââââââââââ The permissible TLS protocols for encrypted connections. The value is a list of one or more comma-separated protocol names. The protocols that can be named for this option depend on the SSL library used to compile MySQL. For details, see Section 6.3.2, âEncrypted Connection TLS Protocols and Ciphersâ. ⢠--user=user_name, -u user_name ââââââââââââââââââââââ¬ââââââââââââââââââââ âCommand-Line Format â --user=user_name, â ââââââââââââââââââââââŒâââââââââââââââââââ†âType â String â ââââââââââââââââââââââŽââââââââââââââââââââ The user name of the MySQL account to use for connecting to the server. ⢠--verbose, -v ââââââââââââââââââââââ¬ââââââââââââ âCommand-Line Format â --verbose â ââââââââââââââââââââââŽââââââââââââ Verbose mode. Print more information about what the program does. This option can be used multiple times to increase the amount of information. ⢠--version, -V ââââââââââââââââââââââ¬ââââââââââââ âCommand-Line Format â --version â ââââââââââââââââââââââŽââââââââââââ Display version information and exit. ⢠--zstd-compression-level=level ââââââââââââââââââââââ¬âââââââââââââââââââââââââââââ âCommand-Line Format â --zstd-compression-level=# â ââââââââââââââââââââââŒââââââââââââââââââââââââââââ†âType â Integer â ââââââââââââââââââââââŽâââââââââââââââââââââââââââââ The compression level to use for connections to the server that use the zstd compression algorithm. The permitted levels are from 1 to 22, with larger values indicating increasing levels of compression. The default zstd compression level is 3. The compression level setting has no effect on connections that do not use zstd compression. For more information, see Section 4.2.8, âConnection Compression Controlâ. COPYRIGHT Copyright © 1997, 2023, Oracle and/or its affiliates. This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see http://www.gnu.org/licenses/. SEE ALSO For more information, please refer to the MySQL Reference Manual, which may already be installed locally and which is also available online at http://dev.mysql.com/doc/. AUTHOR Oracle Corporation (http://dev.mysql.com/). MySQL 8.3 11/23/2023 MYSQLSHOW(1)
|
mysqlshow - display database, table, and column information
|
mysqlshow [options] [db_name [tbl_name [col_name]]]
| null | null |
gtest
|
Exit with the status determined by EXPRESSION. --help display this help and exit --version output version information and exit An omitted EXPRESSION defaults to false. Otherwise, EXPRESSION is true or false and sets exit status. It is one of: ( EXPRESSION ) EXPRESSION is true ! EXPRESSION EXPRESSION is false EXPRESSION1 -a EXPRESSION2 both EXPRESSION1 and EXPRESSION2 are true EXPRESSION1 -o EXPRESSION2 either EXPRESSION1 or EXPRESSION2 is true -n STRING the length of STRING is nonzero STRING equivalent to -n STRING -z STRING the length of STRING is zero STRING1 = STRING2 the strings are equal STRING1 != STRING2 the strings are not equal INTEGER1 -eq INTEGER2 INTEGER1 is equal to INTEGER2 INTEGER1 -ge INTEGER2 INTEGER1 is greater than or equal to INTEGER2 INTEGER1 -gt INTEGER2 INTEGER1 is greater than INTEGER2 INTEGER1 -le INTEGER2 INTEGER1 is less than or equal to INTEGER2 INTEGER1 -lt INTEGER2 INTEGER1 is less than INTEGER2 INTEGER1 -ne INTEGER2 INTEGER1 is not equal to INTEGER2 FILE1 -ef FILE2 FILE1 and FILE2 have the same device and inode numbers FILE1 -nt FILE2 FILE1 is newer (modification date) than FILE2 FILE1 -ot FILE2 FILE1 is older than FILE2 -b FILE FILE exists and is block special -c FILE FILE exists and is character special -d FILE FILE exists and is a directory -e FILE FILE exists -f FILE FILE exists and is a regular file -g FILE FILE exists and is set-group-ID -G FILE FILE exists and is owned by the effective group ID -h FILE FILE exists and is a symbolic link (same as -L) -k FILE FILE exists and has its sticky bit set -L FILE FILE exists and is a symbolic link (same as -h) -N FILE FILE exists and has been modified since it was last read -O FILE FILE exists and is owned by the effective user ID -p FILE FILE exists and is a named pipe -r FILE FILE exists and the user has read access -s FILE FILE exists and has a size greater than zero -S FILE FILE exists and is a socket -t FD file descriptor FD is opened on a terminal -u FILE FILE exists and its set-user-ID bit is set -w FILE FILE exists and the user has write access -x FILE FILE exists and the user has execute (or search) access Except for -h and -L, all FILE-related tests dereference symbolic links. Beware that parentheses need to be escaped (e.g., by backslashes) for shells. INTEGER may also be -l STRING, which evaluates to the length of STRING. NOTE: Binary -a and -o are inherently ambiguous. Use 'test EXPR1 && test EXPR2' or 'test EXPR1 || test EXPR2' instead. NOTE: [ honors the --help and --version options, but test does not. test treats each of those as it treats any other nonempty STRING. NOTE: your shell may have its own version of test and/or [, which usually supersedes the version described here. Please refer to your shell's documentation for details about the options it supports. AUTHOR Written by Kevin Braunsdorf and Matthew Bradburn. REPORTING BUGS GNU coreutils online help: <https://www.gnu.org/software/coreutils/> Report any translation bugs to <https://translationproject.org/team/> COPYRIGHT Copyright © 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO access(2) Full documentation <https://www.gnu.org/software/coreutils/test> or available locally via: info '(coreutils) test invocation' GNU coreutils 9.3 April 2023 TEST(1)
|
test - check file types and compare values
|
test EXPRESSION test [ EXPRESSION ] [ ] [ OPTION
| null | null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.