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 |
|---|---|---|---|---|---|
blackd
| null | null | null | null | null |
udp_proxy
| null | null | null | null | null |
out123
|
out123 reads raw PCM data (in host byte order) from standard input and plays it on the audio device specified by given options. Alternatively, it can generate periodic or random signals for playback itself.
|
out123 - send raw PCM audio or a waveform pattern to an output device
|
cat audio.raw | out123 [ - ] [ options ] out123 [ options ] filename [ filename ... ] out123 --wave-freq freq1[,freq2,...] [ options ] out123 --source geiger [ options ]
|
out123 options may be either the traditional POSIX one letter options, or the GNU style long options. POSIX style options start with a single '-', while GNU long options start with '--'. Option arguments (if needed) follow separated by whitespace (not '='). Note that some options can be absent from your installation when disabled in the build process. --name name Set the name of this instance, possibly used in various places. This sets the client name for JACK output. -o module, --output module Select audio output module. You can provide a comma-separated list to use the first one that works. Also see -a. --list-modules List the available modules. --list-devices List the available output devices for given output module. If there is no functionality to list devices in the chosen module, an error will be printed and out123 will exit with a non-zero code. -a dev, --audiodevice dev Specify the audio device to use. The default as well as the possible values depend on the active output. For the JACK output, a comma-separated list of ports to connect to (for each channel) can be specified. -s, --stdout The audio samples are written to standard output, instead of playing them through the audio device. The output format is the same as the input ... so in this mode, out123 acts similar the standard tool cat, possibly with some conversions involved. This shortcut is equivalent to '-o raw -a -'. -S, --STDOUT This variant additionally writes the data to stdout, while still playing it on the output device. So it is more like some flavour of tee than a cat. -O file, --outfile Write raw output into a file (instead of simply redirecting standard output to a file with the shell). This shortcut is equivalent to '-o raw -a file'. -w file, --wav Write output as WAV file file , or standard output if - is or the empty string used as file name. You can also use --au and --cdr for AU and CDR format, respectively. Note that WAV/AU writing to non-seekable files or redirected stdout needs some thought. The header is written with the first actual data. The result of decoding nothing to WAV/AU is a file consisting just of the header when it is seekable and really nothing when not (not even a header). Correctly writing data with prophetic headers to stdout is no easy business. This shortcut is equivalent to '-o wav -a file'. --au file Write to file in SUN audio format. If - or the empty string is used as the filename, the AU file is written to stdout. See paragraph about WAV writing for header fun with non-seekable streams. This shortcut is equivalent to '-o au -a file'. --cdr file Write to file as a CDR (CD-ROM audio, more correctly CDDA for Compact Disc Digital Audio). If - is or the empty string used as the filename, the CDR file is written to stdout. This shortcut is equivalent to '-o cdr -a file'. -r rate, --rate rate Set sample rate in Hz (default: 44100). If this does not match the actual input sampling rate, you get changed pitch. Might be intentional;-) -R rate, --inputrate rate Set input sample rate to a different value. This triggers resampling if the output rate is indeed different. See --resample. --speed factor Speed up/down playback by that factor using resampling. See --resample. --resample method This chooses the method for resampling between differing sampling rates or to apply a change in tempo. You can choose between two variants of the syn123 resampler: fine (the default) and dirty. The fine one features 108 dB dynamic range and at worst-case 84% bandwidth. The dirty one uses a bit less CPU time (not that much, though) by reducing the dynamic range to 72 dB with worst-case bandwidth of 85%. The exact properties vary with the sampling rate ratio, as there is interpolation of filter coefficients involved. -c count, --channels count Set channel count to given value. -C count, --inputch count Set input channel count to a differnt value than for output. This probably means you want some remixing. Also see --mix. -e enc, --encoding enc Choose output sample encoding. Possible values look like f32 (32-bit floating point), s32 (32-bit signed integer), u32 (32-bit unsigned integer) and the variants with different numbers of bits (s24, u24, s16, u16, s8, u8) and also special variants like ulaw and alaw 8-bit. See the output of out123's longhelp for actually available encodings. Default is s16. --endian choice Select output endianess (byte order). Choice is big, little, or native, which is the default. The processing can only work in native mode, so you need to specify input or output byte order if that does not match your machine. This also sets the input endianess if that is not set separately. See also --inputend and --byteswap. -E enc, --inputenc enc Specify input encoding different from output encoding for conversion. --inputend choice Select input endianess (byte order). By default it is the same as output byte order. See --endian. --byteswap A switch to trigger swapping of byte order just before output, after any other transformations. This works on top of any endianess you specify with -m, --mono Set for single-channel audio (default is two channels, stereo). --stereo Select stereo output (2 channels, default). --list-encodings List known encoding short and long names to standard output. --mix matrix Specify a mixing matrix between input and output channels as linear factors, comma separated list for the input channel factors for output channel 1, then output channel 2, and so forth. The default is a unit matrix if channel counts match, so for 3 channels the equivalent of both channels with halved amplitude, so '--mix 0.5,0.5'. For splitting mono to stereo, it is '--mix 1,1' top keep the symmetry. --filter coeff Apply digital filter(s) before pre-amplification (see --preamp) with the coefficient list coeff as b_0,...,b_N,a_0,...,a_N where a_0=1 is mandatory and perhaps helps orientation a bit. Multiple filters are separated by ':'. -P dbvalue --preamp dbvalue Enable a pre-amplification stage that amplifies the signal with the given value in dB before output. --offset value Apply a PCM offset (floating point value scaled in [-1:1] in the pre-amplification stage. Normally, you would do that to correct a known DC offset in a recording. --clip mode Select clipping mode: 'soft' or 'hard' for forced clipping also for floating point output, 'implicit' (default) for implied hard clipping during conversion where necessary. --dither Enable dithering for conversions to integer. If you insist. This is just some un-spectacular TPDF dither. For some people, that is not fancy enough. Most people cannot be bothered that way or the other. --test-format Check if given format is supported by given driver and device (in command line before encountering this), silently returning 0 as exit value if it is the case. --test-encodings Print out the short names of encodings supported with the current setup. --query-format If the selected driver and device communicate some default accepted format, print out a command line fragment for out123 setting that format, always in that order: --rate <r> --channels <c> --encoding <e> -o h, --headphones Direct audio output to the headphone connector (some hardware only; AIX, HP, SUN). -o s, --speaker Direct audio output to the speaker (some hardware only; AIX, HP, SUN). -o l, --lineout Direct audio output to the line-out connector (some hardware only; AIX, HP, SUN). -b size, --buffer size Use an audio output buffer of size Kbytes. This is useful to bypass short periods of heavy system activity, which would normally cause the audio output to be interrupted. You should specify a buffer size of at least 1024 (i.e. 1 Mb, which equals about 6 seconds of usual audio data) or more; less than about 300 does not make much sense. The default is 0, which turns buffering off. --preload fraction Wait for the buffer to be filled to fraction before starting playback (fraction between 0 and 1). You can tune this prebuffering to either get sound faster to your ears or safer uninterrupted web radio. Default is 0.2 (changed from 1 since version 1.23). --devbuffer seconds Set device buffer in seconds; <= 0 means default value. This is the small buffer between the application and the audio backend, possibly directly related to hardware buffers. --timelimit samples Set playback time limit in PCM samples if set to a value greater than zero. out123 will stop reading from stdin or playing from the generated wave table after reaching that number of samples. --seconds seconds Set time limit in seconds instead. --source name Choose the signal source: 'file' (default) for playback of the given file(s) on the command line or standard input if there are none, or one of the generators 'wave' (see --wave-freq), geiger (see --geiger-activity), or just 'white' for some white noise. --wave-freq frequencies Set wave generator frequency or list of those with comma separation for enabling a generated test signal instead of standard input. Empty values repeat the previous one. --wave-pat patterns Set the waveform patterns of the generated waves as comma- separated list. Choices include sine, square, triangle, sawtooth, gauss, pulse, and shot. Empty values repeat the previous one. --wave-phase phases Set waveform phase shift(s) as comma-separated list, negative values inverting the pattern in time and empty value repeating the previous. There is also --wave-direction overriding the negative bit. --wave-direction Set wave direction explicitly (the sign counts). --wave-sweep frequency Sweep a generated wave to the given frequency, from first one specified for --wave-freq, using the first wave pattern and direction, too. --sweep-time seconds Set frequency sweep duration in seconds if > 0. This defaults to the configured time limit if set, otherwise one second, as endless sweeps are not sensible. --sweep-count count Set timelimit to exactly produce that many (smooth) sweeps --sweep-type type Set sweep type: lin(ear) for linear, qua(d) (default) for quadratic, or exp(onential) for an exponential change of frequency with time. --sweep-hard Disable post-sweep smoothing for periodicity. --genbuffer bytes Set the buffer size (limit) for signal generators, if > 0 (default), this enforces a periodic buffer also for non-periodic signals, benefit: less runtime CPU overhead, as everything is precomputed as enforced periodic signal. --wave-limit samples This is an alias for --genbuffer. --pink-rows number Activate pink noise source and choose rows for the algorithm (<1 chooses default). The generator follows code provided by Phil Burk (http://softsynth.com) and uses the Gardner method. --geiger-activity number This configures the simulation of a Geiger-Mueller counter as source, with the given numer as average events per second. Play with it. It's fun! -t, --test Test mode. The audio stream is read, but no output occurs. -v, --verbose Increase the verbosity level. -q, --quiet Quiet. Suppress diagnostic messages. --aggressive Tries to get higher priority -T, --realtime Tries to gain realtime priority. This option usually requires root privileges to have any effect. -?, --help Shows short usage instructions. --longhelp Shows long usage instructions. --version Print the version string. AUTHORS Maintainer: Thomas Orgis <maintainer@mpg123.org>, <thomas@orgis.org> Creator (ancestry of code inside mpg123): Michael Hipp Uses code or ideas from various people, see the AUTHORS file accompanying the source code. LICENSE out123 is licensed under the GNU Lesser/Library General Public License, LGPL, version 2.1 . WEBSITE http://www.mpg123.org http://sourceforge.net/projects/mpg123 26 Apr 2020 out123(1)
| null |
perl5.38.2
| null | null | null | null | null |
gdbmtool
|
The gdbmtool utility allows you to view and modify an existing GDBM database or to create a new one. The DBFILE argument supplies the name of the database to open. If not supplied, the default name junk.gdbm is used instead. If the named database does not exist, it will be created. An existing database can be cleared (i.e. all records removed from it) using the --newdb option (see below). Unless the -N (--norc) option is given, after startup gdbmtool looks for file named .gdbmtoolrc first in the current working directory, and, if not found there, in the home directory of the user who started the program. If found, this file is read and interpreted as a list of gdbmtool commands. Then gdbmtool starts a loop, in which it reads commands from the standard input, executes them and prints the results on the standard output. If the standard input is attached to a console, the program runs in interactive mode. The program terminates when the quit command is given, or end-of-file is detected on its standard input. Commands can also be specified in the command line, after the DBFILE argument. In this case, they will be interpreted without attempting to read more commands from the standard input. If several commands are supplied, they must be separated by semicolons (properly escaped or quoted, in order to prevent them from being interpreted by the shell). A gdbmtool command consists of a command verb, optionally followed by one or more arguments, separated by any amount of white space. A command verb can be entered either in full or in an abbreviated form, as long as that abbreviation does not match any other verb. Any sequence of non-whitespace characters appearing after the command verb forms an argument. If the argument contains whitespace or unprintable characters it must be enclosed in double quotes. Within double quotes the usual escape sequences are understood, as shown in the table below: Escape Expansion \a Audible bell character (ASCII 7) \b Backspace character (ASCII 8) \f Form-feed character (ASCII 12) \n Newline character (ASCII 10) \r Carriage return character (ASCII 13) \t Horizontal tabulation character (ASCII 9) \v Vertical tabulation character (ASCII 11) \\ Single slash In addition, a backslash immediately followed by the end-of-line character effectively removes that character, allowing to split long arguments over several input lines.
|
gdbmtool - examine and modify a GDBM database
|
gdbmtool [-lmNnqrs] [-b SIZE] [-c SIZE] [-f FILE] [--block-size=SIZE] [--cache-size=SIZE] [--file FILE] [--newdb] [--no-lock] [--no-mmap] [--norc] [--quiet] [--read-only] [--synchronize] [DBFILE] [COMMAND [; COMMAND...]] gdbmtool [-Vh] [--help] [--usage] [--version]
|
-b, --block-size=SIZE Set block size. -c, --cache-size=SIZE Set cache size. -f, --file=FILE Read commands from FILE, instead of from the standard input. -l, --no-lock Disable file locking. -m, --no-mmap Do not use mmap(2). -n, --newdb Create the database, truncating it if it already exists. -q, --quiet Don't print initial banner. -r, --read-only Open database in read-only mode. -s, --synchronize Synchronize to disk after each write. -h, --help Print a short usage summary. --usage Print a list of available options. -V, --version Print program version SHELL COMMANDS avail Print the avail list. bucket NUM Print the bucket number NUM and set is as the current one. cache Print the bucket cache. close Close the currently open database. count Print the number of entries in the database. current Print the current bucket. delete KEY Delete record with the given KEY. dir Print hash directory. downgrade Downgrade the database from the extended numsync format to the standard format. export FILE-NAME [truncate] [binary|ascii] Export the database to the flat file FILE-NAME. This is equivalent to gdbm_dump(1). This command will not overwrite an existing file, unless the truncate parameter is also given. Another optional parameter determines the type of the dump (*note Flat files::). By default, ASCII dump will be created. fetch KEY Fetch and display the record with the given KEY. first Fetch and display the first record in the database. Subsequent records can be fetched using the next command (see below). hash KEY Compute and display the hash value for the given KEY. header Print file header. help or ? Print a concise command summary, showing each command letter and verb with its parameters and a short description of what it does. Optional arguments are enclosed in square brackets. history Shows the command history list with line numbers. This command is available only if the program was compiled with GNU Readline. history COUNT. Shows COUNT latest commands from the command history. history N COUNT. Shows COUNT commands from the command history starting with Nth command. import FILE-NAME [replace] [nometa] Import data from a flat dump file FILE-NAME. If the replace argument is given, any records with the same keys as the already existing ones will replace them. The nometa argument turns off restoring meta-information from the dump file. list List the contents of the database. next [KEY] Sequential access: fetch and display the next record. If the KEY is given, the record following the one with this key will be fetched. open FILE Open the database file FILE. If successful, any previously open database is closed. Otherwise, if the operation fails, the currently opened database remains unchanged. This command takes additional information from the variables open, lock, mmap, and sync. See the section VARIABLES, for a detailed description of these. quit Close the database and quit the utility. reorganize Reorganize the database. set [VAR=VALUE...] Without arguments, lists variables and their values. If arguments are specified, sets variables. Boolean variables can be set by specifying variable name, optionally prefixed with no, to set it to false. snapshot FILE FILE Analyzes two database snapshots and selects the most recent of them. In case of error, prints a detailed diagnostics. Use this command to manually recover from a crash. For details, please refer to the chapter Crash Tolerance in the GDBM manual. source FILE Read commands from the given FILE. status Print current program status. store KEY DATA Store the DATA with the given KEY in the database. If the KEY already exists, its data will be replaced. sync Synchronize the database file with the disk storage. upgrade Upgrade the database from the standard to the extended numsync format. unset VARIABLE... Unsets listed variables. version Print the version of gdbm. DATA DEFINITIONS The define statement provides a mechanism for defining key or content structures. It is similar to the C struct declaration: define key|content { defnlist } The defnlist is a comma-separated list of member declarations. Within defnlist the newline character looses its special meaning as the command terminator, so each declaration can appear on a separate line and arbitrary number of comments can be inserted to document the definition. Each declaration has one of the following formats type name type name [N] where type is a data type and name is the member name. The second format defines the member name as an array of N elements of type. The supported types are: type meaning char single byte (signed) short signed short integer ushort unsigned short integer int signed integer unsigned unsigned integer uint ditto long signed long integer ulong unsigned long integer llong signed long long integer ullong unsigned long long integer float a floating point number double double-precision floating point number string array of characters (see the NOTE below) stringz null-terminated string of characters The following alignment declarations can be used within defnlist: offset N The next member begins at offset N. pad N Add N bytes of padding to the previous member. For example: define content { int status, pad 8, char id[3], stringz name } To define data consisting of a single data member, the following simplified construct can be used: define key|content type where type is one of the types discussed above. NOTE: The string type can reasonably be used only if it is the last or the only member of the data structure. That's because it provides no information about the number of elements in the array, so it is interpreted to contain all bytes up to the end of the datum. VARIABLES confirm, boolean Whether to ask for confirmation before certain destructive operations, such as truncating the existing database. Default is true. ps1, string Primary prompt string. Its value can contain conversion specifiers, consisting of the % character followed by another character. These specifiers are expanded in the resulting prompt as follows: Sequence Expansion %f name of the db file %p program name %P package name (gdbm) %_ horizontal space (ASCII 32) %v program version %% % The default prompt is %p>%_. ps2, string Secondary prompt. See ps1 for a description of its value. This prompt is displayed before reading the second and subsequent lines of a multi-line command. The default value is %_>%_. delim1, string A string used to delimit fields of a structured datum on output (see the section DATA DEFINITIONS). Default is , (a comma). This variable cannot be unset. delim2, string A string used to delimit array items when printing a structured datum. Default is , (a comma). This variable cannot be unset. pager, string The name and command line of the pager program to pipe output to. This program is used in interactive mode when the estimated number of output lines is greater then the number of lines on your screen. The default value is inherited from the environment variable PAGER. Unsetting this variable disables paging. quiet, boolean Whether to display welcome banner at startup. This variable should be set in a startup script file. The following variables control how the database is opened: cachesize, numeric Sets the cache size. By default this variable is not set. blocksize, numeric Sets the block size. Unset by default. open, string Open mode. The following values are allowed: newdb Truncate the database if it exists or create a new one. Open it in read-write mode. wrcreat or rw Open the database in read-write mode. Create it if it does not exist. This is the default. reader or readonly Open the database in read-only mode. Signal an error if it does not exist. filemode, octal Sets the file mode for newly created database files. Default is 0644. lock, boolean Lock the database. This is the default. mmap, boolean Use memory mapping. This is the default. coalesce, boolean When set, this option causes adjacent free blocks to be merged which allows for more efficient memory management at the expense of a certain increase in CPU usage. centfree, boolean Enables central free block pool. This causes all free blocks of space to be placed in the global pool, thereby speeding up the allocation of data space. SEE ALSO gdbm_dump(1), gdbm_load(1), gdbm(3). REPORTING BUGS Report bugs to <bug-gdbm@gnu.org>. COPYRIGHT Copyright © 2013-2021 Free Software Foundation, Inc License GPLv3+: GNU GPL version 3 or later <http://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. GDBM August 1, 2021 GDBMTOOL(1)
| null |
gnproc
|
Print the number of processing units available to the current process, which may be less than the number of online processors --all print the number of installed processors --ignore=N if possible, exclude N processing units --help display this help and exit --version output version information and exit AUTHOR Written by Giuseppe Scrivano. 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/nproc> or available locally via: info '(coreutils) nproc invocation' GNU coreutils 9.3 April 2023 NPROC(1)
|
nproc - print the number of processing units available
|
nproc [OPTION]...
| null | null |
msgexec
|
Applies a command to all translations of a translation catalog. The COMMAND can be any program that reads a translation from standard input. It is invoked once for each translation. Its output becomes msgexec's output. msgexec's return code is the maximum return code across all invocations. A special builtin command called '0' outputs the translation, followed by a null byte. The output of "msgexec 0" is suitable as input for "xargs -0". Command input: --newline add newline at the end of input Mandatory arguments to long options are mandatory for short options too. Input file location: -i, --input=INPUTFILE input PO file -D, --directory=DIRECTORY add DIRECTORY to list for input files search If no input file is given or if it is -, standard input is read. Input file syntax: -P, --properties-input input file is in Java .properties syntax --stringtable-input input file is in NeXTstep/GNUstep .strings syntax Informative output: -h, --help display this help and exit -V, --version output version information and exit AUTHOR Written by Bruno Haible. REPORTING BUGS Report bugs in the bug tracker at <https://savannah.gnu.org/projects/gettext> or by email to <bug-gettext@gnu.org>. COPYRIGHT Copyright © 2001-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 The full documentation for msgexec is maintained as a Texinfo manual. If the info and msgexec programs are properly installed at your site, the command info msgexec should give you access to the complete manual. GNU gettext-tools 0.22.5 February 2024 MSGEXEC(1)
|
msgexec - process translations of message catalog
|
msgexec [OPTION] COMMAND [COMMAND-OPTION]
| null | null |
x264
| null | null | null | null | null |
gcov-tool-13
|
gcov-tool is an offline tool to process gcc's gcda profile files. Current gcov-tool supports the following functionalities: * merge two sets of profiles with weights. * read a stream of profiles with associated filenames and merge it with a set of profiles with weights. * read one set of profile and rewrite profile contents. One can scale or normalize the count values. Examples of the use cases for this tool are: * Collect the profiles for different set of inputs, and use this tool to merge them. One can specify the weight to factor in the relative importance of each input. * Collect profiles from target systems without a filesystem (freestanding environments). Merge the collected profiles with associated profiles present on the host system. One can specify the weight to factor in the relative importance of each input. * Rewrite the profile after removing a subset of the gcda files, while maintaining the consistency of the summary and the histogram. * It can also be used to debug or libgcov code as the tools shares the majority code as the runtime library. Note that for the merging operation, this profile generated offline may contain slight different values from the online merged profile. Here are a list of typical differences: * histogram difference: This offline tool recomputes the histogram after merging the counters. The resulting histogram, therefore, is precise. The online merging does not have this capability -- the histogram is merged from two histograms and the result is an approximation. * summary checksum difference: Summary checksum uses a CRC32 operation. The value depends on the link list order of gcov-info objects. This order is different in gcov-tool from that in the online merge. It's expected to have different summary checksums. It does not really matter as the compiler does not use this checksum anywhere. * value profile counter values difference: Some counter values for value profile are runtime dependent, like heap addresses. It's normal to see some difference in these kind of counters.
|
gcov-tool - offline gcda profile processing tool
|
gcov-tool [-v|--version] [-h|--help] gcov-tool merge [merge-options] directory1 directory2 [-o|--output directory] [-v|--verbose] [-w|--weight w1,w2] gcov-tool merge-stream [merge-stream-options] [file] [-v|--verbose] [-w|--weight w1,w2] gcov-tool rewrite [rewrite-options] directory [-n|--normalize long_long_value] [-o|--output directory] [-s|--scale float_or_simple-frac_value] [-v|--verbose] gcov-tool overlap [overlap-options] directory1 directory2 [-f|--function] [-F|--fullname] [-h|--hotonly] [-o|--object] [-t|--hot_threshold] float [-v|--verbose]
|
-h --help Display help about using gcov-tool (on the standard output), and exit without doing any further processing. -v --version Display the gcov-tool version number (on the standard output), and exit without doing any further processing. merge Merge two profile directories. -o directory --output directory Set the output profile directory. Default output directory name is merged_profile. -v --verbose Set the verbose mode. -w w1,w2 --weight w1,w2 Set the merge weights of the directory1 and directory2, respectively. The default weights are 1 for both. merge-stream Collect profiles with associated filenames from a gcfn and gcda data stream. Read the stream from the file specified by file or from stdin. Merge the profiles with associated profiles in the host filesystem. Apply the optional weights while merging profiles. For the generation of a gcfn and gcda data stream on the target system, please have a look at the "__gcov_filename_to_gcfn()" and "__gcov_info_to_gcda()" functions declared in "#include <gcov.h>". -v --verbose Set the verbose mode. -w w1,w2 --weight w1,w2 Set the merge weights of the profiles from the gcfn and gcda data stream and the associated profiles in the host filesystem, respectively. The default weights are 1 for both. rewrite Read the specified profile directory and rewrite to a new directory. -n long_long_value --normalize <long_long_value> Normalize the profile. The specified value is the max counter value in the new profile. -o directory --output directory Set the output profile directory. Default output name is rewrite_profile. -s float_or_simple-frac_value --scale float_or_simple-frac_value Scale the profile counters. The specified value can be in floating point value, or simple fraction value form, such 1, 2, 2/3, and 5/3. -v --verbose Set the verbose mode. overlap Compute the overlap score between the two specified profile directories. The overlap score is computed based on the arc profiles. It is defined as the sum of min (p1_counter[i] / p1_sum_all, p2_counter[i] / p2_sum_all), for all arc counter i, where p1_counter[i] and p2_counter[i] are two matched counters and p1_sum_all and p2_sum_all are the sum of counter values in profile 1 and profile 2, respectively. -f --function Print function level overlap score. -F --fullname Print full gcda filename. -h --hotonly Only print info for hot objects/functions. -o --object Print object level overlap score. -t float --hot_threshold <float> Set the threshold for hot counter value. -v --verbose Set the verbose mode. SEE ALSO gpl(7), gfdl(7), fsf-funding(7), gcc(1), gcov(1) and the Info entry for gcc. COPYRIGHT Copyright (c) 2014-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 GCOV-TOOL(1)
| null |
glib-genmarshal
| null | null | null | null | null |
ngettext
|
The ngettext program translates a natural language message into the user's language, by looking up the translation in a message catalog, and chooses the appropriate plural form, which depends on the number COUNT and the language of the message catalog where the translation was found. Display native language translation of a textual message whose grammatical form depends on a number. -d, --domain=TEXTDOMAIN retrieve translated message from TEXTDOMAIN -c, --context=CONTEXT specify context for MSGID -e enable expansion of some escape sequences -E (ignored for compatibility) [TEXTDOMAIN] retrieve translated message from TEXTDOMAIN MSGID MSGID-PLURAL translate MSGID (singular) / MSGID-PLURAL (plural) COUNT choose singular/plural form based on this value Informative output: -h, --help display this help and exit -V, --version display version information and exit If the TEXTDOMAIN parameter is not given, the domain is determined from the environment variable TEXTDOMAIN. If the message catalog is not found in the regular directory, another location can be specified with the environment variable TEXTDOMAINDIR. Standard search directory: /opt/homebrew/Cellar/gettext/0.22.5/share/locale AUTHOR Written by Ulrich Drepper. REPORTING BUGS Report bugs in the bug tracker at <https://savannah.gnu.org/projects/gettext> or by email to <bug-gettext@gnu.org>. COPYRIGHT Copyright © 1995-1997, 2000-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 The full documentation for ngettext is maintained as a Texinfo manual. If the info and ngettext programs are properly installed at your site, the command info ngettext should give you access to the complete manual. GNU gettext-runtime 0.22.5 February 2024 NGETTEXT(1)
|
ngettext - translate message and choose plural form
|
ngettext [OPTION] [TEXTDOMAIN] MSGID MSGID-PLURAL COUNT
| null | null |
nspr-config
| null | null | null | null | null |
mftraining
| null | null | null | null | null |
base32
|
Base32 encode or decode FILE, or standard input, to standard output. With no FILE, or when FILE is -, read standard input. Mandatory arguments to long options are mandatory for short options too. -d, --decode decode data -i, --ignore-garbage when decoding, ignore non-alphabet characters -w, --wrap=COLS wrap encoded lines after COLS character (default 76). Use 0 to disable line wrapping --help display this help and exit --version output version information and exit The data are encoded as described for the base32 alphabet in RFC 4648. When decoding, the input may contain newlines in addition to the bytes of the formal base32 alphabet. Use --ignore-garbage to attempt to recover from any other non-alphabet bytes in the encoded stream. AUTHOR Written by Simon Josefsson. 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 basenc(1) Full documentation <https://www.gnu.org/software/coreutils/base32> or available locally via: info '(coreutils) base32 invocation' GNU coreutils 9.3 April 2023 BASE32(1)
|
base32 - base32 encode/decode data and print to standard output
|
base32 [OPTION]... [FILE]
| null | null |
pdfdetach
|
Pdfdetach lists or extracts embedded files (attachments) from a Portable Document Format (PDF) file.
|
pdfdetach - Portable Document Format (PDF) document embedded file extractor (version 3.03)
|
pdfdetach [options] [PDF-file]
|
Some of the following options can be set with configuration file commands. These are listed in square brackets with the description of the corresponding command line option. -list List all of the embedded files in the PDF file. File names are converted to the text encoding specified by the "-enc" switch. -save number Save the specified embedded file. By default, this uses the file name associated with the embedded file (as printed by the "-list" switch); the file name can be changed with the "-o" switch. -savefile filename Save the specified embedded file. By default, this uses the file name associated with the embedded file (as printed by the "-list" switch); the file name can be changed with the "-o" switch. -saveall Save all of the embedded files. This uses the file names associated with the embedded files (as printed by the "-list" switch). By default, the files are saved in the current directory; this can be changed with the "-o" switch. -o path Set the file name used when saving an embedded file with the "-save" switch, or the directory used by "-saveall". -enc encoding-name Sets the encoding to use for text output (embedded file names). This defaults to "UTF-8". -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. -v Print copyright and version information. -h Print usage information. (-help and --help are equivalent.) 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 pdfinfo software and documentation are copyright 1996-2011 Glyph & Cog, LLC. SEE ALSO pdffonts(1), pdfimages(1), pdfinfo(1), pdftocairo(1), pdftohtml(1), pdftoppm(1), pdftops(1), pdftotext(1) pdfseparate(1), pdfsig(1), pdfunite(1) 15 August 2011 pdfdetach(1)
| null |
git-shell
|
This is a login shell for SSH accounts to provide restricted Git access. It permits execution only of server-side Git commands implementing the pull/push functionality, plus custom commands present in a subdirectory named git-shell-commands in the user’s home directory. COMMANDS git shell accepts the following commands after the -c option: git receive-pack <argument>, git upload-pack <argument>, git upload-archive <argument> Call the corresponding server-side command to support the client’s git push, git fetch, or git archive --remote request. cvs server Imitate a CVS server. See git-cvsserver(1). If a ~/git-shell-commands directory is present, git shell will also handle other, custom commands by running "git-shell-commands/<command> <arguments>" from the user’s home directory. INTERACTIVE USE By default, the commands above can be executed only with the -c option; the shell is not interactive. If a ~/git-shell-commands directory is present, git shell can also be run interactively (with no arguments). If a help command is present in the git-shell-commands directory, it is run to provide the user with an overview of allowed actions. Then a "git> " prompt is presented at which one can enter any of the commands from the git-shell-commands directory, or exit to close the connection. Generally this mode is used as an administrative interface to allow users to list repositories they have access to, create, delete, or rename repositories, or change repository descriptions and permissions. If a no-interactive-login command exists, then it is run and the interactive shell is aborted.
|
git-shell - Restricted login shell for Git-only SSH access
|
chsh -s $(command -v git-shell) <user> git clone <user>@localhost:/path/to/repo.git ssh <user>@localhost
| null |
To disable interactive logins, displaying a greeting instead: $ chsh -s /usr/bin/git-shell $ mkdir $HOME/git-shell-commands $ cat >$HOME/git-shell-commands/no-interactive-login <<\EOF #!/bin/sh printf '%s\n' "Hi $USER! You've successfully authenticated, but I do not" printf '%s\n' "provide interactive shell access." exit 128 EOF $ chmod +x $HOME/git-shell-commands/no-interactive-login To enable git-cvsserver access (which should generally have the no-interactive-login example above as a prerequisite, as creating the git-shell-commands directory allows interactive logins): $ cat >$HOME/git-shell-commands/cvs <<\EOF if ! test $# = 1 && test "$1" = "server" then echo >&2 "git-cvsserver only handles \"server\"" exit 1 fi exec git cvsserver server EOF $ chmod +x $HOME/git-shell-commands/cvs SEE ALSO ssh(1), git-daemon(1), contrib/git-shell-commands/README GIT Part of the git(1) suite Git 2.41.0 2023-06-01 GIT-SHELL(1)
|
listsuites
| null | null | null | null | null |
mpg123-strip
| null | null | null | null | null |
ibd2sdi
|
ibd2sdi is a utility for extracting serialized dictionary information (SDI) from InnoDB tablespace files. SDI data is present in all persistent InnoDB tablespace files. ibd2sdi can be run on file-per-table tablespace files (*.ibd files), general tablespace files (*.ibd files), system tablespace files (ibdata* files), and the data dictionary tablespace (mysql.ibd). It is not supported for use with temporary tablespaces or undo tablespaces. ibd2sdi can be used at runtime or while the server is offline. During DDL operations, ROLLBACK operations, and undo log purge operations related to SDI, there may be a short interval of time when ibd2sdi fails to read SDI data stored in the tablespace. ibd2sdi performs an uncommitted read of SDI from the specified tablespace. Redo logs and undo logs are not accessed. Invoke the ibd2sdi utility like this: ibd2sdi [options] file_name1 [file_name2 file_name3 ...] ibd2sdi supports multi-file tablespaces like the InnoDB system tablespace, but it cannot be run on more than one tablespace at a time. For multi-file tablespaces, specify each file: ibd2sdi ibdata1 ibdata2 The files of a multi-file tablespace must be specified in order of the ascending page number. If two successive files have the same space ID, the later file must start with the last page number of the previous file + 1. ibd2sdi outputs SDI (containing id, type, and data fields) in JSON format. ibd2sdi Options ibd2sdi supports the following options: • --help, -h ┌────────────────────┬─────────┐ │Command-Line Format │ --help │ ├────────────────────┼─────────┤ │Type │ Boolean │ ├────────────────────┼─────────┤ │Default Value │ false │ └────────────────────┴─────────┘ Display a help message and exit. For example: Usage: ./ibd2sdi [-v] [-c <strict-check>] [-d <dump file name>] [-n] filename1 [filenames] See http://dev.mysql.com/doc/refman/8.0/en/ibd2sdi.html for usage hints. -h, --help Display this help and exit. -v, --version Display version information and exit. -#, --debug[=name] Output debug log. See http://dev.mysql.com/doc/refman/8.0/en/dbug-package.html -d, --dump-file=name Dump the tablespace SDI into the file passed by user. Without the filename, it will default to stdout -s, --skip-data Skip retrieving data from SDI records. Retrieve only id and type. -i, --id=# Retrieve the SDI record matching the id passed by user. -t, --type=# Retrieve the SDI records matching the type passed by user. -c, --strict-check=name Specify the strict checksum algorithm by the user. Allowed values are innodb, crc32, none. -n, --no-check Ignore the checksum verification. -p, --pretty Pretty format the SDI output.If false, SDI would be not human readable but it will be of less size (Defaults to on; use --skip-pretty to disable.) Variables (--variable-name=value) and boolean options {FALSE|TRUE} Value (after reading options) --------------------------------- ---------------------------------------- debug (No default value) dump-file (No default value) skip-data FALSE id 0 type 0 strict-check crc32 no-check FALSE pretty TRUE • --version, -v ┌────────────────────┬───────────┐ │Command-Line Format │ --version │ ├────────────────────┼───────────┤ │Type │ Boolean │ ├────────────────────┼───────────┤ │Default Value │ false │ └────────────────────┴───────────┘ Display version information and exit. For example: ibd2sdi Ver 8.0.3-dmr for Linux on x86_64 (Source distribution) • --debug[=debug_options], -# [debug_options] ┌────────────────────┬─────────────────┐ │Command-Line Format │ --debug=options │ ├────────────────────┼─────────────────┤ │Type │ String │ ├────────────────────┼─────────────────┤ │Default Value │ [none] │ └────────────────────┴─────────────────┘ Prints a debug log. For debug options, refer to Section 5.9.4, “The DBUG Package”. ibd2sdi --debug=d:t /tmp/ibd2sdi.trace This option is available only if MySQL was built using WITH_DEBUG. MySQL release binaries provided by Oracle are not built using this option. • --dump-file=, -d ┌────────────────────┬──────────────────┐ │Command-Line Format │ --dump-file=file │ ├────────────────────┼──────────────────┤ │Type │ File name │ ├────────────────────┼──────────────────┤ │Default Value │ [none] │ └────────────────────┴──────────────────┘ Dumps serialized dictionary information (SDI) into the specified dump file. If a dump file is not specified, the tablespace SDI is dumped to stdout. ibd2sdi --dump-file=file_name ../data/test/t1.ibd • --skip-data, -s ┌────────────────────┬─────────────┐ │Command-Line Format │ --skip-data │ ├────────────────────┼─────────────┤ │Type │ Boolean │ ├────────────────────┼─────────────┤ │Default Value │ false │ └────────────────────┴─────────────┘ Skips retrieval of data field values from the serialized dictionary information (SDI) and only retrieves the id and type field values, which are primary keys for SDI records. $> ibd2sdi --skip-data ../data/test/t1.ibd ["ibd2sdi" , { "type": 1, "id": 330 } , { "type": 2, "id": 7 } ] • --id=#, -i # ┌────────────────────┬─────────┐ │Command-Line Format │ --id=# │ ├────────────────────┼─────────┤ │Type │ Integer │ ├────────────────────┼─────────┤ │Default Value │ 0 │ └────────────────────┴─────────┘ Retrieves serialized dictionary information (SDI) matching the specified table or tablespace object id. An object id is unique to the object type. Table and tablespace object IDs are also found in the id column of the mysql.tables and mysql.tablespace data dictionary tables. For information about data dictionary tables, see Section 14.1, “Data Dictionary Schema”. $> ibd2sdi --id=7 ../data/test/t1.ibd ["ibd2sdi" , { "type": 2, "id": 7, "object": { "mysqld_version_id": 80003, "dd_version": 80003, "sdi_version": 1, "dd_object_type": "Tablespace", "dd_object": { "name": "test/t1", "comment": "", "options": "", "se_private_data": "flags=16417;id=2;server_version=80003;space_version=1;", "engine": "InnoDB", "files": [ { "ordinal_position": 1, "filename": "./test/t1.ibd", "se_private_data": "id=2;" } ] } } } ] • --type=#, -t # ┌────────────────────┬─────────────┐ │Command-Line Format │ --type=# │ ├────────────────────┼─────────────┤ │Type │ Enumeration │ ├────────────────────┼─────────────┤ │Default Value │ 0 │ ├────────────────────┼─────────────┤ │Valid Values │ 1 2 │ └────────────────────┴─────────────┘ Retrieves serialized dictionary information (SDI) matching the specified object type. SDI is provided for table (type=1) and tablespace (type=2) objects. This example shows output for a tablespace ts1 in the test database: $> ibd2sdi --type=2 ../data/test/ts1.ibd ["ibd2sdi" , { "type": 2, "id": 7, "object": { "mysqld_version_id": 80003, "dd_version": 80003, "sdi_version": 1, "dd_object_type": "Tablespace", "dd_object": { "name": "test/ts1", "comment": "", "options": "", "se_private_data": "flags=16417;id=2;server_version=80003;space_version=1;", "engine": "InnoDB", "files": [ { "ordinal_position": 1, "filename": "./test/ts1.ibd", "se_private_data": "id=2;" } ] } } } ] Due to the way in which InnoDB handles default value metadata, a default value may be present and non-empty in ibd2sdi output for a given table column even if it is not defined using DEFAULT. Consider the two tables created using the following statements, in the database named i: CREATE TABLE t1 (c VARCHAR(16) NOT NULL); CREATE TABLE t2 (c VARCHAR(16) NOT NULL DEFAULT "Sakila"); Using ibd2sdi, we can see that the default_value for column c is nonempty and is in fact padded to length in both tables, like this: $> ibd2sdi ../data/i/t1.ibd | grep -m1 '\"default_value\"' | cut -b34- | sed -e s/,// "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\nAAAAAAAAAAA=" $> ibd2sdi ../data/i/t2.ibd | grep -m1 '\"default_value\"' | cut -b34- | sed -e s/,// "BlNha2lsYQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\nAAAAAAAAAAA=" Examination of ibd2sdi output may be easier using a JSON-aware utility like jq[1], as shown here: $> ibd2sdi ../data/i/t1.ibd | jq '.[1]["object"]["dd_object"]["columns"][0]["default_value"]' "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\nAAAAAAAAAAA=" $> ibd2sdi ../data/i/t2.ibd | jq '.[1]["object"]["dd_object"]["columns"][0]["default_value"]' "BlNha2lsYQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\nAAAAAAAAAAA=" For more information, see the MySQL Internals documentation[2]. • --strict-check, -c ┌────────────────────┬──────────────────────────┐ │Command-Line Format │ --strict-check=algorithm │ ├────────────────────┼──────────────────────────┤ │Type │ Enumeration │ ├────────────────────┼──────────────────────────┤ │Default Value │ crc32 │ ├────────────────────┼──────────────────────────┤ │Valid Values │ crc32 innodb none │ └────────────────────┴──────────────────────────┘ Specifies a strict checksum algorithm for validating the checksum of pages that are read. Options include innodb, crc32, and none. In this example, the strict version of the innodb checksum algorithm is specified: ibd2sdi --strict-check=innodb ../data/test/t1.ibd In this example, the strict version of crc32 checksum algorithm is specified: ibd2sdi -c crc32 ../data/test/t1.ibd If you do not specify the --strict-check option, validation is performed against non-strict innodb, crc32 and none checksums. • --no-check, -n ┌────────────────────┬────────────┐ │Command-Line Format │ --no-check │ ├────────────────────┼────────────┤ │Type │ Boolean │ ├────────────────────┼────────────┤ │Default Value │ false │ └────────────────────┴────────────┘ Skips checksum validation for pages that are read. ibd2sdi --no-check ../data/test/t1.ibd • --pretty, -p ┌────────────────────┬──────────┐ │Command-Line Format │ --pretty │ ├────────────────────┼──────────┤ │Type │ Boolean │ ├────────────────────┼──────────┤ │Default Value │ false │ └────────────────────┴──────────┘ Outputs SDI data in JSON pretty print format. Enabled by default. If disabled, SDI is not human readable but is smaller in size. Use --skip-pretty to disable. ibd2sdi --skip-pretty ../data/test/t1.ibd 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/. NOTES 1. jq https://stedolan.github.io/jq/ 2. MySQL Internals documentation https://dev.mysql.com/doc/dev/ 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 IBD2SDI(1)
|
ibd2sdi - InnoDB utility for extracting serialized dictionary information (SDI) from an InnoDB tablespace
|
ibd2sdi [options] file_name1 [file_name2 file_name3 ...]
| null | null |
ssltap
| null | null | null | null | null |
nss-policy-check
| null | null | null | null | null |
luajit
|
This is the command-line program to run Lua programs with LuaJIT. LuaJIT is a just-in-time (JIT) compiler for the Lua language. The virtual machine (VM) is based on a fast interpreter combined with a trace compiler. It can significantly improve the performance of Lua programs. LuaJIT is API- and ABI-compatible with the VM of the standard Lua 5.1 interpreter. When embedding the VM into an application, the built library can be used as a drop-in replacement.
|
luajit - Just-In-Time Compiler for the Lua Language
|
luajit [options]... [script [args]...] WEB SITE https://luajit.org
|
-e chunk Run the given chunk of Lua code. -l library Load the named library, just like require("library"). -b ... Save or list bytecode. Run without arguments to get help on options. -j command Perform LuaJIT control command (optional space after -j). -O[opt] Control LuaJIT optimizations. -i Run in interactive mode. -v Show LuaJIT version. -E Ignore environment variables. -- Stop processing options. - Read script from stdin instead. After all options are processed, the given script is run. The arguments are passed in the global arg table. Interactive mode is only entered, if no script and no -e option is given. Interactive mode can be left with EOF (Ctrl-Z).
|
luajit hello.lua world Prints "Hello world", assuming hello.lua contains: print("Hello", arg[1]) luajit -e "local x=0; for i=1,1e9 do x=x+i end; print(x)" Calculates the sum of the numbers from 1 to 1000000000. And finishes in a reasonable amount of time, too. luajit -jv -e "for i=1,10 do for j=1,10 do for k=1,100 do end end end" Runs some nested loops and shows the resulting traces. COPYRIGHT LuaJIT is Copyright © 2005-2022 Mike Pall. LuaJIT is open source software, released under the MIT license. SEE ALSO More details in the provided HTML docs or at: https://luajit.org More about the Lua language can be found at: https://lua.org/docs.html lua(1) luajit(1)
|
env_parallel.ksh
| null | null | null | null | null |
symfony
| null | null | null | null | null |
dwebp
|
This manual page documents the dwebp command. dwebp decompresses WebP files into PNG, PAM, PPM or PGM images. Note: Animated WebP files are not supported.
|
dwebp - decompress a WebP file to an image file
|
dwebp [options] input_file.webp
|
The basic options are: -h Print usage summary. -version Print the version number (as major.minor.revision) and exit. -o string Specify the name of the output file (as PNG format by default). Using "-" as output name will direct output to 'stdout'. -- string Explicitly specify the input file. This option is useful if the input file starts with an '-' for instance. This option must appear last. Any other options afterward will be ignored. If the input file is "-", the data will be read from stdin instead of a file. -bmp Change the output format to uncompressed BMP. -tiff Change the output format to uncompressed TIFF. -pam Change the output format to PAM (retains alpha). -ppm Change the output format to PPM (discards alpha). -pgm Change the output format to PGM. The output consists of luma/chroma samples instead of RGB, using the IMC4 layout. This option is mainly for verification and debugging purposes. -yuv Change the output format to raw YUV. The output consists of luma/chroma-U/chroma-V samples instead of RGB, saved sequentially as individual planes. This option is mainly for verification and debugging purposes. -nofancy Don't use the fancy upscaler for YUV420. This may lead to jaggy edges (especially the red ones), but should be faster. -nofilter Don't use the in-loop filtering process even if it is required by the bitstream. This may produce visible blocks on the non- compliant output, but it will make the decoding faster. -dither strength Specify a dithering strength between 0 and 100. Dithering is a post-processing effect applied to chroma components in lossy compression. It helps by smoothing gradients and avoiding banding artifacts. -alpha_dither If the compressed file contains a transparency plane that was quantized during compression, this flag will allow dithering the reconstructed plane in order to generate smoother transparency gradients. -nodither Disable all dithering (default). -mt Use multi-threading for decoding, if possible. -crop x_position y_position width height Crop the decoded picture to a rectangle with top-left corner at coordinates (x_position, y_position) and size width x height. This cropping area must be fully contained within the source rectangle. The top-left corner will be snapped to even coordinates if needed. This option is meant to reduce the memory needed for cropping large images. Note: the cropping is applied before any scaling. -flip Flip decoded image vertically (can be useful for OpenGL textures for instance). -resize, -scale width height Rescale the decoded picture to dimension width x height. This option is mostly intended to reducing the memory needed to decode large images, when only a small version is needed (thumbnail, preview, etc.). Note: scaling is applied after cropping. If either (but not both) of the width or height parameters is 0, the value will be calculated preserving the aspect-ratio. -quiet Do not print anything. -v Print extra information (decoding time in particular). -noasm Disable all assembly optimizations. 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/
|
dwebp picture.webp -o output.png dwebp picture.webp -ppm -o output.ppm dwebp -o output.ppm -- ---picture.webp cat picture.webp | dwebp -o - -- - > output.ppm AUTHORS dwebp 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 cwebp(1), gif2webp(1), webpmux(1) Please refer to https://developers.google.com/speed/webp/ for additional information. Output file format details PAM: http://netpbm.sourceforge.net/doc/pam.html PGM: http://netpbm.sourceforge.net/doc/pgm.html PPM: http://netpbm.sourceforge.net/doc/ppm.html PNG: http://www.libpng.org/pub/png/png-sitemap.html#info November 17, 2021 DWEBP(1)
|
convert-caffe2-to-onnx
| null | null | null | null | null |
bsqlodbc
|
bsqlodbc is a utility program distributed with FreeTDS. bsqlodbc is a non-interactive equivalent of the ‘isql’ utility programs distributed by Sybase and Microsoft. Like them, bsqlodbc uses the command ‘go’ on a line by itself as a separator between batches. The last batch need not be followed by ‘go’. bsqlodbc makes use of the ODBC API provided by FreeTDS. This API is of course also available to application developers.
|
bsqlodbc – batch SQL script processor using ODBC
|
bsqlodbc [-hqv] [-U username] [-P password] [-S server] [-D database] [-i input_file] [-o output_file] [-e error_file] [-t field_term] [-V odbc_version]
|
-U username Database server login name. -P password Database server password. -S server Database server to which to connect. -D database Database to use. -i input_file Name of script file, containing SQL. -o output_file Name of output file, holding result data. -e error_file Name of file for errors. -t field_term Specifies the field terminator. Default is two spaces ( ‘ ’ ). Recognized escape sequences are tab ( ‘\t’ ), carriage return ( ‘\r’ ), newline ( ‘\n’ ), and backslash ( ‘\\’ ). -h Print column headers with the data to the same file. -q Do not print column metadata, return status, or rowcount. Overrides -h. -v Verbose mode, for more information about the ODBC interaction. This also reports the result set metadata, including and return code. All verbose data are written to standard error (or -e), so as not to interfere with the data stream. -V odbc_version Specify ODBC version (2 or 3). NOTES bsqlodbc 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. EXIT STATUS bsqlodbc exits 0 on success, and >0 if the server cannot process the query. HISTORY bsqlodbc first appeared in FreeTDS 0.65. AUTHORS The bsqlodbc utility was written by James K. Lowden ⟨jklowden@freetds.org⟩. FreeTDS 1.4.21 March 25, 2015 FreeTDS 1.4.21
| null |
ftfy
| null | null | null | null | null |
ffescape
| null | null | null | null | null |
gptx
|
Output a permuted index, including context, of the words in the input files. With no FILE, or when FILE is -, read standard input. Mandatory arguments to long options are mandatory for short options too. -A, --auto-reference output automatically generated references -G, --traditional behave more like System V 'ptx' -F, --flag-truncation=STRING use STRING for flagging line truncations. The default is '/' -M, --macro-name=STRING macro name to use instead of 'xx' -O, --format=roff generate output as roff directives -R, --right-side-refs put references at right, not counted in -w -S, --sentence-regexp=REGEXP for end of lines or end of sentences -T, --format=tex generate output as TeX directives -W, --word-regexp=REGEXP use REGEXP to match each keyword -b, --break-file=FILE word break characters in this FILE -f, --ignore-case fold lower case to upper case for sorting -g, --gap-size=NUMBER gap size in columns between output fields -i, --ignore-file=FILE read ignore word list from FILE -o, --only-file=FILE read only word list from this FILE -r, --references first field of each line is a reference -t, --typeset-mode - not implemented - -w, --width=NUMBER output width in columns, reference excluded --help display this help and exit --version output version information and exit AUTHOR Written by Francois Pinard. 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/ptx> or available locally via: info '(coreutils) ptx invocation' GNU coreutils 9.3 April 2023 PTX(1)
|
ptx - produce a permuted index of file contents
|
ptx [OPTION]... [INPUT]... (without -G) ptx -G [OPTION]... [INPUT [OUTPUT]]
| null | null |
gtimeout
|
Start COMMAND, and kill it if still running after DURATION. Mandatory arguments to long options are mandatory for short options too. --preserve-status exit with the same status as COMMAND, even when the command times out --foreground when not running timeout directly from a shell prompt, allow COMMAND to read from the TTY and get TTY signals; in this mode, children of COMMAND will not be timed out -k, --kill-after=DURATION also send a KILL signal if COMMAND is still running this long after the initial signal was sent -s, --signal=SIGNAL specify the signal to be sent on timeout; SIGNAL may be a name like 'HUP' or a number; see 'kill -l' for a list of signals -v, --verbose diagnose to stderr any signal sent upon timeout --help display this help and exit --version output version information and exit DURATION is a floating point number with an optional suffix: 's' for seconds (the default), 'm' for minutes, 'h' for hours or 'd' for days. A duration of 0 disables the associated timeout. Upon timeout, send the TERM signal to COMMAND, if no other SIGNAL specified. The TERM signal kills any process that does not block or catch that signal. It may be necessary to use the KILL signal, since this signal can't be caught. Exit status: 124 if COMMAND times out, and --preserve-status is not specified 125 if the timeout command itself fails 126 if COMMAND is found but cannot be invoked 127 if COMMAND cannot be found 137 if COMMAND (or timeout itself) is sent the KILL (9) signal (128+9) - the exit status of COMMAND otherwise BUGS Some platforms don't currently support timeouts beyond the year 2038. AUTHOR Written by Padraig Brady. 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 kill(1) Full documentation <https://www.gnu.org/software/coreutils/timeout> or available locally via: info '(coreutils) timeout invocation' GNU coreutils 9.3 April 2023 TIMEOUT(1)
|
timeout - run a command with a time limit
|
timeout [OPTION] DURATION COMMAND [ARG]... timeout [OPTION]
| null | null |
php-cgi
| null | null | null | null | null |
aarch64-apple-darwin23-gcc-ranlib-13
| null | null | null | null | null |
ifnames
|
Scan all of the C source FILES (or the standard input, if none are given) and write to the standard output a sorted list of all the identifiers that appear in those files in '#if', '#elif', '#ifdef', or '#ifndef' directives. Print each identifier on a line, followed by a space-separated list of the files in which that identifier occurs. -h, --help print this help, then exit -V, --version print version number, then exit AUTHOR Written by David J. MacKenzie and Paul Eggert. REPORTING BUGS Report bugs to <bug-autoconf@gnu.org>, or via Savannah: <https://savannah.gnu.org/support/?group=autoconf>. COPYRIGHT Copyright © 2023 Free Software Foundation, Inc. License GPLv3+/Autoconf: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>, <https://gnu.org/licenses/exceptions.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 autoconf(1), automake(1), autoreconf(1), autoupdate(1), autoheader(1), autoscan(1), config.guess(1), config.sub(1), ifnames(1), libtool(1). The full documentation for Autoconf is maintained as a Texinfo manual. To read the manual locally, use the command info autoconf You can also consult the Web version of the manual at <https://gnu.org/software/autoconf/manual/>. GNU Autoconf 2.72 December 2023 IFNAMES(1)
|
ifnames - Extract CPP conditionals from a set of files
|
ifnames [OPTION]... [FILE]...
| null | null |
psa_hash
| null | null | null | null | null |
coloredlogs
| null | null | null | null | null |
pinky
|
-l produce long format output for the specified USERs -b omit the user's home directory and shell in long format -h omit the user's project file in long format -p omit the user's plan file in long format -s do short format output, this is the default -f omit the line of column headings in short format -w omit the user's full name in short format -i omit the user's full name and remote host in short format -q omit the user's full name, remote host and idle time in short format --help display this help and exit --version output version information and exit A lightweight 'finger' program; print user information. The utmp file will be /var/run/utmpx. AUTHOR Written by Joseph Arceneaux, David MacKenzie, and Kaveh Ghazi. 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/pinky> or available locally via: info '(coreutils) pinky invocation' GNU coreutils 9.3 April 2023 PINKY(1)
|
pinky - lightweight finger
|
pinky [OPTION]... [USER]...
| null | null |
hostid
|
Print the numeric identifier (in hexadecimal) for the current host. --help display this help and exit --version output version information and exit AUTHOR Written by 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 gethostid(3) Full documentation <https://www.gnu.org/software/coreutils/hostid> or available locally via: info '(coreutils) hostid invocation' GNU coreutils 9.3 April 2023 HOSTID(1)
|
hostid - print the numeric identifier for the current host
|
hostid [OPTION]
| null | null |
MailHog
| null | null | null | null | null |
ocspclnt
| null | null | null | null | null |
tjbench
| null | null | null | null | null |
env_parallel.ash
| null | null | null | null | null |
check-node
| null | null | null | null | null |
gd2copypal
| null | null | null | null | null |
bsqldb
|
bsqldb is a utility program distributed with FreeTDS. bsqldb is a non- interactive equivalent of the "isql" utility programs distributed by Sybase and Microsoft. Like them, bsqldb uses the command "go" on a line by itself as a separator between batches. The last batch need not be followed by "go". bsqldb makes use of the DB-Library API provided by FreeTDS. This API is of course also available to application developers.
|
bsqldb – batch SQL script processor using DB-Library
|
bsqldb [-hqv] [-S servername] [-D database] [-U username] [-P password] [-i input_file] [-o output_file] [-e error_file] [-H hostname] [-t field_term] [-R pivot_description]
|
-D database Database to use. -H hostname hostname Override name of client sent to server. -P password Database server password. -S servername Database server to which to connect. -U username Database server login name. If username is not provided, a domain login is attempted for TDS 7+ connections. -e error_file Name of file for errors. -h Print column headers with the data to the same file. -i input_file Name of script file, containing SQL. -o output_file Name of output file, holding result data. -q Do not print column metadata, return status, or rowcount. Overrides -h. -t field_term Specifies the field terminator. Default is two spaces (' '). Recognized escape sequences are tab ('\t'), carriage return ('\r'), newline ('\n'), and backslash ('\\'). -v Verbose mode, for more information about the DB-Library interaction. This also reports the result set metadata, including and return code. All verbose data are written to standard error (or -e), so as not to interfere with the data stream. -R pivot_description Specify pivot trasformation. The format is ⟨down_columns⟩ ⟨across_columns⟩ ⟨function⟩ ⟨value⟩. Columns are specified but numbers. The format of down columns and across columns is a comma separated list of columns. function is either count, sum, min or max. ENVIRONMENT DSQUERY default servername NOTES bsqldb 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. The source code for bsqldb is intended as a model for DB-Library users. DB-Library has a rich set of functions, and it can be hard sometimes to understand how to use them, particularly the first time. If you find something about the source code unclear, you are encouraged to email the author your comments. EXIT STATUS bsqldb exits 0 on success, and >0 if the server cannot process the query. For messages with severity > 10, bsqldb calls exit(3) with the severity level. For example, if the severity level is 16, bsqldb will return an exit status of 16 to the shell. HISTORY bsqldb first appeared in FreeTDS 0.63. AUTHORS The bsqldb utility was written by James K. Lowden ⟨jklowden@freetds.org⟩. BUGS Microsoft servers as of SQL Server 7.0 SP 3 do not return output parameters unless the RPC functions are used. This means bsqldb cannot return output parameters for stored procedures with these servers. FreeTDS 1.4.21 March 26, 2015 FreeTDS 1.4.21
| null |
x265
| null | null | null | null | null |
normalizer
| null | null | null | null | null |
gpwd
|
Print the full filename of the current working directory. -L, --logical use PWD from environment, even if it contains symlinks -P, --physical avoid all symlinks --help display this help and exit --version output version information and exit If no option is specified, -P is assumed. NOTE: your shell may have its own version of pwd, which usually supersedes the version described here. Please refer to your shell's documentation for details about the options it supports. AUTHOR Written by 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 getcwd(3) Full documentation <https://www.gnu.org/software/coreutils/pwd> or available locally via: info '(coreutils) pwd invocation' GNU coreutils 9.3 April 2023 PWD(1)
|
pwd - print name of current/working directory
|
pwd [OPTION]...
| null | null |
lzmadec
|
xzdec is a liblzma-based decompression-only tool for .xz (and only .xz) files. xzdec is intended to work as a drop-in replacement for xz(1) in the most common situations where a script has been written to use xz --decompress --stdout (and possibly a few other commonly used options) to decompress .xz files. lzmadec is identical to xzdec except that lzmadec supports .lzma files instead of .xz files. To reduce the size of the executable, xzdec doesn't support multithreading or localization, and doesn't read options from XZ_DEFAULTS and XZ_OPT environment variables. xzdec doesn't support displaying intermediate progress information: sending SIGINFO to xzdec does nothing, but sending SIGUSR1 terminates the process instead of displaying progress information.
|
xzdec, lzmadec - Small .xz and .lzma decompressors
|
xzdec [option...] [file...] lzmadec [option...] [file...]
|
-d, --decompress, --uncompress Ignored for xz(1) compatibility. xzdec supports only decompression. -k, --keep Ignored for xz(1) compatibility. xzdec never creates or removes any files. -c, --stdout, --to-stdout Ignored for xz(1) compatibility. xzdec always writes the decompressed data to standard output. -q, --quiet Specifying this once does nothing since xzdec never displays any warnings or notices. Specify this twice to suppress errors. -Q, --no-warn Ignored for xz(1) compatibility. xzdec never uses the exit status 2. -h, --help Display a help message and exit successfully. -V, --version Display the version number of xzdec and liblzma. EXIT STATUS 0 All was good. 1 An error occurred. xzdec doesn't have any warning messages like xz(1) has, thus the exit status 2 is not used by xzdec. NOTES Use xz(1) instead of xzdec or lzmadec for normal everyday use. xzdec or lzmadec are meant only for situations where it is important to have a smaller decompressor than the full-featured xz(1). xzdec and lzmadec are not really that small. The size can be reduced further by dropping features from liblzma at compile time, but that shouldn't usually be done for executables distributed in typical non- embedded operating system distributions. If you need a truly small .xz decompressor, consider using XZ Embedded. SEE ALSO xz(1) XZ Embedded: <https://tukaani.org/xz/embedded.html> Tukaani 2024-04-08 XZDEC(1)
| null |
lua5.4
| null | null | null | null | null |
fc-match
| null | null | null | null | null |
arduino-builder
| null | null | null | null | null |
mangle
| null | null | null | null | null |
gtail
|
Print the last 10 lines of each FILE to standard output. With more than one FILE, precede each with a header giving the file name. With no FILE, or when FILE is -, read standard input. Mandatory arguments to long options are mandatory for short options too. -c, --bytes=[+]NUM output the last NUM bytes; or use -c +NUM to output starting with byte NUM of each file -f, --follow[={name|descriptor}] output appended data as the file grows; an absent option argument means 'descriptor' -F same as --follow=name --retry -n, --lines=[+]NUM output the last NUM lines, instead of the last 10; or use -n +NUM to output starting with line NUM --max-unchanged-stats=N with --follow=name, reopen a FILE which has not changed size after N (default 5) iterations to see if it has been unlinked or renamed (this is the usual case of rotated log files); with inotify, this option is rarely useful --pid=PID with -f, terminate after process ID, PID dies -q, --quiet, --silent never output headers giving file names --retry keep trying to open a file if it is inaccessible -s, --sleep-interval=N with -f, sleep for approximately N seconds (default 1.0) between iterations; with inotify and --pid=P, check process P at least once every N seconds -v, --verbose always output headers giving file names -z, --zero-terminated line delimiter is NUL, not newline --help display this help and exit --version output version information and exit NUM may have a multiplier suffix: b 512, kB 1000, K 1024, MB 1000*1000, M 1024*1024, GB 1000*1000*1000, G 1024*1024*1024, and so on for T, P, E, Z, Y, R, Q. Binary prefixes can be used, too: KiB=K, MiB=M, and so on. With --follow (-f), tail defaults to following the file descriptor, which means that even if a tail'ed file is renamed, tail will continue to track its end. This default behavior is not desirable when you really want to track the actual name of the file, not the file descriptor (e.g., log rotation). Use --follow=name in that case. That causes tail to track the named file in a way that accommodates renaming, removal and creation. AUTHOR Written by Paul Rubin, David MacKenzie, Ian Lance Taylor, 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 head(1) Full documentation <https://www.gnu.org/software/coreutils/tail> or available locally via: info '(coreutils) tail invocation' GNU coreutils 9.3 April 2023 TAIL(1)
|
tail - output the last part of files
|
tail [OPTION]... [FILE]...
| null | null |
lzgrep
|
xzgrep invokes grep(1) on uncompressed contents of files. The formats of the files are determined from the filename suffixes. Any file with a suffix supported by xz(1), gzip(1), bzip2(1), lzop(1), zstd(1), or lz4(1) will be decompressed; all other files are assumed to be uncompressed. If no files are specified or file is - then standard input is read. When reading from standard input, only files supported by xz(1) are decompressed. Other files are assumed to be in uncompressed form already. Most options of grep(1) are supported. However, the following options are not supported: -r, --recursive -R, --dereference-recursive -d, --directories=action -Z, --null -z, --null-data --include=glob --exclude=glob --exclude-from=file --exclude-dir=glob xzegrep is an alias for xzgrep -E. xzfgrep is an alias for xzgrep -F. The commands lzgrep, lzegrep, and lzfgrep are provided for backward compatibility with LZMA Utils. EXIT STATUS 0 At least one match was found from at least one of the input files. No errors occurred. 1 No matches were found from any of the input files. No errors occurred. >1 One or more errors occurred. It is unknown if matches were found. ENVIRONMENT GREP If GREP is set to a non-empty value, it is used instead of grep, grep -E, or grep -F. SEE ALSO grep(1), xz(1), gzip(1), bzip2(1), lzop(1), zstd(1), lz4(1), zgrep(1) Tukaani 2024-02-13 XZGREP(1)
|
xzgrep - search possibly-compressed files for patterns
|
xzgrep [option...] [pattern_list] [file...] xzegrep ... xzfgrep ... lzgrep ... lzegrep ... lzfgrep ...
| null | null |
msgunfmt
|
Convert binary message catalog to Uniforum style .po file. Mandatory arguments to long options are mandatory for short options too. Operation mode: -j, --java Java mode: input is a Java ResourceBundle class --csharp C# mode: input is a .NET .dll file --csharp-resources C# resources mode: input is a .NET .resources file --tcl Tcl mode: input is a tcl/msgcat .msg file Input file location: FILE ... input .mo files If no input file is given or if it is -, standard input is read. Input file location in Java mode: -r, --resource=RESOURCE resource name -l, --locale=LOCALE locale name, either language or language_COUNTRY The class name is determined by appending the locale name to the resource name, separated with an underscore. The class is located using the CLASSPATH. Input file location in C# mode: -r, --resource=RESOURCE resource name -l, --locale=LOCALE locale name, either language or language_COUNTRY -d DIRECTORY base directory for locale dependent .dll files The -l and -d options are mandatory. The .dll file is located in a subdirectory of the specified directory whose name depends on the locale. Input file location in Tcl mode: -l, --locale=LOCALE locale name, either language or language_COUNTRY -d DIRECTORY base directory of .msg message catalogs The -l and -d options are mandatory. The .msg file is located in the specified directory. Output file location: -o, --output-file=FILE write output to specified file The results are written to standard output if no output file is specified or if it is -. Output details: --color use colors and other text attributes always --color=WHEN use colors and other text attributes if WHEN. WHEN may be 'always', 'never', 'auto', or 'html'. --style=STYLEFILE specify CSS style rule file for --color -e, --no-escape do not use C escapes in output (default) -E, --escape use C escapes in output, no extended chars --force-po write PO file even if empty -i, --indent write indented output style --strict write strict uniforum style -p, --properties-output write out a Java .properties file --stringtable-output write out a NeXTstep/GNUstep .strings file -w, --width=NUMBER set output page width --no-wrap do not break long message lines, longer than the output page width, into several lines -s, --sort-output generate sorted output Informative output: -h, --help display this help and exit -V, --version output version information and exit -v, --verbose increase verbosity level AUTHOR Written by Ulrich Drepper. REPORTING BUGS Report bugs in the bug tracker at <https://savannah.gnu.org/projects/gettext> or by email to <bug-gettext@gnu.org>. COPYRIGHT Copyright © 1995-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 The full documentation for msgunfmt is maintained as a Texinfo manual. If the info and msgunfmt programs are properly installed at your site, the command info msgunfmt should give you access to the complete manual. GNU gettext-tools 0.22.5 February 2024 MSGUNFMT(1)
|
msgunfmt - uncompile message catalog from binary format
|
msgunfmt [OPTION] [FILE]...
| null | null |
bd_list_titles
| null | null | null | null | null |
cpp-13
|
The C preprocessor, often known as cpp, is a macro processor that is used automatically by the C compiler to transform your program before compilation. It is called a macro processor because it allows you to define macros, which are brief abbreviations for longer constructs. The C preprocessor is intended to be used only with C, C++, and Objective-C source code. In the past, it has been abused as a general text processor. It will choke on input which does not obey C's lexical rules. For example, apostrophes will be interpreted as the beginning of character constants, and cause errors. Also, you cannot rely on it preserving characteristics of the input which are not significant to C-family languages. If a Makefile is preprocessed, all the hard tabs will be removed, and the Makefile will not work. Having said that, you can often get away with using cpp on things which are not C. Other Algol-ish programming languages are often safe (Ada, etc.) So is assembly, with caution. -traditional-cpp mode preserves more white space, and is otherwise more permissive. Many of the problems can be avoided by writing C or C++ style comments instead of native language comments, and keeping macros simple. Wherever possible, you should use a preprocessor geared to the language you are writing in. Modern versions of the GNU assembler have macro facilities. Most high level programming languages have their own conditional compilation and inclusion mechanism. If all else fails, try a true general text processor, such as GNU M4. C preprocessors vary in some details. This manual discusses the GNU C preprocessor, which provides a small superset of the features of ISO Standard C. In its default mode, the GNU C preprocessor does not do a few things required by the standard. These are features which are rarely, if ever, used, and may cause surprising changes to the meaning of a program which does not expect them. To get strict ISO Standard C, you should use the -std=c90, -std=c99, -std=c11 or -std=c17 options, depending on which version of the standard you want. To get all the mandatory diagnostics, you must also use -pedantic. This manual describes the behavior of the ISO preprocessor. To minimize gratuitous differences, where the ISO preprocessor's behavior does not conflict with traditional semantics, the traditional preprocessor should behave the same way. The various differences that do exist are detailed in the section Traditional Mode. For clarity, unless noted otherwise, references to CPP in this manual refer to GNU CPP.
|
cpp - The C Preprocessor
|
cpp [-Dmacro[=defn]...] [-Umacro] [-Idir...] [-iquotedir...] [-M|-MM] [-MG] [-MF filename] [-MP] [-MQ target...] [-MT target...] infile [[-o] outfile] Only the most useful options are given above; see below for a more complete list of preprocessor-specific options. In addition, cpp accepts most gcc driver options, which are not listed here. Refer to the GCC documentation for details.
|
The cpp command expects two file names as arguments, infile and outfile. The preprocessor reads infile together with any other files it specifies with #include. All the output generated by the combined input files is written in outfile. Either infile or outfile may be -, which as infile means to read from standard input and as outfile means to write to standard output. If either file is omitted, it means the same as if - had been specified for that file. You can also use the -o outfile option to specify the output file. Unless otherwise noted, or the option ends in =, all options which take an argument may have that argument appear either immediately after the option, or with a space between option and argument: -Ifoo and -I foo have the same effect. Many options have multi-letter names; therefore multiple single-letter options may not be grouped: -dM is very different from -d -M. -D name Predefine name as a macro, with definition 1. -D name=definition The contents of definition are tokenized and processed as if they appeared during translation phase three in a #define directive. In particular, the definition is truncated by embedded newline characters. If you are invoking the preprocessor from a shell or shell-like program you may need to use the shell's quoting syntax to protect characters such as spaces that have a meaning in the shell syntax. If you wish to define a function-like macro on the command line, write its argument list with surrounding parentheses before the equals sign (if any). Parentheses are meaningful to most shells, so you should quote the option. With sh and csh, -D'name(args...)=definition' works. -D and -U options are processed in the order they are given on the command line. All -imacros file and -include file options are processed after all -D and -U options. -U name Cancel any previous definition of name, either built in or provided with a -D option. -include file Process file as if "#include "file"" appeared as the first line of the primary source file. However, the first directory searched for file is the preprocessor's working directory instead of the directory containing the main source file. If not found there, it is searched for in the remainder of the "#include "..."" search chain as normal. If multiple -include options are given, the files are included in the order they appear on the command line. -imacros file Exactly like -include, except that any output produced by scanning file is thrown away. Macros it defines remain defined. This allows you to acquire all the macros from a header without also processing its declarations. All files specified by -imacros are processed before all files specified by -include. -undef Do not predefine any system-specific or GCC-specific macros. The standard predefined macros remain defined. -pthread Define additional macros required for using the POSIX threads library. You should use this option consistently for both compilation and linking. This option is supported on GNU/Linux targets, most other Unix derivatives, and also on x86 Cygwin and MinGW targets. -M Instead of outputting the result of preprocessing, output a rule suitable for make describing the dependencies of the main source file. The preprocessor outputs one make rule containing the object file name for that source file, a colon, and the names of all the included files, including those coming from -include or -imacros command-line options. Unless specified explicitly (with -MT or -MQ), the object file name consists of the name of the source file with any suffix replaced with object file suffix and with any leading directory parts removed. If there are many included files then the rule is split into several lines using \-newline. The rule has no commands. This option does not suppress the preprocessor's debug output, such as -dM. To avoid mixing such debug output with the dependency rules you should explicitly specify the dependency output file with -MF, or use an environment variable like DEPENDENCIES_OUTPUT. Debug output is still sent to the regular output stream as normal. Passing -M to the driver implies -E, and suppresses warnings with an implicit -w. -MM Like -M but do not mention header files that are found in system header directories, nor header files that are included, directly or indirectly, from such a header. This implies that the choice of angle brackets or double quotes in an #include directive does not in itself determine whether that header appears in -MM dependency output. -MF file When used with -M or -MM, specifies a file to write the dependencies to. If no -MF switch is given the preprocessor sends the rules to the same place it would send preprocessed output. When used with the driver options -MD or -MMD, -MF overrides the default dependency output file. If file is -, then the dependencies are written to stdout. -MG In conjunction with an option such as -M requesting dependency generation, -MG assumes missing header files are generated files and adds them to the dependency list without raising an error. The dependency filename is taken directly from the "#include" directive without prepending any path. -MG also suppresses preprocessed output, as a missing header file renders this useless. This feature is used in automatic updating of makefiles. -Mno-modules Disable dependency generation for compiled module interfaces. -MP This option instructs CPP to add a phony target for each dependency other than the main file, causing each to depend on nothing. These dummy rules work around errors make gives if you remove header files without updating the Makefile to match. This is typical output: test.o: test.c test.h test.h: -MT target Change the target of the rule emitted by dependency generation. By default CPP takes the name of the main input file, deletes any directory components and any file suffix such as .c, and appends the platform's usual object suffix. The result is the target. An -MT option sets the target to be exactly the string you specify. If you want multiple targets, you can specify them as a single argument to -MT, or use multiple -MT options. For example, -MT '$(objpfx)foo.o' might give $(objpfx)foo.o: foo.c -MQ target Same as -MT, but it quotes any characters which are special to Make. -MQ '$(objpfx)foo.o' gives $$(objpfx)foo.o: foo.c The default target is automatically quoted, as if it were given with -MQ. -MD -MD is equivalent to -M -MF file, except that -E is not implied. The driver determines file based on whether an -o option is given. If it is, the driver uses its argument but with a suffix of .d, otherwise it takes the name of the input file, removes any directory components and suffix, and applies a .d suffix. If -MD is used in conjunction with -E, any -o switch is understood to specify the dependency output file, but if used without -E, each -o is understood to specify a target object file. Since -E is not implied, -MD can be used to generate a dependency output file as a side effect of the compilation process. -MMD Like -MD except mention only user header files, not system header files. -fpreprocessed Indicate to the preprocessor that the input file has already been preprocessed. This suppresses things like macro expansion, trigraph conversion, escaped newline splicing, and processing of most directives. The preprocessor still recognizes and removes comments, so that you can pass a file preprocessed with -C to the compiler without problems. In this mode the integrated preprocessor is little more than a tokenizer for the front ends. -fpreprocessed is implicit if the input file has one of the extensions .i, .ii or .mi. These are the extensions that GCC uses for preprocessed files created by -save-temps. -fdirectives-only When preprocessing, handle directives, but do not expand macros. The option's behavior depends on the -E and -fpreprocessed options. With -E, preprocessing is limited to the handling of directives such as "#define", "#ifdef", and "#error". Other preprocessor operations, such as macro expansion and trigraph conversion are not performed. In addition, the -dD option is implicitly enabled. With -fpreprocessed, predefinition of command line and most builtin macros is disabled. Macros such as "__LINE__", which are contextually dependent, are handled normally. This enables compilation of files previously preprocessed with "-E -fdirectives-only". With both -E and -fpreprocessed, the rules for -fpreprocessed take precedence. This enables full preprocessing of files previously preprocessed with "-E -fdirectives-only". -fdollars-in-identifiers Accept $ in identifiers. -fextended-identifiers Accept universal character names and extended characters in identifiers. This option is enabled by default for C99 (and later C standard versions) and C++. -fno-canonical-system-headers When preprocessing, do not shorten system header paths with canonicalization. -fmax-include-depth=depth Set the maximum depth of the nested #include. The default is 200. -ftabstop=width Set the distance between tab stops. This helps the preprocessor report correct column numbers in warnings or errors, even if tabs appear on the line. If the value is less than 1 or greater than 100, the option is ignored. The default is 8. -ftrack-macro-expansion[=level] Track locations of tokens across macro expansions. This allows the compiler to emit diagnostic about the current macro expansion stack when a compilation error occurs in a macro expansion. Using this option makes the preprocessor and the compiler consume more memory. The level parameter can be used to choose the level of precision of token location tracking thus decreasing the memory consumption if necessary. Value 0 of level de-activates this option. Value 1 tracks tokens locations in a degraded mode for the sake of minimal memory overhead. In this mode all tokens resulting from the expansion of an argument of a function-like macro have the same location. Value 2 tracks tokens locations completely. This value is the most memory hungry. When this option is given no argument, the default parameter value is 2. Note that "-ftrack-macro-expansion=2" is activated by default. -fmacro-prefix-map=old=new When preprocessing files residing in directory old, expand the "__FILE__" and "__BASE_FILE__" macros as if the files resided in directory new instead. This can be used to change an absolute path to a relative path by using . for new which can result in more reproducible builds that are location independent. This option also affects "__builtin_FILE()" during compilation. See also -ffile-prefix-map and -fcanon-prefix-map. -fexec-charset=charset Set the execution character set, used for string and character constants. The default is UTF-8. charset can be any encoding supported by the system's "iconv" library routine. -fwide-exec-charset=charset Set the wide execution character set, used for wide string and character constants. The default is one of UTF-32BE, UTF-32LE, UTF-16BE, or UTF-16LE, whichever corresponds to the width of "wchar_t" and the big-endian or little-endian byte order being used for code generation. As with -fexec-charset, charset can be any encoding supported by the system's "iconv" library routine; however, you will have problems with encodings that do not fit exactly in "wchar_t". -finput-charset=charset Set the input character set, used for translation from the character set of the input file to the source character set used by GCC. If the locale does not specify, or GCC cannot get this information from the locale, the default is UTF-8. This can be overridden by either the locale or this command-line option. Currently the command-line option takes precedence if there's a conflict. charset can be any encoding supported by the system's "iconv" library routine. -fworking-directory Enable generation of linemarkers in the preprocessor output that let the compiler know the current working directory at the time of preprocessing. When this option is enabled, the preprocessor emits, after the initial linemarker, a second linemarker with the current working directory followed by two slashes. GCC uses this directory, when it's present in the preprocessed input, as the directory emitted as the current working directory in some debugging information formats. This option is implicitly enabled if debugging information is enabled, but this can be inhibited with the negated form -fno-working-directory. If the -P flag is present in the command line, this option has no effect, since no "#line" directives are emitted whatsoever. -A predicate=answer Make an assertion with the predicate predicate and answer answer. This form is preferred to the older form -A predicate(answer), which is still supported, because it does not use shell special characters. -A -predicate=answer Cancel an assertion with the predicate predicate and answer answer. -C Do not discard comments. All comments are passed through to the output file, except for comments in processed directives, which are deleted along with the directive. You should be prepared for side effects when using -C; it causes the preprocessor to treat comments as tokens in their own right. For example, comments appearing at the start of what would be a directive line have the effect of turning that line into an ordinary source line, since the first token on the line is no longer a #. -CC Do not discard comments, including during macro expansion. This is like -C, except that comments contained within macros are also passed through to the output file where the macro is expanded. In addition to the side effects of the -C option, the -CC option causes all C++-style comments inside a macro to be converted to C-style comments. This is to prevent later use of that macro from inadvertently commenting out the remainder of the source line. The -CC option is generally used to support lint comments. -P Inhibit generation of linemarkers in the output from the preprocessor. This might be useful when running the preprocessor on something that is not C code, and will be sent to a program which might be confused by the linemarkers. -traditional -traditional-cpp Try to imitate the behavior of pre-standard C preprocessors, as opposed to ISO C preprocessors. Note that GCC does not otherwise attempt to emulate a pre-standard C compiler, and these options are only supported with the -E switch, or when invoking CPP explicitly. -trigraphs Support ISO C trigraphs. These are three-character sequences, all starting with ??, that are defined by ISO C to stand for single characters. For example, ??/ stands for \, so '??/n' is a character constant for a newline. By default, GCC ignores trigraphs, but in standard-conforming modes it converts them. See the -std and -ansi options. -remap Enable special code to work around file systems which only permit very short file names, such as MS-DOS. -H Print the name of each header file used, in addition to other normal activities. Each name is indented to show how deep in the #include stack it is. Precompiled header files are also printed, even if they are found to be invalid; an invalid precompiled header file is printed with ...x and a valid one with ...! . -dletters Says to make debugging dumps during compilation as specified by letters. The flags documented here are those relevant to the preprocessor. Other letters are interpreted by the compiler proper, or reserved for future versions of GCC, and so are silently ignored. If you specify letters whose behavior conflicts, the result is undefined. -dM Instead of the normal output, generate a list of #define directives for all the macros defined during the execution of the preprocessor, including predefined macros. This gives you a way of finding out what is predefined in your version of the preprocessor. Assuming you have no file foo.h, the command touch foo.h; cpp -dM foo.h shows all the predefined macros. -dD Like -dM except in two respects: it does not include the predefined macros, and it outputs both the #define directives and the result of preprocessing. Both kinds of output go to the standard output file. -dN Like -dD, but emit only the macro names, not their expansions. -dI Output #include directives in addition to the result of preprocessing. -dU Like -dD except that only macros that are expanded, or whose definedness is tested in preprocessor directives, are output; the output is delayed until the use or test of the macro; and #undef directives are also output for macros tested but undefined at the time. -fdebug-cpp This option is only useful for debugging GCC. When used from CPP or with -E, it dumps debugging information about location maps. Every token in the output is preceded by the dump of the map its location belongs to. When used from GCC without -E, this option has no effect. -I dir -iquote dir -isystem dir -idirafter dir Add the directory dir to the list of directories to be searched for header files during preprocessing. If dir begins with = or $SYSROOT, then the = or $SYSROOT is replaced by the sysroot prefix; see --sysroot and -isysroot. Directories specified with -iquote apply only to the quote form of the directive, "#include "file"". Directories specified with -I, -isystem, or -idirafter apply to lookup for both the "#include "file"" and "#include <file>" directives. You can specify any number or combination of these options on the command line to search for header files in several directories. The lookup order is as follows: 1. For the quote form of the include directive, the directory of the current file is searched first. 2. For the quote form of the include directive, the directories specified by -iquote options are searched in left-to-right order, as they appear on the command line. 3. Directories specified with -I options are scanned in left-to- right order. 4. Directories specified with -isystem options are scanned in left-to-right order. 5. Standard system directories are scanned. 6. Directories specified with -idirafter options are scanned in left-to-right order. You can use -I to override a system header file, substituting your own version, since these directories are searched before the standard system header file directories. However, you should not use this option to add directories that contain vendor-supplied system header files; use -isystem for that. The -isystem and -idirafter options also mark the directory as a system directory, so that it gets the same special treatment that is applied to the standard system directories. If a standard system include directory, or a directory specified with -isystem, is also specified with -I, the -I option is ignored. The directory is still searched but as a system directory at its normal position in the system include chain. This is to ensure that GCC's procedure to fix buggy system headers and the ordering for the "#include_next" directive are not inadvertently changed. If you really need to change the search order for system directories, use the -nostdinc and/or -isystem options. -I- Split the include path. This option has been deprecated. Please use -iquote instead for -I directories before the -I- and remove the -I- option. Any directories specified with -I options before -I- are searched only for headers requested with "#include "file""; they are not searched for "#include <file>". If additional directories are specified with -I options after the -I-, those directories are searched for all #include directives. In addition, -I- inhibits the use of the directory of the current file directory as the first search directory for "#include "file"". There is no way to override this effect of -I-. -iprefix prefix Specify prefix as the prefix for subsequent -iwithprefix options. If the prefix represents a directory, you should include the final /. -iwithprefix dir -iwithprefixbefore dir Append dir to the prefix specified previously with -iprefix, and add the resulting directory to the include search path. -iwithprefixbefore puts it in the same place -I would; -iwithprefix puts it where -idirafter would. -isysroot dir This option is like the --sysroot option, but applies only to header files (except for Darwin targets, where it applies to both header files and libraries). See the --sysroot option for more information. -imultilib dir Use dir as a subdirectory of the directory containing target- specific C++ headers. -nostdinc Do not search the standard system directories for header files. Only the directories explicitly specified with -I, -iquote, -isystem, and/or -idirafter options (and the directory of the current file, if appropriate) are searched. -nostdinc++ Do not search for header files in the C++-specific standard directories, but do still search the other standard directories. (This option is used when building the C++ library.) -Wcomment -Wcomments Warn whenever a comment-start sequence /* appears in a /* comment, or whenever a backslash-newline appears in a // comment. This warning is enabled by -Wall. -Wtrigraphs Warn if any trigraphs are encountered that might change the meaning of the program. Trigraphs within comments are not warned about, except those that would form escaped newlines. This option is implied by -Wall. If -Wall is not given, this option is still enabled unless trigraphs are enabled. To get trigraph conversion without warnings, but get the other -Wall warnings, use -trigraphs -Wall -Wno-trigraphs. -Wundef Warn if an undefined identifier is evaluated in an "#if" directive. Such identifiers are replaced with zero. -Wexpansion-to-defined Warn whenever defined is encountered in the expansion of a macro (including the case where the macro is expanded by an #if directive). Such usage is not portable. This warning is also enabled by -Wpedantic and -Wextra. -Wunused-macros Warn about macros defined in the main file that are unused. A macro is used if it is expanded or tested for existence at least once. The preprocessor also warns if the macro has not been used at the time it is redefined or undefined. Built-in macros, macros defined on the command line, and macros defined in include files are not warned about. Note: If a macro is actually used, but only used in skipped conditional blocks, then the preprocessor reports it as unused. To avoid the warning in such a case, you might improve the scope of the macro's definition by, for example, moving it into the first skipped block. Alternatively, you could provide a dummy use with something like: #if defined the_macro_causing_the_warning #endif -Wno-endif-labels Do not warn whenever an "#else" or an "#endif" are followed by text. This sometimes happens in older programs with code of the form #if FOO ... #else FOO ... #endif FOO The second and third "FOO" should be in comments. This warning is on by default. ENVIRONMENT This section describes the environment variables that affect how CPP operates. You can use them to specify directories or prefixes to use when searching for include files, or to control dependency output. Note that you can also specify places to search using options such as -I, and control dependency output with options like -M. These take precedence over environment variables, which in turn take precedence over the configuration of GCC. CPATH C_INCLUDE_PATH CPLUS_INCLUDE_PATH OBJC_INCLUDE_PATH Each variable's value is a list of directories separated by a special character, much like PATH, in which to look for header files. The special character, "PATH_SEPARATOR", is target- dependent and determined at GCC build time. For Microsoft Windows- based targets it is a semicolon, and for almost all other targets it is a colon. CPATH specifies a list of directories to be searched as if specified with -I, but after any paths given with -I options on the command line. This environment variable is used regardless of which language is being preprocessed. The remaining environment variables apply only when preprocessing the particular language indicated. Each specifies a list of directories to be searched as if specified with -isystem, but after any paths given with -isystem options on the command line. In all these variables, an empty element instructs the compiler to search its current working directory. Empty elements can appear at the beginning or end of a path. For instance, if the value of CPATH is ":/special/include", that has the same effect as -I. -I/special/include. DEPENDENCIES_OUTPUT If this variable is set, its value specifies how to output dependencies for Make based on the non-system header files processed by the compiler. System header files are ignored in the dependency output. The value of DEPENDENCIES_OUTPUT can be just a file name, in which case the Make rules are written to that file, guessing the target name from the source file name. Or the value can have the form file target, in which case the rules are written to file file using target as the target name. In other words, this environment variable is equivalent to combining the options -MM and -MF, with an optional -MT switch too. SUNPRO_DEPENDENCIES This variable is the same as DEPENDENCIES_OUTPUT (see above), except that system header files are not ignored, so it implies -M rather than -MM. However, the dependence on the main input file is omitted. SOURCE_DATE_EPOCH If this variable is set, its value specifies a UNIX timestamp to be used in replacement of the current date and time in the "__DATE__" and "__TIME__" macros, so that the embedded timestamps become reproducible. The value of SOURCE_DATE_EPOCH must be a UNIX timestamp, defined as the number of seconds (excluding leap seconds) since 01 Jan 1970 00:00:00 represented in ASCII; identical to the output of "date +%s" on GNU/Linux and other systems that support the %s extension in the "date" command. The value should be a known timestamp such as the last modification time of the source or package and it should be set by the build process. SEE ALSO gpl(7), gfdl(7), fsf-funding(7), gcc(1), and the Info entries for cpp and gcc. COPYRIGHT Copyright (c) 1987-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. A copy of the license is included in the man page gfdl(7). This manual contains no Invariant Sections. The Front-Cover Texts are (a) (see below), and the Back-Cover Texts are (b) (see below). (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 CPP(1)
| null |
tiffcp
|
tiffcp combines one or more files created according to the Tag Image File Format, Revision 6.0 into a single TIFF file. Because the output file may be compressed using a different algorithm than the input files, tiffcp is most often used to convert between different compression schemes. By default, tiffcp will copy all the understood tags in a TIFF directory of an input file to the associated directory in the output file. tiffcp can be used to reorganize the storage characteristics of data in a file, but it is explicitly intended to not alter or convert the image data content in any way.
|
tiffcp - copy (and possibly convert) a TIFF file
|
tiffcp [ options ] src1.tif … srcN.tif dst.tif
|
-a Append to an existing output file instead of overwriting it. -b image subtract the following monochrome image from all others processed. This can be used to remove a noise bias from a set of images. This bias image is typically an image of noise the camera saw with its shutter closed. -B Force output to be written with Big-Endian byte order. This option only has an effect when the output file is created or overwritten and not when it is appended to. -C Suppress the use of "strip chopping" when reading images that have a single strip/tile of uncompressed data. -c Specify the compression to use for data written to the output file: -c none for no compression, -c packbits for PackBits compression, -c lzw for Lempel-Ziv & Welch compression, -c zip for Deflate compression, -c lzma for LZMA2 compression, -c jpeg for baseline JPEG compression, -c g3 for CCITT Group 3 (T.4) compression, -c g4 for CCITT Group 4 (T.6) compression, or -c sgilog for SGILOG compression. By default tiffcp will compress data according to the value of the Compression tag found in the source file. The CCITT Group 3 and Group 4 compression algorithms can only be used with bilevel data. Group 3 compression can be specified together with several T.4-specific options: • 1d for 1-dimensional encoding, • 2d for 2-dimensional encoding, and • fill to force each encoded scanline to be zero-filled so that the terminating EOL code lies on a byte boundary. Group 3-specific options are specified by appending a :-separated list to the g3 option; e.g. -c g3:2d:fill to get 2D-encoded data with byte-aligned EOL codes. LZW, Deflate and LZMA2 compression can be specified together with a predictor value. A predictor value of 2 causes each scanline of the output image to undergo horizontal differencing before it is encoded; a value of 1 forces each scanline to be encoded without differencing. A value 3 is for floating point predictor which you can use if the encoded data are in floating point format. LZW-specific options are specified by appending a :-separated list to the lzw option; e.g. -c lzw:2 for LZW compression with horizontal differencing. Deflate and LZMA2 encoders support various compression levels (or encoder presets) set as character p and a preset number. p1 is the fastest one with the worst compression ratio and p9 is the slowest but with the best possible ratio; e.g. -c zip:3:p9 for Deflate encoding with maximum compression level and floating point predictor. For the Deflate codec, and in a libtiff build with libdeflate enabled, p12 is actually the maximum level. For the Deflate codec, and in a libtiff build with libdeflate enabled, s0 can be used to require zlib to be used, and s1 for libdeflate (defaults to libdeflate when it is available). -f fillorder Specify the bit fill order to use in writing output data. By default, tiffcp will create a new file with the same fill order as the original. Specifying -f lsb2msb will force data to be written with the FillOrder tag set to LSB2MSB, while -f msb2lsb will force data to be written with the FillOrder tag set to MSB2LSB. -i Ignore non-fatal read errors and continue processing of the input file. -l Specify the length of a tile (in pixels). tiffcp attempts to set the tile dimensions so that no more than 8 kilobytes of data appear in a tile. -L Force output to be written with Little-Endian byte order. This option only has an effect when the output file is created or overwritten and not when it is appended to. -M Suppress the use of memory-mapped files when reading images. -o offset Set initial directory offset. -p Specify the planar configuration to use in writing image data that has one 8-bit sample per pixel. By default, tiffcp will create a new file with the same planar configuration as the original. Specifying -p contig will force data to be written with multi-sample data packed together, while -p separate will force samples to be written in separate planes. -r Specify the number of rows (scanlines) in each strip of data written to the output file. By default (or when value 0 is specified), tiffcp attempts to set the rows/strip that no more than 8 kilobytes of data appear in a strip. If you specify special value -1 it will results in infinite number of the rows per strip. The entire image will be the one strip in that case. -s Force the output file to be written with data organized in strips (rather than tiles). -t Force the output file to be written with data organized in tiles (rather than strips). options can be used to force the resultant image to be written as strips or tiles of data, respectively. -w Specify the width of a tile (in pixels). :program::tiffcp attempts to set the tile dimensions so that no more than 8 kilobytes of data appear in a tile. -x Force the output file to be written with PAGENUMBER value in sequence. -8 Write BigTIFF instead of classic TIFF format. -,= character substitute character for , in parsing image directory indices in files. This is necessary if filenames contain commas. Note that -,= with whitespace immediately following will disable the special meaning of the , entirely. See examples. -m size Set maximum memory allocation size (in MiB). The default is 256MiB. Set to 0 to disable the limit.
|
The following concatenates two files and writes the result using LZW encoding: tiffcp -c lzw a.tif b.tif result.tif To convert a G3 1d-encoded TIFF to a single strip of G4-encoded data the following might be used: tiffcp -c g4 -r 10000 g3.tif g4.tif (1000 is just a number that is larger than the number of rows in the source file.) To extract a selected set of images from a multi-image TIFF file, the file name may be immediately followed by a , separated list of image directory indices. The first image is always in directory 0. Thus, to copy the 1st and 3rd images of image file album.tif to result.tif: tiffcp album.tif,0,2 result.tif A trailing comma denotes remaining images in sequence. The following command will copy all image with except the first one: tiffcp album.tif,1, result.tif Given file CCD.tif whose first image is a noise bias followed by images which include that bias, subtract the noise from all those images following it (while decompressing) with the command: tiffcp -c none -b CCD.tif CCD.tif,1, result.tif If the file above were named CCD,X.tif, the -,= option would be required to correctly parse this filename with image numbers, as follows: tiffcp -c none -,=% -b CCD,X.tif CCD,X%1%.tif result.tif SEE ALSO tiffinfo (1), tiffdump (1), tiffsplit (1), libtiff (3tiff) AUTHOR LibTIFF contributors COPYRIGHT 1988-2022, LibTIFF contributors 4.6 September 8, 2023 TIFFCP(1)
|
myisam_ftdump
|
myisam_ftdump displays information about FULLTEXT indexes in MyISAM tables. It reads the MyISAM index file directly, so it must be run on the server host where the table is located. Before using myisam_ftdump, be sure to issue a FLUSH TABLES statement first if the server is running. myisam_ftdump scans and dumps the entire index, which is not particularly fast. On the other hand, the distribution of words changes infrequently, so it need not be run often. Invoke myisam_ftdump like this: myisam_ftdump [options] tbl_name index_num The tbl_name argument should be the name of a MyISAM table. You can also specify a table by naming its index file (the file with the .MYI suffix). If you do not invoke myisam_ftdump in the directory where the table files are located, the table or index file name must be preceded by the path name to the table's database directory. Index numbers begin with 0. Example: Suppose that the test database contains a table named mytexttable that has the following definition: CREATE TABLE mytexttable ( id INT NOT NULL, txt TEXT NOT NULL, PRIMARY KEY (id), FULLTEXT (txt) ) ENGINE=MyISAM; The index on id is index 0 and the FULLTEXT index on txt is index 1. If your working directory is the test database directory, invoke myisam_ftdump as follows: myisam_ftdump mytexttable 1 If the path name to the test database directory is /usr/local/mysql/data/test, you can also specify the table name argument using that path name. This is useful if you do not invoke myisam_ftdump in the database directory: myisam_ftdump /usr/local/mysql/data/test/mytexttable 1 You can use myisam_ftdump to generate a list of index entries in order of frequency of occurrence like this on Unix-like systems: myisam_ftdump -c mytexttable 1 | sort -r On Windows, use: myisam_ftdump -c mytexttable 1 | sort /R myisam_ftdump supports the following options: • --help, -h -? ┌────────────────────┬────────┐ │Command-Line Format │ --help │ └────────────────────┴────────┘ Display a help message and exit. • --count, -c ┌────────────────────┬─────────┐ │Command-Line Format │ --count │ └────────────────────┴─────────┘ Calculate per-word statistics (counts and global weights). • --dump, -d ┌────────────────────┬────────┐ │Command-Line Format │ --dump │ └────────────────────┴────────┘ Dump the index, including data offsets and word weights. • --length, -l ┌────────────────────┬──────────┐ │Command-Line Format │ --length │ └────────────────────┴──────────┘ Report the length distribution. • --stats, -s ┌────────────────────┬─────────┐ │Command-Line Format │ --stats │ └────────────────────┴─────────┘ Report global index statistics. This is the default operation if no other operation is specified. • --verbose, -v ┌────────────────────┬───────────┐ │Command-Line Format │ --verbose │ └────────────────────┴───────────┘ Verbose mode. Print more output about what the program does. 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 MYISAM_FTDUMP(1)
|
myisam_ftdump - display full-text index information
|
myisam_ftdump [options] tbl_name index_num
| null | null |
gi-compile-repository
| null | null | null | null | null |
signtool
| null | null | null | null | null |
lzmore
|
xzmore displays text from compressed files to a terminal using more(1). Files supported by xz(1) are decompressed; other files are assumed to be in uncompressed form already. If no files are given, xzmore reads from standard input. See the more(1) manual for the keyboard commands. Note that scrolling backwards might not be possible depending on the implementation of more(1). This is because xzmore uses a pipe to pass the decompressed data to more(1). xzless(1) uses less(1) which provides more advanced features. The command lzmore is provided for backward compatibility with LZMA Utils. ENVIRONMENT PAGER If PAGER is set, its value is used as the pager instead of more(1). SEE ALSO more(1), xz(1), xzless(1), zmore(1) Tukaani 2024-02-12 XZMORE(1)
|
xzmore, lzmore - view xz or lzma compressed (text) files
|
xzmore [file...] lzmore [file...]
| null | null |
protoc-gen-upb
| null | null | null | null | null |
git-upload-pack
|
Invoked by git fetch-pack, learns what objects the other side is missing, and sends them after packing. This command is usually not invoked directly by the end user. The UI for the protocol is on the git fetch-pack side, and the program pair is meant to be used to pull updates from a remote repository. For push operations, see git send-pack.
|
git-upload-pack - Send objects packed back to git-fetch-pack
|
git-upload-pack [--[no-]strict] [--timeout=<n>] [--stateless-rpc] [--advertise-refs] <directory>
|
--[no-]strict Do not try <directory>/.git/ if <directory> is no Git directory. --timeout=<n> Interrupt transfer after <n> seconds of inactivity. --stateless-rpc Perform only a single read-write cycle with stdin and stdout. This fits with the HTTP POST request processing model where a program may read the request, write a response, and must exit. --http-backend-info-refs Used by git-http-backend(1) to serve up $GIT_URL/info/refs?service=git-upload-pack requests. See "Smart Clients" in gitprotocol-http(5) and "HTTP Transport" in the gitprotocol-v2(5) documentation. Also understood by git-receive- pack(1). <directory> The repository to sync from. ENVIRONMENT GIT_PROTOCOL Internal variable used for handshaking the wire protocol. Server admins may need to configure some transports to allow this variable to be passed. See the discussion in git(1). SEE ALSO gitnamespaces(7) GIT Part of the git(1) suite Git 2.41.0 2023-06-01 GIT-UPLOAD-PACK(1)
| null |
innochecksum
|
innochecksum prints checksums for InnoDB files. This tool reads an InnoDB tablespace file, calculates the checksum for each page, compares the calculated checksum to the stored checksum, and reports mismatches, which indicate damaged pages. It was originally developed to speed up verifying the integrity of tablespace files after power outages but can also be used after file copies. Because checksum mismatches cause InnoDB to deliberately shut down a running server, it may be preferable to use this tool rather than waiting for an in-production server to encounter the damaged pages. innochecksum cannot be used on tablespace files that the server already has open. For such files, you should use CHECK TABLE to check tables within the tablespace. Attempting to run innochecksum on a tablespace that the server already has open results in an Unable to lock file error. If checksum mismatches are found, restore the tablespace from backup or start the server and attempt to use mysqldump to make a backup of the tables within the tablespace. Invoke innochecksum like this: innochecksum [options] file_name innochecksum Options innochecksum supports the following options. For options that refer to page numbers, the numbers are zero-based. • --help, -? ┌────────────────────┬─────────┐ │Command-Line Format │ --help │ ├────────────────────┼─────────┤ │Type │ Boolean │ ├────────────────────┼─────────┤ │Default Value │ false │ └────────────────────┴─────────┘ Displays command line help. Example usage: innochecksum --help • --info, -I ┌────────────────────┬─────────┐ │Command-Line Format │ --info │ ├────────────────────┼─────────┤ │Type │ Boolean │ ├────────────────────┼─────────┤ │Default Value │ false │ └────────────────────┴─────────┘ Synonym for --help. Displays command line help. Example usage: innochecksum --info • --version, -V ┌────────────────────┬───────────┐ │Command-Line Format │ --version │ ├────────────────────┼───────────┤ │Type │ Boolean │ ├────────────────────┼───────────┤ │Default Value │ false │ └────────────────────┴───────────┘ Displays version information. Example usage: innochecksum --version • --verbose, -v ┌────────────────────┬───────────┐ │Command-Line Format │ --verbose │ ├────────────────────┼───────────┤ │Type │ Boolean │ ├────────────────────┼───────────┤ │Default Value │ false │ └────────────────────┴───────────┘ Verbose mode; prints a progress indicator to the log file every five seconds. In order for the progress indicator to be printed, the log file must be specified using the --log option. To turn on verbose mode, run: innochecksum --verbose To turn off verbose mode, run: innochecksum --verbose=FALSE The --verbose option and --log option can be specified at the same time. For example: innochecksum --verbose --log=/var/lib/mysql/test/logtest.txt To locate the progress indicator information in the log file, you can perform the following search: cat ./logtest.txt | grep -i "okay" The progress indicator information in the log file appears similar to the following: page 1663 okay: 2.863% done page 8447 okay: 14.537% done page 13695 okay: 23.568% done page 18815 okay: 32.379% done page 23039 okay: 39.648% done page 28351 okay: 48.789% done page 33023 okay: 56.828% done page 37951 okay: 65.308% done page 44095 okay: 75.881% done page 49407 okay: 85.022% done page 54463 okay: 93.722% done ... • --count, -c ┌────────────────────┬───────────┐ │Command-Line Format │ --count │ ├────────────────────┼───────────┤ │Type │ Base name │ ├────────────────────┼───────────┤ │Default Value │ true │ └────────────────────┴───────────┘ Print a count of the number of pages in the file and exit. Example usage: innochecksum --count ../data/test/tab1.ibd • --start-page=num, -s num ┌────────────────────┬────────────────┐ │Command-Line Format │ --start-page=# │ ├────────────────────┼────────────────┤ │Type │ Numeric │ ├────────────────────┼────────────────┤ │Default Value │ 0 │ └────────────────────┴────────────────┘ Start at this page number. Example usage: innochecksum --start-page=600 ../data/test/tab1.ibd or: innochecksum -s 600 ../data/test/tab1.ibd • --end-page=num, -e num ┌────────────────────┬──────────────────────┐ │Command-Line Format │ --end-page=# │ ├────────────────────┼──────────────────────┤ │Type │ Numeric │ ├────────────────────┼──────────────────────┤ │Default Value │ 0 │ ├────────────────────┼──────────────────────┤ │Minimum Value │ 0 │ ├────────────────────┼──────────────────────┤ │Maximum Value │ 18446744073709551615 │ └────────────────────┴──────────────────────┘ End at this page number. Example usage: innochecksum --end-page=700 ../data/test/tab1.ibd or: innochecksum --p 700 ../data/test/tab1.ibd • --page=num, -p num ┌────────────────────┬──────────┐ │Command-Line Format │ --page=# │ ├────────────────────┼──────────┤ │Type │ Integer │ ├────────────────────┼──────────┤ │Default Value │ 0 │ └────────────────────┴──────────┘ Check only this page number. Example usage: innochecksum --page=701 ../data/test/tab1.ibd • --strict-check, -C ┌────────────────────┬──────────────────────────┐ │Command-Line Format │ --strict-check=algorithm │ ├────────────────────┼──────────────────────────┤ │Type │ Enumeration │ ├────────────────────┼──────────────────────────┤ │Default Value │ crc32 │ ├────────────────────┼──────────────────────────┤ │Valid Values │ innodb crc32 none │ └────────────────────┴──────────────────────────┘ Specify a strict checksum algorithm. Options include innodb, crc32, and none. In this example, the innodb checksum algorithm is specified: innochecksum --strict-check=innodb ../data/test/tab1.ibd In this example, the crc32 checksum algorithm is specified: innochecksum -C crc32 ../data/test/tab1.ibd The following conditions apply: • If you do not specify the --strict-check option, innochecksum validates against innodb, crc32 and none. • If you specify the none option, only checksums generated by none are allowed. • If you specify the innodb option, only checksums generated by innodb are allowed. • If you specify the crc32 option, only checksums generated by crc32 are allowed. • --no-check, -n ┌────────────────────┬────────────┐ │Command-Line Format │ --no-check │ ├────────────────────┼────────────┤ │Type │ Boolean │ ├────────────────────┼────────────┤ │Default Value │ false │ └────────────────────┴────────────┘ Ignore the checksum verification when rewriting a checksum. This option may only be used with the innochecksum --write option. If the --write option is not specified, innochecksum terminates. In this example, an innodb checksum is rewritten to replace an invalid checksum: innochecksum --no-check --write innodb ../data/test/tab1.ibd • --allow-mismatches, -a ┌────────────────────┬──────────────────────┐ │Command-Line Format │ --allow-mismatches=# │ ├────────────────────┼──────────────────────┤ │Type │ Integer │ ├────────────────────┼──────────────────────┤ │Default Value │ 0 │ ├────────────────────┼──────────────────────┤ │Minimum Value │ 0 │ ├────────────────────┼──────────────────────┤ │Maximum Value │ 18446744073709551615 │ └────────────────────┴──────────────────────┘ The maximum number of checksum mismatches allowed before innochecksum terminates. The default setting is 0. If --allow-mismatches=N, where N>=0, N mismatches are permitted and innochecksum terminates at N+1. When --allow-mismatches is set to 0, innochecksum terminates on the first checksum mismatch. In this example, an existing innodb checksum is rewritten to set --allow-mismatches to 1. innochecksum --allow-mismatches=1 --write innodb ../data/test/tab1.ibd With --allow-mismatches set to 1, if there is a mismatch at page 600 and another at page 700 on a file with 1000 pages, the checksum is updated for pages 0-599 and 601-699. Because --allow-mismatches is set to 1, the checksum tolerates the first mismatch and terminates on the second mismatch, leaving page 600 and pages 700-999 unchanged. • --write=name, -w num ┌────────────────────┬───────────────────┐ │Command-Line Format │ --write=algorithm │ ├────────────────────┼───────────────────┤ │Type │ Enumeration │ ├────────────────────┼───────────────────┤ │Default Value │ crc32 │ ├────────────────────┼───────────────────┤ │Valid Values │ innodb crc32 │ │ │ none │ └────────────────────┴───────────────────┘ Rewrite a checksum. When rewriting an invalid checksum, the --no-check option must be used together with the --write option. The --no-check option tells innochecksum to ignore verification of the invalid checksum. You do not have to specify the --no-check option if the current checksum is valid. An algorithm must be specified when using the --write option. Possible values for the --write option are: • innodb: A checksum calculated in software, using the original algorithm from InnoDB. • crc32: A checksum calculated using the crc32 algorithm, possibly done with a hardware assist. • none: A constant number. The --write option rewrites entire pages to disk. If the new checksum is identical to the existing checksum, the new checksum is not written to disk in order to minimize I/O. innochecksum obtains an exclusive lock when the --write option is used. In this example, a crc32 checksum is written for tab1.ibd: innochecksum -w crc32 ../data/test/tab1.ibd In this example, a crc32 checksum is rewritten to replace an invalid crc32 checksum: innochecksum --no-check --write crc32 ../data/test/tab1.ibd • --page-type-summary, -S ┌────────────────────┬─────────────────────┐ │Command-Line Format │ --page-type-summary │ ├────────────────────┼─────────────────────┤ │Type │ Boolean │ ├────────────────────┼─────────────────────┤ │Default Value │ false │ └────────────────────┴─────────────────────┘ Display a count of each page type in a tablespace. Example usage: innochecksum --page-type-summary ../data/test/tab1.ibd Sample output for --page-type-summary: File::../data/test/tab1.ibd ================PAGE TYPE SUMMARY============== #PAGE_COUNT PAGE_TYPE =============================================== 2 Index page 0 Undo log page 1 Inode page 0 Insert buffer free list page 2 Freshly allocated page 1 Insert buffer bitmap 0 System page 0 Transaction system page 1 File Space Header 0 Extent descriptor page 0 BLOB page 0 Compressed BLOB page 0 Other type of page =============================================== Additional information: Undo page type: 0 insert, 0 update, 0 other Undo page state: 0 active, 0 cached, 0 to_free, 0 to_purge, 0 prepared, 0 other • --page-type-dump, -D ┌────────────────────┬───────────────────────┐ │Command-Line Format │ --page-type-dump=name │ ├────────────────────┼───────────────────────┤ │Type │ String │ ├────────────────────┼───────────────────────┤ │Default Value │ [none] │ └────────────────────┴───────────────────────┘ Dump the page type information for each page in a tablespace to stderr or stdout. Example usage: innochecksum --page-type-dump=/tmp/a.txt ../data/test/tab1.ibd • --log, -l ┌────────────────────┬────────────┐ │Command-Line Format │ --log=path │ ├────────────────────┼────────────┤ │Type │ File name │ ├────────────────────┼────────────┤ │Default Value │ [none] │ └────────────────────┴────────────┘ Log output for the innochecksum tool. A log file name must be provided. Log output contains checksum values for each tablespace page. For uncompressed tables, LSN values are also provided. Example usage: innochecksum --log=/tmp/log.txt ../data/test/tab1.ibd or: innochecksum -l /tmp/log.txt ../data/test/tab1.ibd • - option. Specify the - option to read from standard input. If the - option is missing when “read from standard in” is expected, innochecksum prints innochecksum usage information indicating that the “-” option was omitted. Example usages: cat t1.ibd | innochecksum - In this example, innochecksum writes the crc32 checksum algorithm to a.ibd without changing the original t1.ibd file. cat t1.ibd | innochecksum --write=crc32 - > a.ibd Running innochecksum on Multiple User-defined Tablespace Files The following examples demonstrate how to run innochecksum on multiple user-defined tablespace files (.ibd files). Run innochecksum for all tablespace (.ibd) files in the “test” database: innochecksum ./data/test/*.ibd Run innochecksum for all tablespace files (.ibd files) that have a file name starting with “t”: innochecksum ./data/test/t*.ibd Run innochecksum for all tablespace files (.ibd files) in the data directory: innochecksum ./data/*/*.ibd Note Running innochecksum on multiple user-defined tablespace files is not supported on Windows operating systems, as Windows shells such as cmd.exe do not support glob pattern expansion. On Windows systems, innochecksum must be run separately for each user-defined tablespace file. For example: innochecksum.exe t1.ibd innochecksum.exe t2.ibd innochecksum.exe t3.ibd Running innochecksum on Multiple System Tablespace Files By default, there is only one InnoDB system tablespace file (ibdata1) but multiple files for the system tablespace can be defined using the innodb_data_file_path option. In the following example, three files for the system tablespace are defined using the innodb_data_file_path option: ibdata1, ibdata2, and ibdata3. ./bin/mysqld --no-defaults --innodb-data-file-path="ibdata1:10M;ibdata2:10M;ibdata3:10M:autoextend" The three files (ibdata1, ibdata2, and ibdata3) form one logical system tablespace. To run innochecksum on multiple files that form one logical system tablespace, innochecksum requires the - option to read tablespace files in from standard input, which is equivalent to concatenating multiple files to create one single file. For the example provided above, the following innochecksum command would be used: cat ibdata* | innochecksum - Refer to the innochecksum options information for more information about the “-” option. Note Running innochecksum on multiple files in the same tablespace is not supported on Windows operating systems, as Windows shells such as cmd.exe do not support glob pattern expansion. On Windows systems, innochecksum must be run separately for each system tablespace file. For example: innochecksum.exe ibdata1 innochecksum.exe ibdata2 innochecksum.exe ibdata3 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 INNOCHECKSUM(1)
|
innochecksum - offline InnoDB file checksum utility
|
innochecksum [options] file_name
| null | null |
run-with-aspell
|
The recommended way to use Aspell as a replacement for Ispell is to change the Ispell command from within the program being used. If that is not possible, the run-with-aspell script may be used instead.
|
run-with-aspell - script to help use GNU Aspell as an ispell replacement
|
run-with-aspell <command>
|
<command> is the name of the program with any optional arguments. The old method of mapping ispell to Aspell is discouraged because it can create compatibility problems with programs that actually require ispell such as ispell's own scripts. SEE ALSO aspell(1), aspell-import(1), word-list-compress(1) Aspell is fully documented in its Texinfo manual. See the `aspell' entry in info for more complete documentation. AUTHOR This manual page was written by Sudhakar Chandrasekharan <thaths@netscape.com> and Brian Nelson <pyro@debian.org>. GNU 2004-03-03 RUN-WITH-ASPELL(1)
| null |
ollama
| null | null | null | null | null |
danetool
|
Tool to generate and check DNS resource records for the DANE protocol.
|
danetool - GnuTLS DANE tool
|
danetool [-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. --outfile=str Output file. --load-pubkey=str Loads a public key file. This can be either a file or a PKCS #11 URL --load-certificate=str Loads a certificate file. This can be either a file or a PKCS #11 URL --dlv=str Sets a DLV file. This sets a DLV file to be used for DNSSEC verification. --hash=str Hash algorithm to use for signing. Available hash functions are SHA1, RMD160, SHA256, SHA384, SHA512. --check=str Check a host's DANE TLSA entry. Obtains the DANE TLSA entry from the given hostname and prints information. Note that the actual certificate of the host can be provided using --load-certificate, otherwise danetool will connect to the server to obtain it. The exit code on verification success will be zero. --check-ee Check only the end-entity's certificate. Checks the end-entity's certificate only. Trust anchors or CAs are not considered. --check-ca Check only the CA's certificate. Checks the trust anchor's and CA's certificate only. End-entities are not considered. --tlsa-rr Print the DANE RR data on a certificate or public key. This option must appear in combination with the following options: host. This command prints the DANE RR data needed to enable DANE on a DNS server. --host=hostname Specify the hostname to be used in the DANE RR. This command sets the hostname for the DANE RR. --proto=protocol The protocol set for DANE data (tcp, udp etc.). This command specifies the protocol for the service set in the DANE data. --port=str The port or service to connect to, for DANE data. --app-proto This is an alias for the --starttls-proto option. --starttls-proto=str The application protocol to be used to obtain the server's certificate (https, ftp, smtp, imap, ldap, xmpp, lmtp, pop3, nntp, sieve, postgres). When the server's certificate isn't provided danetool will connect to the server to obtain the certificate. In that case it is required to know the protocol to talk with the server prior to initiating the TLS handshake. --ca Whether the provided certificate or public key is a Certificate Authority. Marks the DANE RR as a CA certificate if specified. --x509 Use the hash of the X.509 certificate, rather than the public key. This option forces the generated record to contain the hash of the full X.509 certificate. By default only the hash of the public key is used. --local This is an alias for the --domain option. --domain, --no-domain The provided certificate or public key is issued by the local domain. The no-domain form will disable the option. This option is enabled by default. DANE distinguishes certificates and public keys offered via the DNSSEC to trusted and local entities. This flag indicates that this is a domain-issued certificate, meaning that there could be no CA involved. --local-dns, --no-local-dns Use the local DNS server for DNSSEC resolving. The no-local-dns form will disable the option. This option will use the local DNS server for DNSSEC. This is disabled by default due to many servers not allowing DNSSEC. --insecure Do not verify any DNSSEC signature. Ignores any DNSSEC signature verification results. --inder, --no-inder Use DER format for input certificates and private keys. 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. --print-raw, --no-print-raw Print the received DANE data in raw format. The no-print-raw form will disable the option. This option will print the received DANE data. --quiet Suppress several informational messages. In that case on the exit code can be used as an indication of verification success -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.
|
DANE TLSA RR generation To create a DANE TLSA resource record for a certificate (or public key) that was issued locally and may or may not be signed by a CA use the following command. $ danetool --tlsa-rr --host www.example.com --load-certificate cert.pem To create a DANE TLSA resource record for a CA signed certificate, which will be marked as such use the following command. $ danetool --tlsa-rr --host www.example.com --load-certificate cert.pem --no-domain The former is useful to add in your DNS entry even if your certificate is signed by a CA. That way even users who do not trust your CA will be able to verify your certificate using DANE. In order to create a record for the CA signer of your certificate use the following. $ danetool --tlsa-rr --host www.example.com --load-certificate cert.pem --ca --no-domain To read a server's DANE TLSA entry, use: $ danetool --check www.example.com --proto tcp --port 443 To verify an HTTPS server's DANE TLSA entry, use: $ danetool --check www.example.com --proto tcp --port 443 --load-certificate chain.pem To verify an SMTP server's DANE TLSA entry, use: $ danetool --check www.example.com --proto tcp --starttls-proto=smtp --load-certificate chain.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 certtool (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 danetool(1)
|
mysqlrouter_passwd
|
The mysqlrouter_passwd utility is a command line application to manage the accounts in the passwd file. Usage information: Usage bin/mysqlrouter_passwd [opts] <cmd> <filename> [<username>] bin/mysqlrouter_passwd --help bin/mysqlrouter_passwd --version Commands delete Delete username (if it exists) from <filename>. list list one or all accounts of <filename>. set add or overwrite account of <username> in <filename>. verify verify if password matches <username>'s credentials in <filename>.
|
mysqlrouter_passwd - MySQL Router Password Tool
|
mysqlrouter_passwd [options]
|
-?, --help Display this help and exit. --kdf <name> Key Derivation Function for 'set'. One of pbkdf2-sha256, pbkdf2-sha512, sha256-crypt, sha512-crypt. default: sha256-crypt -V, --version Display version information and exit. --work-factor <num> Work-factor hint for KDF if account is updated. COPYRIGHT Copyright © 2006, 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/. AUTHOR Oracle Corporation (http://dev.mysql.com/). MySQL 8.1 11/22/2023 MYSQLROUTER_PASSWD(1)
| null |
nettle-lfib-stream
| null | null | null | null | null |
gchcon
|
Change the SELinux security context of each FILE to CONTEXT. With --reference, change the security context of each FILE to that of RFILE. Mandatory arguments to long options are mandatory for short options too. --dereference affect the referent of each symbolic link (this is the default), rather than the symbolic link itself -h, --no-dereference affect symbolic links instead of any referenced file -u, --user=USER set user USER in the target security context -r, --role=ROLE set role ROLE in the target security context -t, --type=TYPE set type TYPE in the target security context -l, --range=RANGE set range RANGE in the target security context --no-preserve-root do not treat '/' specially (the default) --preserve-root fail to operate recursively on '/' --reference=RFILE use RFILE's security context rather than specifying a CONTEXT value -R, --recursive operate on files and directories recursively -v, --verbose output a diagnostic for every file processed The following options modify how a hierarchy is traversed when the -R option is also specified. If more than one is specified, only the final one takes effect. -H if a command line argument is a symbolic link to a directory, traverse it -L traverse every symbolic link to a directory encountered -P do not traverse any symbolic links (default) --help display this help and exit --version output version information and exit AUTHOR Written by Russell Coker 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/chcon> or available locally via: info '(coreutils) chcon invocation' GNU coreutils 9.3 April 2023 CHCON(1)
|
chcon - change file security context
|
chcon [OPTION]... CONTEXT FILE... chcon [OPTION]... [-u USER] [-r ROLE] [-l RANGE] [-t TYPE] FILE... chcon [OPTION]... --reference=RFILE FILE...
| null | null |
virtualenv
| null | null | null | null | null |
enum_options
| null | null | null | null | null |
django-admin
| null | null | null | null | null |
pngtogd
| null | null | null | null | null |
saved_model_cli
| null | null | null | null | null |
ismindex
| null | null | null | null | null |
openssl
|
OpenSSL is a cryptography toolkit implementing the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) network protocols and related cryptography standards required by them. The openssl program is a command line program for using the various cryptography functions of OpenSSL's crypto library from the shell. It can be used for o Creation and management of private keys, public keys and parameters o Public key cryptographic operations o Creation of X.509 certificates, CSRs and CRLs o Calculation of Message Digests and Message Authentication Codes o Encryption and Decryption with Ciphers o SSL/TLS Client and Server Tests o Handling of S/MIME signed or encrypted mail o Timestamp requests, generation and verification COMMAND SUMMARY The openssl program provides a rich variety of commands (command in the "SYNOPSIS" above). Each command can have many options and argument parameters, shown above as options and parameters. Detailed documentation and use cases for most standard subcommands are available (e.g., openssl-x509(1)). The subcommand openssl-list(1) may be used to list subcommands. The command no-XXX tests whether a command of the specified name is available. If no command named XXX exists, it returns 0 (success) and prints no-XXX; otherwise it returns 1 and prints XXX. In both cases, the output goes to stdout and nothing is printed to stderr. Additional command line arguments are always ignored. Since for each cipher there is a command of the same name, this provides an easy way for shell scripts to test for the availability of ciphers in the openssl program. (no-XXX is not able to detect pseudo-commands such as quit, list, or no-XXX itself.) Configuration Option Many commands use an external configuration file for some or all of their arguments and have a -config option to specify that file. The default name of the file is openssl.cnf in the default certificate storage area, which can be determined from the openssl-version(1) command using the -d or -a option. The environment variable OPENSSL_CONF can be used to specify a different file location or to disable loading a configuration (using the empty string). Among others, the configuration file can be used to load modules and to specify parameters for generating certificates and random numbers. See config(5) for details. Standard Commands asn1parse Parse an ASN.1 sequence. ca Certificate Authority (CA) Management. ciphers Cipher Suite Description Determination. cms CMS (Cryptographic Message Syntax) command. crl Certificate Revocation List (CRL) Management. crl2pkcs7 CRL to PKCS#7 Conversion. dgst Message Digest calculation. MAC calculations are superseded by openssl-mac(1). dhparam Generation and Management of Diffie-Hellman Parameters. Superseded by openssl-genpkey(1) and openssl-pkeyparam(1). dsa DSA Data Management. dsaparam DSA Parameter Generation and Management. Superseded by openssl-genpkey(1) and openssl-pkeyparam(1). ec EC (Elliptic curve) key processing. ecparam EC parameter manipulation and generation. enc Encryption, decryption, and encoding. engine Engine (loadable module) information and manipulation. errstr Error Number to Error String Conversion. fipsinstall FIPS configuration installation. gendsa Generation of DSA Private Key from Parameters. Superseded by openssl-genpkey(1) and openssl-pkey(1). genpkey Generation of Private Key or Parameters. genrsa Generation of RSA Private Key. Superseded by openssl-genpkey(1). help Display information about a command's options. info Display diverse information built into the OpenSSL libraries. kdf Key Derivation Functions. list List algorithms and features. mac Message Authentication Code Calculation. nseq Create or examine a Netscape certificate sequence. ocsp Online Certificate Status Protocol command. passwd Generation of hashed passwords. pkcs12 PKCS#12 Data Management. pkcs7 PKCS#7 Data Management. pkcs8 PKCS#8 format private key conversion command. pkey Public and private key management. pkeyparam Public key algorithm parameter management. pkeyutl Public key algorithm cryptographic operation command. prime Compute prime numbers. rand Generate pseudo-random bytes. rehash Create symbolic links to certificate and CRL files named by the hash values. req PKCS#10 X.509 Certificate Signing Request (CSR) Management. rsa RSA key management. rsautl RSA command for signing, verification, encryption, and decryption. Superseded by openssl-pkeyutl(1). s_client This implements a generic SSL/TLS client which can establish a transparent connection to a remote server speaking SSL/TLS. It's intended for testing purposes only and provides only rudimentary interface functionality but internally uses mostly all functionality of the OpenSSL ssl library. s_server This implements a generic SSL/TLS server which accepts connections from remote clients speaking SSL/TLS. It's intended for testing purposes only and provides only rudimentary interface functionality but internally uses mostly all functionality of the OpenSSL ssl library. It provides both an own command line oriented protocol for testing SSL functions and a simple HTTP response facility to emulate an SSL/TLS-aware webserver. s_time SSL Connection Timer. sess_id SSL Session Data Management. smime S/MIME mail processing. speed Algorithm Speed Measurement. spkac SPKAC printing and generating command. srp Maintain SRP password file. This command is deprecated. storeutl Command to list and display certificates, keys, CRLs, etc. ts Time Stamping Authority command. verify X.509 Certificate Verification. See also the openssl-verification-options(1) manual page. version OpenSSL Version Information. x509 X.509 Certificate Data Management. Message Digest Commands blake2b512 BLAKE2b-512 Digest blake2s256 BLAKE2s-256 Digest md2 MD2 Digest md4 MD4 Digest md5 MD5 Digest mdc2 MDC2 Digest rmd160 RMD-160 Digest sha1 SHA-1 Digest sha224 SHA-2 224 Digest sha256 SHA-2 256 Digest sha384 SHA-2 384 Digest sha512 SHA-2 512 Digest sha3-224 SHA-3 224 Digest sha3-256 SHA-3 256 Digest sha3-384 SHA-3 384 Digest sha3-512 SHA-3 512 Digest keccak-224 KECCAK 224 Digest keccak-256 KECCAK 256 Digest keccak-384 KECCAK 384 Digest keccak-512 KECCAK 512 Digest shake128 SHA-3 SHAKE128 Digest shake256 SHA-3 SHAKE256 Digest sm3 SM3 Digest Encryption, Decryption, and Encoding Commands The following aliases provide convenient access to the most used encodings and ciphers. Depending on how OpenSSL was configured and built, not all ciphers listed here may be present. See openssl-enc(1) for more information. aes128, aes-128-cbc, aes-128-cfb, aes-128-ctr, aes-128-ecb, aes-128-ofb AES-128 Cipher aes192, aes-192-cbc, aes-192-cfb, aes-192-ctr, aes-192-ecb, aes-192-ofb AES-192 Cipher aes256, aes-256-cbc, aes-256-cfb, aes-256-ctr, aes-256-ecb, aes-256-ofb AES-256 Cipher aria128, aria-128-cbc, aria-128-cfb, aria-128-ctr, aria-128-ecb, aria-128-ofb Aria-128 Cipher aria192, aria-192-cbc, aria-192-cfb, aria-192-ctr, aria-192-ecb, aria-192-ofb Aria-192 Cipher aria256, aria-256-cbc, aria-256-cfb, aria-256-ctr, aria-256-ecb, aria-256-ofb Aria-256 Cipher base64 Base64 Encoding bf, bf-cbc, bf-cfb, bf-ecb, bf-ofb Blowfish Cipher camellia128, camellia-128-cbc, camellia-128-cfb, camellia-128-ctr, camellia-128-ecb, camellia-128-ofb Camellia-128 Cipher camellia192, camellia-192-cbc, camellia-192-cfb, camellia-192-ctr, camellia-192-ecb, camellia-192-ofb Camellia-192 Cipher camellia256, camellia-256-cbc, camellia-256-cfb, camellia-256-ctr, camellia-256-ecb, camellia-256-ofb Camellia-256 Cipher cast, cast-cbc CAST Cipher cast5-cbc, cast5-cfb, cast5-ecb, cast5-ofb CAST5 Cipher chacha20 Chacha20 Cipher des, des-cbc, des-cfb, des-ecb, des-ede, des-ede-cbc, des-ede-cfb, des-ede-ofb, des-ofb DES Cipher des3, desx, des-ede3, des-ede3-cbc, des-ede3-cfb, des-ede3-ofb Triple-DES Cipher idea, idea-cbc, idea-cfb, idea-ecb, idea-ofb IDEA Cipher rc2, rc2-cbc, rc2-cfb, rc2-ecb, rc2-ofb RC2 Cipher rc4 RC4 Cipher rc5, rc5-cbc, rc5-cfb, rc5-ecb, rc5-ofb RC5 Cipher seed, seed-cbc, seed-cfb, seed-ecb, seed-ofb SEED Cipher sm4, sm4-cbc, sm4-cfb, sm4-ctr, sm4-ecb, sm4-ofb SM4 Cipher
|
openssl - OpenSSL command line program
|
openssl command [ options ... ] [ parameters ... ] openssl no-XXX [ options ] openssl -help | -version
|
Details of which options are available depend on the specific command. This section describes some common options with common behavior. Program Options These options can be specified without a command specified to get help or version information. -help Provides a terse summary of all options. For more detailed information, each command supports a -help option. Accepts --help as well. -version Provides a terse summary of the openssl program version. For more detailed information see openssl-version(1). Accepts --version as well. Common Options -help If an option takes an argument, the "type" of argument is also given. -- This terminates the list of options. It is mostly useful if any filename parameters start with a minus sign: openssl verify [flags...] -- -cert1.pem... Format Options See openssl-format-options(1) for manual page. Pass Phrase Options See the openssl-passphrase-options(1) manual page. Random State Options Prior to OpenSSL 1.1.1, it was common for applications to store information about the state of the random-number generator in a file that was loaded at startup and rewritten upon exit. On modern operating systems, this is generally no longer necessary as OpenSSL will seed itself from a trusted entropy source provided by the operating system. These flags are still supported for special platforms or circumstances that might require them. It is generally an error to use the same seed file more than once and every use of -rand should be paired with -writerand. -rand files A file or files containing random data used to seed the random number generator. Multiple files can be specified separated by an OS-dependent character. The separator is ";" for MS-Windows, "," for OpenVMS, and ":" for all others. Another way to specify multiple files is to repeat this flag with different filenames. -writerand file Writes the seed data to the specified file upon exit. This file can be used in a subsequent command invocation. Certificate Verification Options See the openssl-verification-options(1) manual page. Name Format Options See the openssl-namedisplay-options(1) manual page. TLS Version Options Several commands use SSL, TLS, or DTLS. By default, the commands use TLS and clients will offer the lowest and highest protocol version they support, and servers will pick the highest version that the client offers that is also supported by the server. The options below can be used to limit which protocol versions are used, and whether TCP (SSL and TLS) or UDP (DTLS) is used. Note that not all protocols and flags may be available, depending on how OpenSSL was built. -ssl3, -tls1, -tls1_1, -tls1_2, -tls1_3, -no_ssl3, -no_tls1, -no_tls1_1, -no_tls1_2, -no_tls1_3 These options require or disable the use of the specified SSL or TLS protocols. When a specific TLS version is required, only that version will be offered or accepted. Only one specific protocol can be given and it cannot be combined with any of the no_ options. The no_* options do not work with s_time and ciphers commands but work with s_client and s_server commands. -dtls, -dtls1, -dtls1_2 These options specify to use DTLS instead of TLS. With -dtls, clients will negotiate any supported DTLS protocol version. Use the -dtls1 or -dtls1_2 options to support only DTLS1.0 or DTLS1.2, respectively. Engine Options -engine id Load the engine identified by id and use all the methods it implements (algorithms, key storage, etc.), unless specified otherwise in the command-specific documentation or it is configured to do so, as described in "Engine Configuration" in config(5). The engine will be used for key ids specified with -key and similar options when an option like -keyform engine is given. A special case is the "loader_attic" engine, which is meant just for internal OpenSSL testing purposes and supports loading keys, parameters, certificates, and CRLs from files. When this engine is used, files with such credentials are read via this engine. Using the "file:" schema is optional; a plain file (path) name will do. Options specifying keys, like -key and similar, can use the generic OpenSSL engine key loading URI scheme "org.openssl.engine:" to retrieve private keys and public keys. The URI syntax is as follows, in simplified form: org.openssl.engine:{engineid}:{keyid} Where "{engineid}" is the identity/name of the engine, and "{keyid}" is a key identifier that's acceptable by that engine. For example, when using an engine that interfaces against a PKCS#11 implementation, the generic key URI would be something like this (this happens to be an example for the PKCS#11 engine that's part of OpenSC): -key org.openssl.engine:pkcs11:label_some-private-key As a third possibility, for engines and providers that have implemented their own OSSL_STORE_LOADER(3), "org.openssl.engine:" should not be necessary. For a PKCS#11 implementation that has implemented such a loader, the PKCS#11 URI as defined in RFC 7512 should be possible to use directly: -key pkcs11:object=some-private-key;pin-value=1234 Provider Options -provider name Load and initialize the provider identified by name. The name can be also a path to the provider module. In that case the provider name will be the specified path and not just the provider module name. Interpretation of relative paths is platform specific. The configured "MODULESDIR" path, OPENSSL_MODULES environment variable, or the path specified by -provider-path is prepended to relative paths. See provider(7) for a more detailed description. -provider-path path Specifies the search path that is to be used for looking for providers. Equivalently, the OPENSSL_MODULES environment variable may be set. -propquery propq Specifies the property query clause to be used when fetching algorithms from the loaded providers. See property(7) for a more detailed description. ENVIRONMENT The OpenSSL library can be take some configuration parameters from the environment. Some of these variables are listed below. For information about specific commands, see openssl-engine(1), openssl-rehash(1), and tsget(1). For information about the use of environment variables in configuration, see "ENVIRONMENT" in config(5). For information about querying or specifying CPU architecture flags, see OPENSSL_ia32cap(3), and OPENSSL_s390xcap(3). For information about all environment variables used by the OpenSSL libraries, see openssl-env(7). OPENSSL_TRACE=name[,...] Enable tracing output of OpenSSL library, by name. This output will only make sense if you know OpenSSL internals well. Also, it might not give you any output at all if OpenSSL was built without tracing support. The value is a comma separated list of names, with the following available: TRACE Traces the OpenSSL trace API itself. INIT Traces OpenSSL library initialization and cleanup. TLS Traces the TLS/SSL protocol. TLS_CIPHER Traces the ciphers used by the TLS/SSL protocol. CONF Show details about provider and engine configuration. ENGINE_TABLE The function that is used by RSA, DSA (etc) code to select registered ENGINEs, cache defaults and functional references (etc), will generate debugging summaries. ENGINE_REF_COUNT Reference counts in the ENGINE structure will be monitored with a line of generated for each change. PKCS5V2 Traces PKCS#5 v2 key generation. PKCS12_KEYGEN Traces PKCS#12 key generation. PKCS12_DECRYPT Traces PKCS#12 decryption. X509V3_POLICY Generates the complete policy tree at various points during X.509 v3 policy evaluation. BN_CTX Traces BIGNUM context operations. CMP Traces CMP client and server activity. STORE Traces STORE operations. DECODER Traces decoder operations. ENCODER Traces encoder operations. REF_COUNT Traces decrementing certain ASN.1 structure references. HTTP Traces the HTTP client and server, such as messages being sent and received. SEE ALSO openssl-asn1parse(1), openssl-ca(1), openssl-ciphers(1), openssl-cms(1), openssl-crl(1), openssl-crl2pkcs7(1), openssl-dgst(1), openssl-dhparam(1), openssl-dsa(1), openssl-dsaparam(1), openssl-ec(1), openssl-ecparam(1), openssl-enc(1), openssl-engine(1), openssl-errstr(1), openssl-gendsa(1), openssl-genpkey(1), openssl-genrsa(1), openssl-kdf(1), openssl-list(1), openssl-mac(1), openssl-nseq(1), openssl-ocsp(1), openssl-passwd(1), openssl-pkcs12(1), openssl-pkcs7(1), openssl-pkcs8(1), openssl-pkey(1), openssl-pkeyparam(1), openssl-pkeyutl(1), openssl-prime(1), openssl-rand(1), openssl-rehash(1), openssl-req(1), openssl-rsa(1), openssl-rsautl(1), openssl-s_client(1), openssl-s_server(1), openssl-s_time(1), openssl-sess_id(1), openssl-smime(1), openssl-speed(1), openssl-spkac(1), openssl-srp(1), openssl-storeutl(1), openssl-ts(1), openssl-verify(1), openssl-version(1), openssl-x509(1), config(5), crypto(7), openssl-env(7). ssl(7), x509v3_config(5) HISTORY The list -XXX-algorithms options were added in OpenSSL 1.0.0; For notes on the availability of other commands, see their individual manual pages. The -issuer_checks option is deprecated as of OpenSSL 1.1.0 and is silently ignored. The -xcertform and -xkeyform options are obsolete since OpenSSL 3.0 and have no effect. The interactive mode, which could be invoked by running "openssl" with no further arguments, was removed in OpenSSL 3.0, and running that program with no arguments is now equivalent to "openssl help". COPYRIGHT Copyright 2000-2023 The OpenSSL Project Authors. All Rights Reserved. Licensed under the Apache License 2.0 (the "License"). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at <https://www.openssl.org/source/license.html>. 3.3.1 2024-06-04 OPENSSL(1ssl)
| null |
rust-gdb
| null | null | null | null | null |
sndfile-metadata-get
|
sndfile-metadata-get displays bext and string metadata stored in an audio file. The following options specify what to print. --all all metadata --bext-description description --bext-originator originator info --bext-orig-ref originator reference --bext-umid Unique Material Identifier --bext-orig-date origination date --bext-orig-time origination time --bext-coding-hist coding history --str-title title --str-copyright copyright --str-artist artist --str-comment comment --str-date creation date --str-album album --str-license license sndfile-metadata-set sets bext and string metadata in an audio file if the format supports it. If the file does not contain a BEXT chunk to be modified, the second synopsis must be used, where another output file capable of storing the metadata is created. This file is overwritten if it already exists. The following options take an argument specifying the metadata: --bext-description description --bext-originator originator --bext-orig-ref originator reference --bext-umid Unique Material Identifier --bext-orig-date origination date --bext-orig-time origination time --bext-coding-hist coding history --bext-time-raf time reference --str-comment comment --str-title title --str-copyright copyright --str-artist artist --str-date date --str-album album --str-license license The following options take no argument: --bext-auto-time-date Set the BEXT time and date to current. --bext-auto-time Set the BEXT time to current. --bext-auto-date Set the BEXT date to current. --str-auto-date Set the string date to current. EXIT STATUS The sndfile-metadata-get utility exits 0 on success, and >0 if an error occurs. SEE ALSO http://libsndfile.github.io/libsndfile/ http://tech.ebu.ch/docs/tech/tech3285.pdf AUTHORS Erik de Castro Lopo <erikd@mega-nerd.com> macOS 14.5 November 2, 2014 macOS 14.5
|
sndfile-metadata-get, sndfile-metadata-set – get or set metadata in a sound file
|
sndfile-metadata-get [options] file sndfile-metadata-set [options] file sndfile-metadata-set [options] input output
| null | null |
hb-info
| null | null | null | null | null |
key_ladder_demo
| null | null | null | null | null |
exrenvmap
| null | null | null | null | null |
glogname
|
Print the user's login name. --help display this help and exit --version output version information and exit AUTHOR Written by FIXME: unknown. 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 getlogin(3) Full documentation <https://www.gnu.org/software/coreutils/logname> or available locally via: info '(coreutils) logname invocation' GNU coreutils 9.3 April 2023 LOGNAME(1)
|
logname - print user´s login name
|
logname [OPTION]
| null | null |
rbenv-install
| null | null | null | null | null |
cpuinfo
| null | null | null | null | null |
mysqladmin
|
mysqladmin is a client for performing administrative operations. You can use it to check the server's configuration and current status, to create and drop databases, and more. Invoke mysqladmin like this: mysqladmin [options] command [command-arg] [command [command-arg]] ... mysqladmin supports the following commands. Some of the commands take an argument following the command name. • create db_name Create a new database named db_name. • debug Prior to MySQL 8.0.20, tell the server to write debug information to the error log. The connected user must have the SUPER privilege. Format and content of this information is subject to change. This includes information about the Event Scheduler. See Section 25.4.5, “Event Scheduler Status”. • drop db_name Delete the database named db_name and all its tables. • extended-status Display the server status variables and their values. • flush-hosts Flush all information in the host cache. See Section 5.1.12.3, “DNS Lookups and the Host Cache”. • flush-logs [log_type ...] Flush all logs. The mysqladmin flush-logs command permits optional log types to be given, to specify which logs to flush. Following the flush-logs command, you can provide a space-separated list of one or more of the following log types: binary, engine, error, general, relay, slow. These correspond to the log types that can be specified for the FLUSH LOGS SQL statement. • flush-privileges Reload the grant tables (same as reload). • flush-status Clear status variables. • flush-tables Flush all tables. • kill id,id,... Kill server threads. If multiple thread ID values are given, there must be no spaces in the list. To kill threads belonging to other users, the connected user must have the CONNECTION_ADMIN privilege (or the deprecated SUPER privilege). • password new_password Set a new password. This changes the password to new_password for the account that you use with mysqladmin for connecting to the server. Thus, the next time you invoke mysqladmin (or any other client program) using the same account, you must specify the new password. Warning Setting a password using mysqladmin should be considered insecure. On some systems, your password becomes visible to system status programs such as ps that may be invoked by other users to display command lines. MySQL clients typically overwrite the command-line password argument with zeros during their initialization sequence. However, there is still a brief interval during which the value is visible. Also, on some systems this overwriting strategy is ineffective and the password remains visible to ps. (SystemV Unix systems and perhaps others are subject to this problem.) If the new_password value contains spaces or other characters that are special to your command interpreter, you need to enclose it within quotation marks. On Windows, be sure to use double quotation marks rather than single quotation marks; single quotation marks are not stripped from the password, but rather are interpreted as part of the password. For example: mysqladmin password "my new password" The new password can be omitted following the password command. In this case, mysqladmin prompts for the password value, which enables you to avoid specifying the password on the command line. Omitting the password value should be done only if password is the final command on the mysqladmin command line. Otherwise, the next argument is taken as the password. Caution Do not use this command used if the server was started with the --skip-grant-tables option. No password change is applied. This is true even if you precede the password command with flush-privileges on the same command line to re-enable the grant tables because the flush operation occurs after you connect. However, you can use mysqladmin flush-privileges to re-enable the grant table and then use a separate mysqladmin password command to change the password. • ping Check whether the server is available. The return status from mysqladmin is 0 if the server is running, 1 if it is not. This is 0 even in case of an error such as Access denied, because this means that the server is running but refused the connection, which is different from the server not running. • processlist Show a list of active server threads. This is like the output of the SHOW PROCESSLIST statement. If the --verbose option is given, the output is like that of SHOW FULL PROCESSLIST. (See Section 13.7.7.31, “SHOW PROCESSLIST Statement”.) • reload Reload the grant tables. • refresh Flush all tables and close and open log files. • shutdown Stop the server. • start-replica Start replication on a replica server. • start-slave This is a deprecated alias for start-replica. • status Display a short server status message. • stop-replica Stop replication on a replica server. • stop-slave This is a deprecated alias for stop-replica. • variables Display the server system variables and their values. • version Display version information from the server. All commands can be shortened to any unique prefix. For example: $> mysqladmin proc stat +----+-------+-----------+----+---------+------+-------+------------------+ | Id | User | Host | db | Command | Time | State | Info | +----+-------+-----------+----+---------+------+-------+------------------+ | 51 | jones | localhost | | Query | 0 | | show processlist | +----+-------+-----------+----+---------+------+-------+------------------+ Uptime: 1473624 Threads: 1 Questions: 39487 Slow queries: 0 Opens: 541 Flush tables: 1 Open tables: 19 Queries per second avg: 0.0268 The mysqladmin status command result displays the following values: • Uptime The number of seconds the MySQL server has been running. • Threads The number of active threads (clients). • Questions The number of questions (queries) from clients since the server was started. • Slow queries The number of queries that have taken more than long_query_time seconds. See Section 5.4.5, “The Slow Query Log”. • Opens The number of tables the server has opened. • Flush tables The number of flush-*, refresh, and reload commands the server has executed. • Open tables The number of tables that currently are open. If you execute mysqladmin shutdown when connecting to a local server using a Unix socket file, mysqladmin waits until the server's process ID file has been removed, to ensure that the server has stopped properly. mysqladmin supports the following options, which can be specified on the command line or in the [mysqladmin] 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”. • --connect-timeout=value ┌────────────────────┬─────────────────────────┐ │Command-Line Format │ --connect-timeout=value │ ├────────────────────┼─────────────────────────┤ │Type │ Numeric │ ├────────────────────┼─────────────────────────┤ │Default Value │ 43200 │ └────────────────────┴─────────────────────────┘ The maximum number of seconds before connection timeout. The default value is 43200 (12 hours). • --count=N, -c N ┌────────────────────┬───────────┐ │Command-Line Format │ --count=# │ └────────────────────┴───────────┘ The number of iterations to make for repeated command execution if the --sleep option is given. • --debug[=debug_options], -# [debug_options] ┌────────────────────┬─────────────────────────────┐ │Command-Line Format │ --debug[=debug_options] │ ├────────────────────┼─────────────────────────────┤ │Type │ String │ ├────────────────────┼─────────────────────────────┤ │Default Value │ d:t:o,/tmp/mysqladmin.trace │ └────────────────────┴─────────────────────────────┘ Write a debugging log. A typical debug_options string is d:t:o,file_name. The default is d:t:o,/tmp/mysqladmin.trace. 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-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”. • --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”. • --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, mysqladmin normally reads the [client] and [mysqladmin] groups. If this option is given as --defaults-group-suffix=_other, mysqladmin also reads the [client_other] and [mysqladmin_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”.) • --force, -f ┌────────────────────┬─────────┐ │Command-Line Format │ --force │ └────────────────────┴─────────┘ Do not ask for confirmation for the drop db_name command. With multiple commands, continue even if an error occurs. • --get-server-public-key ┌────────────────────┬─────────────────────────┐ │Command-Line Format │ --get-server-public-key │ ├────────────────────┼─────────────────────────┤ │Type │ Boolean │ └────────────────────┴─────────────────────────┘ Request from the server the public key required for RSA key pair-based password exchange. This option applies to clients that authenticate with the caching_sha2_password authentication plugin. For that plugin, the server does not send the public key unless requested. This option is ignored for accounts that do not authenticate with that plugin. 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 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. • --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-beep, -b ┌────────────────────┬───────────┐ │Command-Line Format │ --no-beep │ └────────────────────┴───────────┘ Suppress the warning beep that is emitted by default for errors such as a failure to connect to the server. • --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, mysqladmin 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 mysqladmin 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, mysql 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 mysqladmin 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 mysqladmin 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”. • --relative, -r ┌────────────────────┬────────────┐ │Command-Line Format │ --relative │ └────────────────────┴────────────┘ Show the difference between the current and previous values when used with the --sleep option. This option works only with the extended-status command. • --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-warnings ┌────────────────────┬─────────────────┐ │Command-Line Format │ --show-warnings │ └────────────────────┴─────────────────┘ Show warnings resulting from execution of statements sent to the server. • --shutdown-timeout=value ┌────────────────────┬────────────────────────────┐ │Command-Line Format │ --shutdown-timeout=seconds │ ├────────────────────┼────────────────────────────┤ │Type │ Numeric │ ├────────────────────┼────────────────────────────┤ │Default Value │ 3600 │ └────────────────────┴────────────────────────────┘ The maximum number of seconds to wait for server shutdown. The default value is 3600 (1 hour). • --silent, -s ┌────────────────────┬──────────┐ │Command-Line Format │ --silent │ └────────────────────┴──────────┘ Exit silently if a connection to the server cannot be established. • --sleep=delay, -i delay ┌────────────────────┬───────────────┐ │Command-Line Format │ --sleep=delay │ └────────────────────┴───────────────┘ Execute commands repeatedly, sleeping for delay seconds in between. The --count option determines the number of iterations. If --count is not given, mysqladmin executes commands indefinitely until interrupted. • --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. • --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. If you are using the Rewriter plugin, grant this user the SKIP_QUERY_REWRITE privilege. • --verbose, -v ┌────────────────────┬───────────┐ │Command-Line Format │ --verbose │ └────────────────────┴───────────┘ Verbose mode. Print more information about what the program does. • --version, -V ┌────────────────────┬───────────┐ │Command-Line Format │ --version │ └────────────────────┴───────────┘ Display version information and exit. • --vertical, -E ┌────────────────────┬────────────┐ │Command-Line Format │ --vertical │ └────────────────────┴────────────┘ Print output vertically. This is similar to --relative, but prints output vertically. • --wait[=count], -w[count] ┌────────────────────┬────────┐ │Command-Line Format │ --wait │ └────────────────────┴────────┘ If the connection cannot be established, wait and retry instead of aborting. If a count value is given, it indicates the number of times to retry. The default is one time. • --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 MYSQLADMIN(1)
|
mysqladmin - a MySQL server administration program
|
mysqladmin [options] command [command-options] [command [command-options]] ...
| null | null |
splain
|
The "diagnostics" Pragma This module extends the terse diagnostics normally emitted by both the perl compiler and the perl interpreter (from running perl with a -w switch or "use warnings"), augmenting them with the more explicative and endearing descriptions found in perldiag. Like the other pragmata, it affects the compilation phase of your program rather than merely the execution phase. To use in your program as a pragma, merely invoke use diagnostics; at the start (or near the start) of your program. (Note that this does enable perl's -w flag.) Your whole compilation will then be subject(ed :-) to the enhanced diagnostics. These still go out STDERR. Due to the interaction between runtime and compiletime issues, and because it's probably not a very good idea anyway, you may not use "no diagnostics" to turn them off at compiletime. However, you may control their behaviour at runtime using the disable() and enable() methods to turn them off and on respectively. The -verbose flag first prints out the perldiag introduction before any other diagnostics. The $diagnostics::PRETTY variable can generate nicer escape sequences for pagers. Warnings dispatched from perl itself (or more accurately, those that match descriptions found in perldiag) are only displayed once (no duplicate descriptions). User code generated warnings a la warn() are unaffected, allowing duplicate user messages to be displayed. This module also adds a stack trace to the error message when perl dies. This is useful for pinpointing what caused the death. The -traceonly (or just -t) flag turns off the explanations of warning messages leaving just the stack traces. So if your script is dieing, run it again with perl -Mdiagnostics=-traceonly my_bad_script to see the call stack at the time of death. By supplying the -warntrace (or just -w) flag, any warnings emitted will also come with a stack trace. The splain Program Another program, splain is actually nothing more than a link to the (executable) diagnostics.pm module, as well as a link to the diagnostics.pod documentation. The -v flag is like the "use diagnostics -verbose" directive. The -p flag is like the $diagnostics::PRETTY variable. Since you're post-processing with splain, there's no sense in being able to enable() or disable() processing. Output from splain is directed to STDOUT, unlike the pragma.
|
diagnostics, splain - produce verbose warning diagnostics
|
Using the "diagnostics" pragma: use diagnostics; use diagnostics -verbose; enable diagnostics; disable diagnostics; Using the "splain" standalone filter program: perl program 2>diag.out splain [-v] [-p] diag.out Using diagnostics to get stack traces from a misbehaving script: perl -Mdiagnostics=-traceonly my_script.pl
| null |
The following file is certain to trigger a few errors at both runtime and compiletime: use diagnostics; print NOWHERE "nothing\n"; print STDERR "\n\tThis message should be unadorned.\n"; warn "\tThis is a user warning"; print "\nDIAGNOSTIC TESTER: Please enter a <CR> here: "; my $a, $b = scalar <STDIN>; print "\n"; print $x/$y; If you prefer to run your program first and look at its problem afterwards, do this: perl -w test.pl 2>test.out ./splain < test.out Note that this is not in general possible in shells of more dubious heritage, as the theoretical (perl -w test.pl >/dev/tty) >& test.out ./splain < test.out Because you just moved the existing stdout to somewhere else. If you don't want to modify your source code, but still have on-the-fly warnings, do this: exec 3>&1; perl -w test.pl 2>&1 1>&3 3>&- | splain 1>&2 3>&- Nifty, eh? If you want to control warnings on the fly, do something like this. Make sure you do the "use" first, or you won't be able to get at the enable() or disable() methods. use diagnostics; # checks entire compilation phase print "\ntime for 1st bogus diags: SQUAWKINGS\n"; print BOGUS1 'nada'; print "done with 1st bogus\n"; disable diagnostics; # only turns off runtime warnings print "\ntime for 2nd bogus: (squelched)\n"; print BOGUS2 'nada'; print "done with 2nd bogus\n"; enable diagnostics; # turns back on runtime warnings print "\ntime for 3rd bogus: SQUAWKINGS\n"; print BOGUS3 'nada'; print "done with 3rd bogus\n"; disable diagnostics; print "\ntime for 4th bogus: (squelched)\n"; print BOGUS4 'nada'; print "done with 4th bogus\n"; INTERNALS Diagnostic messages derive from the perldiag.pod file when available at runtime. Otherwise, they may be embedded in the file itself when the splain package is built. See the Makefile for details. If an extant $SIG{__WARN__} handler is discovered, it will continue to be honored, but only after the diagnostics::splainthis() function (the module's $SIG{__WARN__} interceptor) has had its way with your warnings. There is a $diagnostics::DEBUG variable you may set if you're desperately curious what sorts of things are being intercepted. BEGIN { $diagnostics::DEBUG = 1 } BUGS Not being able to say "no diagnostics" is annoying, but may not be insurmountable. The "-pretty" directive is called too late to affect matters. You have to do this instead, and before you load the module. BEGIN { $diagnostics::PRETTY = 1 } I could start up faster by delaying compilation until it should be needed, but this gets a "panic: top_level" when using the pragma form in Perl 5.001e. While it's true that this documentation is somewhat subserious, if you use a program named splain, you should expect a bit of whimsy. AUTHOR Tom Christiansen <tchrist@mox.perl.com>, 25 June 1995. perl v5.38.2 2023-11-28 SPLAIN(1)
|
msgfilter
|
Applies a filter to all translations of a translation catalog. Mandatory arguments to long options are mandatory for short options too. Input file location: -i, --input=INPUTFILE input PO file -D, --directory=DIRECTORY add DIRECTORY to list for input files search If no input file is given or if it is -, standard input is read. Output file location: -o, --output-file=FILE write output to specified file The results are written to standard output if no output file is specified or if it is -. The FILTER can be any program that reads a translation from standard input and writes a modified translation to standard output. Filter input and output: --newline add a newline at the end of input and remove a newline from the end of output Useful FILTER-OPTIONs when the FILTER is 'sed': -e, --expression=SCRIPT add SCRIPT to the commands to be executed -f, --file=SCRIPTFILE add the contents of SCRIPTFILE to the commands to be executed -n, --quiet, --silent suppress automatic printing of pattern space Input file syntax: -P, --properties-input input file is in Java .properties syntax --stringtable-input input file is in NeXTstep/GNUstep .strings syntax Output details: --color use colors and other text attributes always --color=WHEN use colors and other text attributes if WHEN. WHEN may be 'always', 'never', 'auto', or 'html'. --style=STYLEFILE specify CSS style rule file for --color --no-escape do not use C escapes in output (default) -E, --escape use C escapes in output, no extended chars --force-po write PO file even if empty --indent indented output style --keep-header keep header entry unmodified, don't filter it --no-location suppress '#: filename:line' lines -n, --add-location preserve '#: filename:line' lines (default) --strict strict Uniforum output style -p, --properties-output write out a Java .properties file --stringtable-output write out a NeXTstep/GNUstep .strings file -w, --width=NUMBER set output page width --no-wrap do not break long message lines, longer than the output page width, into several lines -s, --sort-output generate sorted output -F, --sort-by-file sort output by file location Informative output: -h, --help display this help and exit -V, --version output version information and exit AUTHOR Written by Bruno Haible. REPORTING BUGS Report bugs in the bug tracker at <https://savannah.gnu.org/projects/gettext> or by email to <bug-gettext@gnu.org>. COPYRIGHT Copyright © 2001-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 The full documentation for msgfilter is maintained as a Texinfo manual. If the info and msgfilter programs are properly installed at your site, the command info msgfilter should give you access to the complete manual. GNU gettext-tools 0.22.5 February 2024 MSGFILTER(1)
|
msgfilter - edit translations of message catalog
|
msgfilter [OPTION] FILTER [FILTER-OPTION]
| null | null |
guname
|
Print certain system information. With no OPTION, same as -s. -a, --all print all information, in the following order, except omit -p and -i if unknown: -s, --kernel-name print the kernel name -n, --nodename print the network node hostname -r, --kernel-release print the kernel release -v, --kernel-version print the kernel version -m, --machine print the machine hardware name -p, --processor print the processor type (non-portable) -i, --hardware-platform print the hardware platform (non-portable) -o, --operating-system print the operating system --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 arch(1), uname(2) Full documentation <https://www.gnu.org/software/coreutils/uname> or available locally via: info '(coreutils) uname invocation' GNU coreutils 9.3 April 2023 UNAME(1)
|
uname - print system information
|
uname [OPTION]...
| null | null |
scalar
|
Scalar is a repository management tool that optimizes Git for use in large repositories. Scalar improves performance by configuring advanced Git settings, maintaining repositories in the background, and helping to reduce data sent across the network. An important Scalar concept is the enlistment: this is the top-level directory of the project. It usually contains the subdirectory src/ which is a Git worktree. This encourages the separation between tracked files (inside src/) and untracked files, such as build artifacts (outside src/). When registering an existing Git worktree with Scalar whose name is not src, the enlistment will be identical to the worktree. The scalar command implements various subcommands, and different options depending on the subcommand. With the exception of clone, list and reconfigure --all, all subcommands expect to be run in an enlistment. The following options can be specified before the subcommand: -C <directory> Before running the subcommand, change the working directory. This option imitates the same option of git(1). -c <key>=<value> For the duration of running the specified subcommand, configure this setting. This option imitates the same option of git(1). COMMANDS Clone clone [<options>] <url> [<enlistment>] Clones the specified repository, similar to git-clone(1). By default, only commit and tree objects are cloned. Once finished, the worktree is located at <enlistment>/src. The sparse-checkout feature is enabled (except when run with --full-clone) and the only files present are those in the top-level directory. Use git sparse-checkout set to expand the set of directories you want to see, or git sparse-checkout disable to expand to all files (see git-sparse-checkout(1) for more details). You can explore the subdirectories outside your sparse-checkout by using git ls-tree HEAD[:<directory>]. -b <name>, --branch <name> Instead of checking out the branch pointed to by the cloned repository’s HEAD, check out the <name> branch instead. --[no-]single-branch Clone only the history leading to the tip of a single branch, either specified by the --branch option or the primary branch remote’s HEAD points at. Further fetches into the resulting repository will only update the remote-tracking branch for the branch this option was used for the initial cloning. If the HEAD at the remote did not point at any branch when --single-branch clone was made, no remote-tracking branch is created. --[no-]full-clone A sparse-checkout is initialized by default. This behavior can be turned off via --full-clone. List list List enlistments that are currently registered by Scalar. This subcommand does not need to be run inside an enlistment. Register register [<enlistment>] Adds the enlistment’s repository to the list of registered repositories and starts background maintenance. If <enlistment> is not provided, then the enlistment associated with the current working directory is registered. Note: when this subcommand is called in a worktree that is called src/, its parent directory is considered to be the Scalar enlistment. If the worktree is not called src/, it itself will be considered to be the Scalar enlistment. Unregister unregister [<enlistment>] Remove the specified repository from the list of repositories registered with Scalar and stop the scheduled background maintenance. Run scalar run ( all | config | commit-graph | fetch | loose-objects | pack-files ) [<enlistment>] Run the given maintenance task (or all tasks, if all was specified). Except for all and config, this subcommand simply hands off to git-maintenance(1) (mapping fetch to prefetch and pack-files to incremental-repack). These tasks are run automatically as part of the scheduled maintenance, as soon as the repository is registered with Scalar. It should therefore not be necessary to run this subcommand manually. The config task is specific to Scalar and configures all those opinionated default settings that make Git work more efficiently with large repositories. As this task is run as part of scalar clone automatically, explicit invocations of this task are rarely needed. Reconfigure After a Scalar upgrade, or when the configuration of a Scalar enlistment was somehow corrupted or changed by mistake, this subcommand allows to reconfigure the enlistment. With the --all option, all enlistments currently registered with Scalar will be reconfigured. Use this option after each Scalar upgrade. Diagnose diagnose [<enlistment>] When reporting issues with Scalar, it is often helpful to provide the information gathered by this command, including logs and certain statistics describing the data shape of the current enlistment. The output of this command is a .zip file that is written into a directory adjacent to the worktree in the src directory. Delete delete <enlistment> This subcommand lets you delete an existing Scalar enlistment from your local file system, unregistering the repository. SEE ALSO git-clone(1), git-maintenance(1). GIT Part of the git(1) suite Git 2.41.0 2023-06-01 SCALAR(1)
|
scalar - A tool for managing large Git repositories
|
scalar clone [--single-branch] [--branch <main-branch>] [--full-clone] <url> [<enlistment>] scalar list scalar register [<enlistment>] scalar unregister [<enlistment>] scalar run ( all | config | commit-graph | fetch | loose-objects | pack-files ) [<enlistment>] scalar reconfigure [ --all | <enlistment> ] scalar diagnose [<enlistment>] scalar delete <enlistment>
| null | null |
load_roots
| null | null | null | null | null |
python3.12
|
Python is an interpreted, interactive, object-oriented programming language that combines remarkable power with very clear syntax. For an introduction to programming in Python, see the Python Tutorial. The Python Library Reference documents built-in and standard types, constants, functions and modules. Finally, the Python Reference Manual describes the syntax and semantics of the core language in (perhaps too) much detail. (These documents may be located via the INTERNET RESOURCES below; they may be installed on your system as well.) Python's basic power can be extended with your own modules written in C or C++. On most systems such modules may be dynamically loaded. Python is also adaptable as an extension language for existing applications. See the internal documentation for hints. Documentation for installed Python modules and packages can be viewed by running the pydoc program. COMMAND LINE OPTIONS -B Don't write .pyc files on import. See also PYTHONDONTWRITEBYTECODE. -b Issue warnings about str(bytes_instance), str(bytearray_instance) and comparing bytes/bytearray with str. (-bb: issue errors) -c command Specify the command to execute (see next section). This terminates the option list (following options are passed as arguments to the command). --check-hash-based-pycs mode Configure how Python evaluates the up-to-dateness of hash-based .pyc files. -d Turn on parser debugging output (for expert only, depending on compilation options). -E Ignore environment variables like PYTHONPATH and PYTHONHOME that modify the behavior of the interpreter. -h , -? , --help Prints the usage for the interpreter executable and exits. --help-env Prints help about Python-specific environment variables and exits. --help-xoptions Prints help about implementation-specific -X options and exits. --help-all Prints complete usage information and exits. -i When a script is passed as first argument or the -c option is used, enter interactive mode after executing the script or the command. It does not read the $PYTHONSTARTUP file. This can be useful to inspect global variables or a stack trace when a script raises an exception. -I Run Python in isolated mode. This also implies -E, -P and -s. In isolated mode sys.path contains neither the script's directory nor the user's site-packages directory. All PYTHON* environment variables are ignored, too. Further restrictions may be imposed to prevent the user from injecting malicious code. -m module-name Searches sys.path for the named module and runs the corresponding .py file as a script. This terminates the option list (following options are passed as arguments to the module). -O Remove assert statements and any code conditional on the value of __debug__; augment the filename for compiled (bytecode) files by adding .opt-1 before the .pyc extension. -OO Do -O and also discard docstrings; change the filename for compiled (bytecode) files by adding .opt-2 before the .pyc extension. -P Don't automatically prepend a potentially unsafe path to sys.path such as the current directory, the script's directory or an empty string. See also the PYTHONSAFEPATH environment variable. -q Do not print the version and copyright messages. These messages are also suppressed in non-interactive mode. -s Don't add user site directory to sys.path. -S Disable the import of the module site and the site-dependent manipulations of sys.path that it entails. Also disable these manipulations if site is explicitly imported later. -u Force the stdout and stderr streams to be unbuffered. This option has no effect on the stdin stream. -v Print a message each time a module is initialized, showing the place (filename or built-in module) from which it is loaded. When given twice, print a message for each file that is checked for when searching for a module. Also provides information on module cleanup at exit. -V , --version Prints the Python version number of the executable and exits. When given twice, print more information about the build. -W argument Warning control. Python's warning machinery by default prints warning messages to sys.stderr. The simplest settings apply a particular action unconditionally to all warnings emitted by a process (even those that are otherwise ignored by default): -Wdefault # Warn once per call location -Werror # Convert to exceptions -Walways # Warn every time -Wmodule # Warn once per calling module -Wonce # Warn once per Python process -Wignore # Never warn The action names can be abbreviated as desired and the interpreter will resolve them to the appropriate action name. For example, -Wi is the same as -Wignore . The full form of argument is: action:message:category:module:lineno Empty fields match all values; trailing empty fields may be omitted. For example -W ignore::DeprecationWarning ignores all DeprecationWarning warnings. The action field is as explained above but only applies to warnings that match the remaining fields. The message field must match the whole printed warning message; this match is case-insensitive. The category field matches the warning category (ex: "DeprecationWarning"). This must be a class name; the match test whether the actual warning category of the message is a subclass of the specified warning category. The module field matches the (fully-qualified) module name; this match is case-sensitive. The lineno field matches the line number, where zero matches all line numbers and is thus equivalent to an omitted line number. Multiple -W options can be given; when a warning matches more than one option, the action for the last matching option is performed. Invalid -W options are ignored (though, a warning message is printed about invalid options when the first warning is issued). Warnings can also be controlled using the PYTHONWARNINGS environment variable and from within a Python program using the warnings module. For example, the warnings.filterwarnings() function can be used to use a regular expression on the warning message. -X option Set implementation-specific option. The following options are available: -X faulthandler: enable faulthandler -X showrefcount: output the total reference count and number of used memory blocks when the program finishes or after each statement in the interactive interpreter. This only works on debug builds -X tracemalloc: start tracing Python memory allocations using the tracemalloc module. By default, only the most recent frame is stored in a traceback of a trace. Use -X tracemalloc=NFRAME to start tracing with a traceback limit of NFRAME frames -X importtime: show how long each import takes. It shows module name, cumulative time (including nested imports) and self time (excluding nested imports). Note that its output may be broken in multi-threaded application. Typical usage is python3 -X importtime -c 'import asyncio' -X dev: enable CPython's "development mode", introducing additional runtime checks which are too expensive to be enabled by default. It will not be more verbose than the default if the code is correct: new warnings are only emitted when an issue is detected. Effect of the developer mode: * Add default warning filter, as -W default * Install debug hooks on memory allocators: see the PyMem_SetupDebugHooks() C function * Enable the faulthandler module to dump the Python traceback on a crash * Enable asyncio debug mode * Set the dev_mode attribute of sys.flags to True * io.IOBase destructor logs close() exceptions -X utf8: enable UTF-8 mode for operating system interfaces, overriding the default locale-aware mode. -X utf8=0 explicitly disables UTF-8 mode (even when it would otherwise activate automatically). See PYTHONUTF8 for more details -X pycache_prefix=PATH: enable writing .pyc files to a parallel tree rooted at the given directory instead of to the code tree. -X warn_default_encoding: enable opt-in EncodingWarning for 'encoding=None' -X no_debug_ranges: disable the inclusion of the tables mapping extra location information (end line, start column offset and end column offset) to every instruction in code objects. This is useful when smaller code objects and pyc files are desired as well as suppressing the extra visual location indicators when the interpreter displays tracebacks. -X frozen_modules=[on|off]: whether or not frozen modules should be used. The default is "on" (or "off" if you are running a local build). -X int_max_str_digits=number: limit the size of int<->str conversions. This helps avoid denial of service attacks when parsing untrusted data. The default is sys.int_info.default_max_str_digits. 0 disables. -x Skip the first line of the source. This is intended for a DOS specific hack only. Warning: the line numbers in error messages will be off by one! INTERPRETER INTERFACE The interpreter interface resembles that of the UNIX shell: when called with standard input connected to a tty device, it prompts for commands and executes them until an EOF is read; when called with a file name argument or with a file as standard input, it reads and executes a script from that file; when called with -c command, it executes the Python statement(s) given as command. Here command may contain multiple statements separated by newlines. Leading whitespace is significant in Python statements! In non-interactive mode, the entire input is parsed before it is executed. If available, the script name and additional arguments thereafter are passed to the script in the Python variable sys.argv, which is a list of strings (you must first import sys to be able to access it). If no script name is given, sys.argv[0] is an empty string; if -c is used, sys.argv[0] contains the string '-c'. Note that options interpreted by the Python interpreter itself are not placed in sys.argv. In interactive mode, the primary prompt is `>>>'; the second prompt (which appears when a command is not complete) is `...'. The prompts can be changed by assignment to sys.ps1 or sys.ps2. The interpreter quits when it reads an EOF at a prompt. When an unhandled exception occurs, a stack trace is printed and control returns to the primary prompt; in non-interactive mode, the interpreter exits after printing the stack trace. The interrupt signal raises the KeyboardInterrupt exception; other UNIX signals are not caught (except that SIGPIPE is sometimes ignored, in favor of the IOError exception). Error messages are written to stderr. FILES AND DIRECTORIES These are subject to difference depending on local installation conventions; ${prefix} and ${exec_prefix} are installation-dependent and should be interpreted as for GNU software; they may be the same. The default for both is /usr/local. ${exec_prefix}/bin/python Recommended location of the interpreter. ${prefix}/lib/python<version> ${exec_prefix}/lib/python<version> Recommended locations of the directories containing the standard modules. ${prefix}/include/python<version> ${exec_prefix}/include/python<version> Recommended locations of the directories containing the include files needed for developing Python extensions and embedding the interpreter. ENVIRONMENT VARIABLES PYTHONSAFEPATH If this is set to a non-empty string, don't automatically prepend a potentially unsafe path to sys.path such as the current directory, the script's directory or an empty string. See also the -P option. PYTHONHOME Change the location of the standard Python libraries. By default, the libraries are searched in ${prefix}/lib/python<version> and ${exec_prefix}/lib/python<version>, where ${prefix} and ${exec_prefix} are installation-dependent directories, both defaulting to /usr/local. When $PYTHONHOME is set to a single directory, its value replaces both ${prefix} and ${exec_prefix}. To specify different values for these, set $PYTHONHOME to ${prefix}:${exec_prefix}. PYTHONPATH Augments the default search path for module files. The format is the same as the shell's $PATH: one or more directory pathnames separated by colons. Non-existent directories are silently ignored. The default search path is installation dependent, but generally begins with ${prefix}/lib/python<version> (see PYTHONHOME above). The default search path is always appended to $PYTHONPATH. If a script argument is given, the directory containing the script is inserted in the path in front of $PYTHONPATH. The search path can be manipulated from within a Python program as the variable sys.path. PYTHONPLATLIBDIR Override sys.platlibdir. PYTHONSTARTUP If this is the name of a readable file, the Python commands in that file are executed before the first prompt is displayed in interactive mode. The file is executed in the same name space where interactive commands are executed so that objects defined or imported in it can be used without qualification in the interactive session. You can also change the prompts sys.ps1 and sys.ps2 in this file. PYTHONOPTIMIZE If this is set to a non-empty string it is equivalent to specifying the -O option. If set to an integer, it is equivalent to specifying -O multiple times. PYTHONDEBUG If this is set to a non-empty string it is equivalent to specifying the -d option. If set to an integer, it is equivalent to specifying -d multiple times. PYTHONDONTWRITEBYTECODE If this is set to a non-empty string it is equivalent to specifying the -B option (don't try to write .pyc files). PYTHONINSPECT If this is set to a non-empty string it is equivalent to specifying the -i option. PYTHONIOENCODING If this is set before running the interpreter, it overrides the encoding used for stdin/stdout/stderr, in the syntax encodingname:errorhandler The errorhandler part is optional and has the same meaning as in str.encode. For stderr, the errorhandler part is ignored; the handler will always be ´backslashreplace´. PYTHONNOUSERSITE If this is set to a non-empty string it is equivalent to specifying the -s option (Don't add the user site directory to sys.path). PYTHONUNBUFFERED If this is set to a non-empty string it is equivalent to specifying the -u option. PYTHONVERBOSE If this is set to a non-empty string it is equivalent to specifying the -v option. If set to an integer, it is equivalent to specifying -v multiple times. PYTHONWARNINGS If this is set to a comma-separated string it is equivalent to specifying the -W option for each separate value. PYTHONHASHSEED If this variable is set to "random", a random value is used to seed the hashes of str and bytes objects. If PYTHONHASHSEED is set to an integer value, it is used as a fixed seed for generating the hash() of the types covered by the hash randomization. Its purpose is to allow repeatable hashing, such as for selftests for the interpreter itself, or to allow a cluster of python processes to share hash values. The integer must be a decimal number in the range [0,4294967295]. Specifying the value 0 will disable hash randomization. PYTHONINTMAXSTRDIGITS Limit the maximum digit characters in an int value when converting from a string and when converting an int back to a str. A value of 0 disables the limit. Conversions to or from bases 2, 4, 8, 16, and 32 are never limited. PYTHONMALLOC Set the Python memory allocators and/or install debug hooks. The available memory allocators are malloc and pymalloc. The available debug hooks are debug, malloc_debug, and pymalloc_debug. When Python is compiled in debug mode, the default is pymalloc_debug and the debug hooks are automatically used. Otherwise, the default is pymalloc. PYTHONMALLOCSTATS If set to a non-empty string, Python will print statistics of the pymalloc memory allocator every time a new pymalloc object arena is created, and on shutdown. This variable is ignored if the $PYTHONMALLOC environment variable is used to force the malloc(3) allocator of the C library, or if Python is configured without pymalloc support. PYTHONASYNCIODEBUG If this environment variable is set to a non-empty string, enable the debug mode of the asyncio module. PYTHONTRACEMALLOC If this environment variable is set to a non-empty string, start tracing Python memory allocations using the tracemalloc module. The value of the variable is the maximum number of frames stored in a traceback of a trace. For example, PYTHONTRACEMALLOC=1 stores only the most recent frame. PYTHONFAULTHANDLER If this environment variable is set to a non-empty string, faulthandler.enable() is called at startup: install a handler for SIGSEGV, SIGFPE, SIGABRT, SIGBUS and SIGILL signals to dump the Python traceback. This is equivalent to the -X faulthandler option. PYTHONEXECUTABLE If this environment variable is set, sys.argv[0] will be set to its value instead of the value got through the C runtime. Only works on Mac OS X. PYTHONUSERBASE Defines the user base directory, which is used to compute the path of the user site-packages directory and installation paths for python -m pip install --user. PYTHONPROFILEIMPORTTIME If this environment variable is set to a non-empty string, Python will show how long each import takes. This is exactly equivalent to setting -X importtime on the command line. PYTHONBREAKPOINT If this environment variable is set to 0, it disables the default debugger. It can be set to the callable of your debugger of choice. Debug-mode variables Setting these variables only has an effect in a debug build of Python, that is, if Python was configured with the --with-pydebug build option. PYTHONDUMPREFS If this environment variable is set, Python will dump objects and reference counts still alive after shutting down the interpreter. AUTHOR The Python Software Foundation: https://www.python.org/psf/ INTERNET RESOURCES Main website: https://www.python.org/ Documentation: https://docs.python.org/ Developer resources: https://devguide.python.org/ Downloads: https://www.python.org/downloads/ Module repository: https://pypi.org/ Newsgroups: comp.lang.python, comp.lang.python.announce LICENSING Python is distributed under an Open Source license. See the file "LICENSE" in the Python source distribution for information on terms & conditions for accessing and otherwise using Python and for a DISCLAIMER OF ALL WARRANTIES. PYTHON(1)
|
python - an interpreted, interactive, object-oriented programming language
|
python [ -B ] [ -b ] [ -d ] [ -E ] [ -h ] [ -i ] [ -I ] [ -m module-name ] [ -q ] [ -O ] [ -OO ] [ -P ] [ -s ] [ -S ] [ -u ] [ -v ] [ -V ] [ -W argument ] [ -x ] [ -X option ] [ -? ] [ --check-hash-based-pycs default | always | never ] [ --help ] [ --help-env ] [ --help-xoptions ] [ --help-all ] [ -c command | script | - ] [ arguments ]
| null | null |
gtee
|
Copy standard input to each FILE, and also to standard output. -a, --append append to the given FILEs, do not overwrite -i, --ignore-interrupts ignore interrupt signals -p operate in a more appropriate MODE with pipes. --output-error[=MODE] set behavior on write error. See MODE below --help display this help and exit --version output version information and exit MODE determines behavior with write errors on the outputs: warn diagnose errors writing to any output warn-nopipe diagnose errors writing to any output not a pipe exit exit on error writing to any output exit-nopipe exit on error writing to any output not a pipe The default MODE for the -p option is 'warn-nopipe'. With "nopipe" MODEs, exit immediately if all outputs become broken pipes. The default operation when --output-error is not specified, is to exit immediately on error writing to a pipe, and diagnose errors writing to non pipe outputs. AUTHOR Written by Mike Parker, Richard M. Stallman, and 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 Full documentation <https://www.gnu.org/software/coreutils/tee> or available locally via: info '(coreutils) tee invocation' GNU coreutils 9.3 April 2023 TEE(1)
|
tee - read from standard input and write to standard output and files
|
tee [OPTION]... [FILE]...
| null | null |
lzfgrep
|
xzgrep invokes grep(1) on uncompressed contents of files. The formats of the files are determined from the filename suffixes. Any file with a suffix supported by xz(1), gzip(1), bzip2(1), lzop(1), zstd(1), or lz4(1) will be decompressed; all other files are assumed to be uncompressed. If no files are specified or file is - then standard input is read. When reading from standard input, only files supported by xz(1) are decompressed. Other files are assumed to be in uncompressed form already. Most options of grep(1) are supported. However, the following options are not supported: -r, --recursive -R, --dereference-recursive -d, --directories=action -Z, --null -z, --null-data --include=glob --exclude=glob --exclude-from=file --exclude-dir=glob xzegrep is an alias for xzgrep -E. xzfgrep is an alias for xzgrep -F. The commands lzgrep, lzegrep, and lzfgrep are provided for backward compatibility with LZMA Utils. EXIT STATUS 0 At least one match was found from at least one of the input files. No errors occurred. 1 No matches were found from any of the input files. No errors occurred. >1 One or more errors occurred. It is unknown if matches were found. ENVIRONMENT GREP If GREP is set to a non-empty value, it is used instead of grep, grep -E, or grep -F. SEE ALSO grep(1), xz(1), gzip(1), bzip2(1), lzop(1), zstd(1), lz4(1), zgrep(1) Tukaani 2024-02-13 XZGREP(1)
|
xzgrep - search possibly-compressed files for patterns
|
xzgrep [option...] [pattern_list] [file...] xzegrep ... xzfgrep ... lzgrep ... lzegrep ... lzfgrep ...
| null | null |
black
| null | null | null | null | null |
exrheader
| null | null | null | null | null |
gstty
|
Print or change terminal characteristics. Mandatory arguments to long options are mandatory for short options too. -a, --all print all current settings in human-readable form -g, --save print all current settings in a stty-readable form -F, --file=DEVICE open and use the specified DEVICE instead of stdin --help display this help and exit --version output version information and exit Optional - before SETTING indicates negation. An * marks non-POSIX settings. The underlying system defines which settings are available. Special characters: * discard CHAR CHAR will toggle discarding of output * dsusp CHAR CHAR will send a terminal stop signal once input flushed eof CHAR CHAR will send an end of file (terminate the input) eol CHAR CHAR will end the line * eol2 CHAR alternate CHAR for ending the line erase CHAR CHAR will erase the last character typed intr CHAR CHAR will send an interrupt signal kill CHAR CHAR will erase the current line * lnext CHAR CHAR will enter the next character quoted * status CHAR CHAR will send an info signal quit CHAR CHAR will send a quit signal * rprnt CHAR CHAR will redraw the current line start CHAR CHAR will restart the output after stopping it stop CHAR CHAR will stop the output susp CHAR CHAR will send a terminal stop signal * swtch CHAR CHAR will switch to a different shell layer * werase CHAR CHAR will erase the last word typed Special settings: N set the input and output speeds to N bauds * cols N tell the kernel that the terminal has N columns * columns N same as cols N * [-]drain wait for transmission before applying settings (on by default) ispeed N set the input speed to N min N with -icanon, set N characters minimum for a completed read ospeed N set the output speed to N * rows N tell the kernel that the terminal has N rows * size print the number of rows and columns according to the kernel speed print the terminal speed time N with -icanon, set read timeout of N tenths of a second Control settings: [-]clocal disable modem control signals [-]cread allow input to be received * [-]crtscts enable RTS/CTS handshaking csN set character size to N bits, N in [5..8] [-]cstopb use two stop bits per character (one with '-') [-]hup send a hangup signal when the last process closes the tty [-]hupcl same as [-]hup [-]parenb generate parity bit in output and expect parity bit in input [-]parodd set odd parity (or even parity with '-') Input settings: [-]brkint breaks cause an interrupt signal [-]icrnl translate carriage return to newline [-]ignbrk ignore break characters [-]igncr ignore carriage return [-]ignpar ignore characters with parity errors * [-]imaxbel beep and do not flush a full input buffer on a character [-]inlcr translate newline to carriage return [-]inpck enable input parity checking [-]istrip clear high (8th) bit of input characters * [-]iutf8 assume input characters are UTF-8 encoded * [-]ixany let any character restart output, not only start character [-]ixoff enable sending of start/stop characters [-]ixon enable XON/XOFF flow control [-]parmrk mark parity errors (with a 255-0-character sequence) [-]tandem same as [-]ixoff Output settings: * bsN backspace delay style, N in [0..1] * crN carriage return delay style, N in [0..3] * ffN form feed delay style, N in [0..1] * nlN newline delay style, N in [0..1] * [-]ocrnl translate carriage return to newline * [-]ofdel use delete characters for fill instead of NUL characters * [-]ofill use fill (padding) characters instead of timing for delays * [-]onlcr translate newline to carriage return-newline * [-]onlret newline performs a carriage return * [-]onocr do not print carriage returns in the first column [-]opost postprocess output * tabN horizontal tab delay style, N in [0..3] * tabs same as tab0 * -tabs same as tab3 * vtN vertical tab delay style, N in [0..1] Local settings: [-]crterase echo erase characters as backspace-space-backspace * crtkill kill all line by obeying the echoprt and echoe settings * -crtkill kill all line by obeying the echoctl and echok settings * [-]ctlecho echo control characters in hat notation ('^c') [-]echo echo input characters * [-]echoctl same as [-]ctlecho [-]echoe same as [-]crterase [-]echok echo a newline after a kill character * [-]echoke same as [-]crtkill [-]echonl echo newline even if not echoing other characters * [-]echoprt echo erased characters backward, between '\' and '/' * [-]extproc enable "LINEMODE"; useful with high latency links * [-]flusho discard output [-]icanon enable special characters: erase, kill, werase, rprnt [-]iexten enable non-POSIX special characters [-]isig enable interrupt, quit, and suspend special characters [-]noflsh disable flushing after interrupt and quit special characters * [-]prterase same as [-]echoprt * [-]tostop stop background jobs that try to write to the terminal Combination settings: cbreak same as -icanon -cbreak same as icanon cooked same as brkint ignpar istrip icrnl ixon opost isig icanon, eof and eol characters to their default values -cooked same as raw crt same as echoe echoctl echoke dec same as echoe echoctl echoke -ixany intr ^c erase 0177 kill ^u * [-]decctlq same as [-]ixany ek erase and kill characters to their default values evenp same as parenb -parodd cs7 -evenp same as -parenb cs8 litout same as -parenb -istrip -opost cs8 -litout same as parenb istrip opost cs7 nl same as -icrnl -onlcr -nl same as icrnl -inlcr -igncr onlcr -ocrnl -onlret oddp same as parenb parodd cs7 -oddp same as -parenb cs8 [-]parity same as [-]evenp pass8 same as -parenb -istrip cs8 -pass8 same as parenb istrip cs7 raw same as -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff -icanon -opost -isig -ixany -imaxbel min 1 time 0 -raw same as cooked sane same as cread -ignbrk brkint -inlcr -igncr icrnl icanon iexten echo echoe echok -echonl -noflsh -ixoff -iutf8 -ixany imaxbel -ocrnl opost -ofill onlcr -onocr -onlret nl0 cr0 tab0 bs0 vt0 ff0 isig -tostop -ofdel -echoprt echoctl echoke -extproc -flusho, all special characters to their default values Handle the tty line connected to standard input. Without arguments, prints baud rate, line discipline, and deviations from stty sane. In settings, CHAR is taken literally, or coded as in ^c, 0x37, 0177 or 127; special values ^- or undef used to disable special characters. 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 Full documentation <https://www.gnu.org/software/coreutils/stty> or available locally via: info '(coreutils) stty invocation' GNU coreutils 9.3 April 2023 STTY(1)
|
stty - change and print terminal line settings
|
stty [-F DEVICE | --file=DEVICE] [SETTING]... stty [-F DEVICE | --file=DEVICE] [-a|--all] stty [-F DEVICE | --file=DEVICE] [-g|--save]
| null | null |
pre-commit
| null | null | null | null | null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.