neulab/tldr huggingface dataset:
Do not expect a personal answer to a bug report.  The purpose of reporting bugs is to get them fixed for everyone in the next release, if possible.  For personal assistance, consult the service directory at <https://www.fsf.org/resources/service/> for a list of people who offer it.
Please do not send anything but bug reports to this mailing list.  For other Emacs lists, see <https://savannah.gnu.org/mail/?group=emacs>.
Emacs is free; anyone may redistribute copies of Emacs to anyone under the terms stated in the GNU General Public License, a copy of which accompanies each copy of Emacs and which also appears in the reference manual.
Copies of Emacs may sometimes be received packaged with distributions of Unix systems, but it is never included in the scope of any license covering those systems.  Such inclusion violates the terms on which distribution is permitted.  In fact, the primary purpose of the GNU General Public License is to prohibit anyone from attaching any other restrictions to redistribution of Emacs.
Richard Stallman encourages you to improve and extend Emacs, and urges that you contribute your extensions to the GNU library.  Eventually GNU (Gnu's Not Unix) will be a complete replacement for Unix.  Everyone will be free to use, copy, study and change the GNU system.
emacsclient(1), etags(1), X(7), xlsfonts(1), xterm(1), xrdb(1)
Emacs was written by Richard Stallman and the Free Software Foundation. For detailed credits and acknowledgments, see the GNU Emacs manual.
Copyright 1995, 1999-2021 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of this document provided the copyright notice and this permission notice are preserved on all copies.
Permission is granted to copy and distribute modified versions of this document under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one.
Permission is granted to copy and distribute translations of this document into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation.
WHEREIS(1)                        User Commands                       WHEREIS(1)
whereis - locate the binary, source, and manual page files for a command
whereis [options] [-BMS directory... -f] name...
whereis locates the binary, source and manual files for the specified command names. The supplied names are first stripped of leading pathname components. Prefixes of s. resulting from use of source code control are also dealt with. whereis then attempts to locate the desired program in the standard Linux places, and in the places specified by $PATH and $MANPATH.
The search restrictions (options -b, -m and -s) are cumulative and apply to the subsequent name patterns on the command line. Any new search restriction resets the search mask. For example,
whereis -bm ls tr -m gcc
searches for "ls" and "tr" binaries and man pages, and for "gcc" man pages only.
The options -B, -M and -S reset search paths for the subsequent name patterns. For example,
whereis -m ls -M /usr/share/man/man1 -f cal
searches for "ls" man pages in all default paths, but for "cal" in the /usr/share/man/man1 directory only.
-b Search for binaries.
-m Search for manuals.
-s Search for sources.
-u Only show the command names that have unusual entries. A command is said to be unusual if it does not have just one entry of each explicitly requested type. Thus 'whereis -m -u *' asks for those files in the current directory which have no documentation file, or more than one.
-B list Limit the places where whereis searches for binaries, by a whitespace-separated list of directories.
-M list Limit the places where whereis searches for manuals and documentation in Info format, by a whitespace-separated list of directories.
-S list Limit the places where whereis searches for sources, by a whitespace-separated list of directories.
-f Terminates the directory list and signals the start of filenames. It must be used when any of the -B, -M, or -S options is used.
-l Output the list of effective lookup paths that whereis is using. When none of -B, -M, or -S is specified, the option will output the hard-coded paths that the command was able to find on the system.
By default whereis tries to find files from hard-coded paths, which are defined with glob patterns. The command attempts to use the contents of $PATH and $MANPATH environment variables as default search path. The easiest way to know what paths are in use is to add the -l listing option. Effects of the -B, -M, and -S are displayed with -l.
WHEREIS_DEBUG=all enables debug output.
To find all files in /usr/bin which are not documented in /usr/man/man1 or have no source in /usr/src:
cd /usr/bin whereis -u -ms -M /usr/man/man1 -S /usr/src -f *
The whereis command is part of the util-linux package which can be downloaded from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils/util-linux/>.
LILYPOND(1)                       User Commands                      LILYPOND(1)
LilyPond - manual page for LilyPond 2.22.1
lilypond [OPTION]... FILE...
Typeset music and/or produce MIDI from FILE.
LilyPond produces beautiful music notation.  For more information, see https://lilypond.org
-f, --formats=FORMATs dump FORMAT,...  Also as separate options:
--pdf  generate PDF files (default)
--svg  generate SVG files
--png  generate PNG files
--ps   generate PostScript files
-E, --eps generate Encapsulated PostScript files
-O, --pspdfopt=KEY set ps/pdf optimization to KEY, which is either 'size' (default), 'TeX', or 'TeX-GS'
-d, --define-default=SYM[=VAL] set Scheme option SYM to VAL (default: #t); use -dhelp for help
-e, --evaluate=EXPR evaluate scheme code
-h, --help show this help and exit
-H, --header=FIELD dump \header field FIELD to file named BASENAME.FIELD
-I, --include=DIR append DIR to search path
-i, --init=FILE use FILE as init file
-j, --jail=USER,GROUP,JAIL,DIR chroot to JAIL, become USER:GROUP and cd into DIR
-l, --loglevel=LOGLEVEL print log messages according to LOGLEVEL, which is either NONE, ERROR, WARNING, BASIC, PROGRESS, INFO (default), or DEBUG
-o, --output=FILE write output to FILE (suffix will be added) or to FOLDER, in which case the file name will be taken from the input file.
--relocate (ignored)
-s, --silent no progress, only error messages (equivalent to --loglevel=ERROR)
-v, --version show version number and exit
-V, --verbose be verbose (equivalent to --loglevel=DEBUG)
-w, --warranty show warranty and copyright
You found a bug? Please read https://lilypond.org/bug-reports.html
Copyright Â© 1996--2021 by
Han-Wen Nienhuys <hanwen@xs4all.nl> Jan Nieuwenhuizen <janneke@gnu.org> and others.
This program is free software.  It is covered by the GNU General Public License and you are welcome to change it and/or distribute copies of it under certain conditions.  Invoke as `lilypond --warranty' for more information.
The full documentation for LilyPond is maintained as a Texinfo manual. If the info and LilyPond programs are properly installed at your site, the command
info LilyPond
RTMPDUMP(1)                  General Commands Manual                 RTMPDUMP(1)
rtmpdump - RTMP streaming media client
rtmpdump -r url [-n hostname] [-c port] [-l protocol] [-S host:port] [-a app] [-t tcUrl] [-p pageUrl] [-s swfUrl] [-f flashVer] [-u auth] [-C conndata] [-y playpath] [-Y] [-v] [-d subscription] [-e] [-k skip] [-A start] [-B stop] [-b buffer] [-m timeout] [-T key] [-j JSON] [-w swfHash] [-x swfSize] [-W swfUrl] [-X swfAge] [-o output] [-#] [-q] [-V] [-z] rtmpdump -h
rtmpdump is a tool for dumping media content streamed over RTMP.
rtmpdump makes a connection to the specified RTMP server and plays the media specified by the given url.  The url should be of the form rtmp[t][e]://hostname[:port][/app[/playpath]]
Plain rtmp, as well as tunneled and encrypted sessions are supported.
Network Parameters These options define how to connect to the media server.
--rtmp         -r url URL of the server and media content.
--host         -n hostname Overrides the hostname in the RTMP URL.
--port         -c port Overrides the port number in the RTMP URL.
--protocol     -l number Overrides the protocol in the RTMP URL. 0 = rtmp 1 = rtmpt 2 = rtmpe 3 = rtmpte 4 = rtmps 5 = rtmpts
--socks        -S host:port Use the specified SOCKS4 proxy.
Connection Parameters These options define the content of the RTMP Connect request packet.  If correct values are not provided, the media server will reject the connection attempt.
--app          -a app Name of application to connect to on the RTMP server. Overrides the app in the RTMP URL. Sometimes the rtmpdump URL parser cannot determine the app name automatically, so it must be given explicitly using this option.
--tcUrl        -t url URL of the target stream. Defaults to rtmp[e]://host[:port]/app/playpath.
--pageUrl      -p url URL of the web page in which the media was embedded. By default no value will be sent.
--swfUrl       -s url URL of the SWF player for the media. By default no value will be sent.
--flashVer     -f version Version of the Flash plugin used to run the SWF player. The default is "LNX 10,0,32,18".
--auth         -u string An authentication string to be appended to the Connect message. Using this option will append a Boolean TRUE and then the specified string.  This option is only used by some particular servers and is deprecated. The more general --conn option should be used instead.
--conn         -C type:data Append arbitrary AMF data to the Connect message. The type must be B for Boolean, N for number, S for string, O for object, or Z for null. For Booleans the data must be either 0 or 1 for FALSE or TRUE, respectively. Likewise for Objects the data must be 0 or 1 to end or begin an object, respectively. Data items in subobjects may be named, by prefixing the type with 'N' and specifying the name before the value, e.g.  NB:myFlag:1. This option may be used multiple times to construct arbitrary AMF sequences. E.g. -C B:1 -C S:authMe -C O:1 -C NN:code:1.23 -C NS:flag:ok -C O:0
Session Parameters These options take effect after the Connect request has succeeded.
--playpath     -y path Overrides the playpath parsed from the RTMP URL. Sometimes the rtmpdump URL parser cannot determine the correct playpath automatically, so it must be given explicitly using this option.
--playlist          -Y Issue a set_playlist command before sending the play command. The playlist will just contain the current playpath.
--live         -v Specify that the media is a live stream. No resuming or seeking in live streams is possible.
--subscribe    -d stream Name of live stream to subscribe to. Defaults to playpath.
--realtime     -R Download approximately in realtime, without attempting to speed up via Pause/Unpause commands ("the BUFX hack").  Useful for servers that jump backwards in time at the Unpause command.  Resuming and seeking in realtime streams is still possible.
--resume       -e Resume an incomplete RTMP download.
--skip         -k num Skip num keyframes when looking for the last keyframe from which to resume. This may be useful if a regular attempt to resume fails. The default is 0.
--start        -A num Start at num seconds into the stream. Not valid for live streams.
--stop         -B num Stop at num seconds into the stream.
--buffer       -b num Set buffer time to num milliseconds. The default is 36000000.
--timeout      -m num Timeout the session after num seconds without receiving any data from the server. The default is 120.
Security Parameters These options handle additional authentication requests from the server.
--token        -T key Key for SecureToken response, used if the server requires SecureToken authentication.
--jtv          -j JSON JSON token used by legacy Justin.tv servers. Invokes NetStream.Authenticate.UsherToken
--swfhash      -w hexstring SHA256 hash of the decompressed SWF file. This option may be needed if the server uses SWF Verification, but see the --swfVfy option below. The hash is 32 bytes, and must be given in hexadecimal. The --swfsize option must always be used with this option.
--swfsize      -x num Size of the decompressed SWF file. This option may be needed if the server uses SWF Verification, but see the --swfVfy option below. The --swfhash option must always be used with this option.
--swfVfy       -W url URL of the SWF player for this media. This option replaces all three of the --swfUrl, --swfhash, and --swfsize options. When this option is used, the SWF player is retrieved from the specified URL and the hash and size are computed automatically. Also the information is cached in a .swfinfo file in the user's home directory, so that it doesn't need to be retrieved and recalculated every time rtmpdump is run. The .swfinfo file records the URL, the time it was fetched, the modification timestamp of the SWF file, its size, and its hash. By default, the cached info will be used for 30 days before re-checking.
--swfAge       -X days Specify how many days to use the cached SWF info before re- checking. Use 0 to always check the SWF URL. Note that if the check shows that the SWF file has the same modification timestamp as before, it will not be retrieved again.
Miscellaneous --flv          -o output Specify the output file name. If the name is - or is omitted, the stream is written to stdout.
--hashes       -# Display streaming progress with a hash mark for each 1% of progress, instead of a byte counter.
--quiet        -q Suppress all command output.
--verbose      -V Verbose command output.
--debug        -z Debug level output. Extremely verbose, including hex dumps of all packet data.
--help         -h Print a summary of command options.
0      Successful program execution.
1      Unrecoverable error.
2      Incomplete transfer, resuming may get further.
HOME   The value of $HOME is used as the location for the .swfinfo file.
$HOME/.swfinfo Cache of SWF Verification information
rtmpgw(8)
Andrej Stepanchuk, Howard Chu, The Flvstreamer Team <http://rtmpdump.mplayerhq.hu>
FALLOCATE(1)                      User Commands                     FALLOCATE(1)
fallocate - preallocate or deallocate space to a file
fallocate [-c|-p|-z] [-o offset] -l length [-n] filename
fallocate -d [-o offset] [-l length] filename
fallocate -x [-o offset] -l length filename
fallocate is used to manipulate the allocated disk space for a file, either to deallocate or preallocate it. For filesystems which support the fallocate system call, preallocation is done quickly by allocating blocks and marking them as uninitialized, requiring no IO to the data blocks. This is much faster than creating a file by filling it with zeroes.
The exit status returned by fallocate is 0 on success and 1 on failure.
The length and offset arguments may be followed by the multiplicative suffixes KiB (=1024), MiB (=1024*1024), and so on for GiB, TiB, PiB, EiB, ZiB, and YiB (the "iB" is optional, e.g., "K" has the same meaning as "KiB") or the suffixes KB (=1000), MB (=1000*1000), and so on for GB, TB, PB, EB, ZB, and YB.
The options --collapse-range, --dig-holes, --punch-hole, and --zero-range are mutually exclusive.
-c, --collapse-range Removes a byte range from a file, without leaving a hole. The byte range to be collapsed starts at offset and continues for length bytes. At the completion of the operation, the contents of the file starting at the location offset+length will be appended at the location offset, and the file will be length bytes smaller. The option --keep-size may not be specified for the collapse-range operation.
Available since Linux 3.15 for ext4 (only for extent-based files) and XFS.
A filesystem may place limitations on the granularity of the operation, in order to ensure efficient implementation. Typically, offset and len must be a multiple of the filesystem logical block size, which varies according to the filesystem type and configuration. If a filesystem has such a requirement, the operation will fail with the error EINVAL if this requirement is violated.
-d, --dig-holes Detect and dig holes. This makes the file sparse in-place, without using extra disk space. The minimum size of the hole depends on filesystem I/O block size (usually 4096 bytes). Also, when using this option, --keep-size is implied. If no range is specified by --offset and --length, then the entire file is analyzed for holes.
You can think of this option as doing a "cp --sparse" and then renaming the destination file to the original, without the need for extra disk space.
See --punch-hole for a list of supported filesystems.
-i, --insert-range Insert a hole of length bytes from offset, shifting existing data.
-l, --length length Specifies the length of the range, in bytes.
-n, --keep-size Do not modify the apparent length of the file. This may effectively allocate blocks past EOF, which can be removed with a truncate.
-o, --offset offset Specifies the beginning offset of the range, in bytes.
-p, --punch-hole Deallocates space (i.e., creates a hole) in the byte range starting at offset and continuing for length bytes. Within the specified range, partial filesystem blocks are zeroed, and whole filesystem blocks are removed from the file. After a successful call, subsequent reads from this range will return zeroes. This option may not be specified at the same time as the --zero-range option. Also, when using this option, --keep-size is implied.
Supported for XFS (since Linux 2.6.38), ext4 (since Linux 3.0), Btrfs (since Linux 3.7), tmpfs (since Linux 3.5) and gfs2 (since Linux 4.16).
-v, --verbose Enable verbose mode.
-x, --posix Enable POSIX operation mode. In that mode allocation operation always completes, but it may take longer time when fast allocation is not supported by the underlying filesystem.
-z, --zero-range Zeroes space in the byte range starting at offset and continuing for length bytes. Within the specified range, blocks are preallocated for the regions that span the holes in the file. After a successful call, subsequent reads from this range will return zeroes.
Zeroing is done within the filesystem preferably by converting the range into unwritten extents. This approach means that the specified range will not be physically zeroed out on the device (except for partial blocks at the either end of the range), and I/O is (otherwise) required only to update metadata.
Option --keep-size can be specified to prevent file length modification.
Available since Linux 3.14 for ext4 (only for extent-based files) and XFS.
Eric Sandeen <sandeen@redhat.com>, Karel Zak <kzak@redhat.com>
truncate(1), fallocate(2), posix_fallocate(3)
The fallocate command is part of the util-linux package which can be downloaded from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils/util-linux/>.
WEB(1)                       General Commands Manual                      WEB(1)
web, wmail - handle web page, mail message for plumber
web url ... wmail address
Web opens each of the named urls in a new web browser window.  Any of the urls may be relative paths to files in the file system; they will be translated into file:// URLs before being passed to the web browser.
Web uses the web browser's -remote option command-line option, which requires an instance of the web browser to be already running.  The choice of browser is determined by the $BROWSER environment variable, which should be the name of the executable for your choice of web browser.  The default is firefox.  Since the various browsers all use different syntaxes in their -remote options, the executable name is inspected to determine the type of browser.  The supported browsers are Opera, Mozilla Firefox, Mozilla Firebird, and Mozilla.  When possible, web opens each URL in a new tab rather than a new window.
When run under Mac OS X, $BROWSER should be set to camino , firefox , or safari.  Web uses AppleScript to talk to the browser.  If $BROWSER is not set, web looks for Firefox in /Applications/Firefox.app and uses it if found; otherwise it uses Safari.
Wmail starts the composition of a new mail message to address.
The choice of mailer is determined by the $MAILER environment variable. The supported mailers are:
browser invoke the mailer via a mailto:// URL passed to web
Web and wmail are invoked as start commands in the rules for opening web pages and writing mail messages.
/plumb/basic plumbing rules using web and wmail
GUNICORN(1)            User Contributed Perl Documentation           GUNICORN(1)
gunicorn - Event-based HTTP/WSGI server
gunicorn [OPTIONS] APP_MODULE
-c CONFIG, --config=CONFIG Config file. [none]
-b BIND, --bind=BIND Address to listen on. Ex. 127.0.0.1:8000 or unix:/tmp/gunicorn.sock
-w WORKERS, --workers=WORKERS Number of workers to spawn. [1]
-a ARBITER, --arbiter=ARBITER gunicorn arbiter entry point or module [egg:gunicorn#main]
-p PIDFILE, --pid=PIDFILE Set the background PID FILE
-D, --daemon Run daemonized in the background.
-m UMASK, --umask=UMASK Define umask of daemon process
-u USER, --user=USER Change worker user
-g GROUP, --group=GROUP Change worker group
-n PROC_NAME, --name=PROC_NAME Process name
--log-level=LOGLEVEL Log level below which to silence messages. [info]
--log-file=LOGFILE Log to a file. - equals stdout. [-]
d, --debug Debug mode. only 1 worker.
Green Unicorn (gunicorn) is an HTTP/WSGI server designed to serve fast clients or sleepy applications. That is to say; behind a buffering front- end server such as nginx or lighttpd.
* Optional support for Eventlet and Gevent to provide asynchronous long-polling ("Comet") connections. * Process management: Gunicorn reaps and restarts workers that die. * Easy integration with Django and Paster compatible applications (Pylons, TurboGears 2, etc. * Load balancing via pre-fork and a shared socket * Graceful worker process restarts * Upgrading without losing connections * Decode chunked transfers on-the-fly, allowing upload progress notifications or stream-based protocols over HTTP
KERNEL PARAMETERS There are various kernel parameters that you might want to tune in order to deal with a large number of simultaneous connections. Generally these should only affect sites with a large number of concurrent requests and apply to any sort of network server you may be running. They're listed here for ease of reference.
The commands listed are tested under Mac OS X 10.6. Your flavor of Unix may use slightly different flags. Always reference the appropriate man pages if uncertain.
INCREASING THE FILE DESCRIPTOR LIMIT One of the first settings that usually needs to be bumped is the maximum number of open file descriptors for a given process. For the confused out there, remember that Unices treat sockets as files.
$ sudo ulimit -n 1024
INCREASING THE LISTEN QUEUE SIZE Listening sockets have an associated queue of incoming connections that are waiting to be accepted. If you happen to have a stampede of clients that fill up this queue new connections will eventually start getting dropped.
$ sudo sysctl -w kern.ipc.somaxconn="1024"
WIDENING THE EPHEMERAL PORT RANGE After a socket is closed it eventually enters the TIME_WAIT state. This can become an issue after a prolonged burst of client activity. Eventually the ephemeral port range is used up which can cause new connections to stall while they wait for a valid port.
This setting is generally only required on machines that are being used to test a network server.
gunicorn_paster(1)
GO-DOC(1)                    General Commands Manual                   GO-DOC(1)
go - tool for managing Go source code
go doc [-n] [-x] [ packages ]
Doc runs the godoc command on the packages named by the import paths.
For more about godoc, see 'godoc godoc'.
For more about specifying packages, see go-packages(7).
To run godoc with specific options, run godoc itself.
-n     The -n flag causes tool to print the command that would be executed but not execute it.
-x     The -x flag causes clean to print remove commands as it executes them.
godoc(1).
This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others).
OFFLINEIMAP(1)                                                    OFFLINEIMAP(1)
offlineimap - Synchronize mailboxes and Maildirs both ways or one either way.
offlineimap (options)
Synchronize the accounts configured in the configuration file via IMAP. Each account has two sides. One of the side must be an IMAP server. The other side can either be a Maildir or another IMAP server.
Works with Python 2.
-h, --help Display summary of options.
--version Output version.
-V Output offlineimap version and additional imaplib2 information.
--dry-run Run in dry run mode.
Do not actually modify any store but check and print what synchronization actions would be taken if a sync would be performed. It will not precisely give the exact information what will happen. If e.g. we need to create a folder, it merely outputs Would create folder X, but not how many and which mails it would transfer.
--info Output information on the configured email repositories.
Useful for debugging and bug reporting. Use in conjunction with the ‘-a’ option to limit the output to a single account. This mode will prevent any actual sync to occur and exits after it output the debug information.
-1 Limit multithreading operations and run solely a single-thread sync.
This effectively sets the maxsyncaccounts and all maxconnections configuration file variables to 1 (the number).
-P <directory> Set OfflineIMAP into profile mode.
The program will create DIR (it must not already exist). As it runs, Python profiling information about each thread is logged into profiledir. Please note: This option is present for debugging and optimization only, and should NOT be used unless you have a specific reason to do so. It will significantly decrease program performance, may reduce reliability, and can generate huge amounts of data. This option implies the ‘-1’ option.
-a <account1[,account2[,...]]> Overrides the accounts section in the config file.
Allows one to specify a particular account or set of accounts to sync without having to edit the config file.
-c <path/to/configuration_file> Specifies a configuration file to use.
-d <type1[,type2[,...]]> Enables debugging for OfflineIMAP.
This is useful if you are to track down a malfunction or figure out what is going on under the hood. This option requires one or more debugtypes, separated by commas. These define what exactly will be debugged, and so far include options: "imap", "thread", "maildir" or "ALL". The imap option will enable IMAP protocol stream and parsing debugging. Note that the output may contain passwords, so take care to remove that from the debugging output before sending it to anyone else. The maildir option will enable debugging for certain Maildir operations. The use of any debug option (unless "thread" is included), implies the single-thread option ‘-1’.
-l <path/to/file.log> Send logs to <file.log>.
-s Send logs to syslog.
-f <folder1[,folder1[,...]]> Only sync the specified folders.
The folder names are the untranslated foldernames of the remote repository. This command-line option overrides any folderfilter and folderincludes options in the configuration file.
-k <[section:]option=value Override any configuration file option.
If "section" is omitted, it defaults to "general". Any underscores in the section name are replaced with spaces: for instance, to override option "autorefresh" in the "[Account Personal]" section in the config file one would use ‘-k Account_Personal:autorefresh=30’. Repeat this option as much as necessary to redefine multiple options.
-o Run only once.
Ignore any autorefresh setting in the configuration file.
-q Run only quick synchronizations.
Ignore any flag updates on IMAP servers. If a flag on the remote IMAP changes, and we have the message locally, it will be left untouched in a quick run. This option is ignored if maxage is set.
-u <UI> Specifies an alternative user interface to use.
This overrides the default specified in the configuration file. The UI specified with ‘-u’ will be forced to be used, even if checks determine that it is not usable. Possible interface choices are: quiet, basic, syslog, ttyui, blinkenlights, machineui.
--delete-folder Delete a folder on the remote repository.
Only one account must be specified/configured for this feature to work or you must provide one account with -a. The folder name must be provided with the remote separators (likely /) in UTF-8 if utf8foldernames is enabled or in IMAP otherwise. E.g.: "Remote/folder/name".
--migrate-fmd5-using-nametrans Migrate FMD5 hashes from versions prior to 6.3.5.
The way that FMD5 hashes are calculated was changed in version 6.3.5 (now using the nametrans folder name) introducing a regression which may lead to re-uploading all messages. Try and fix the above regression by calculating the correct FMD5 values and renaming the corresponding messages.
Caution Since the FMD5 part of the filename changes, this may lead to UID conflicts. Ensure to dispose a proper backup of both the cache and the Maildir before running this fix as well as verify the results using the ‘--dry-run’ flag first.
--mbnames-prune Remove dangling entries for removed accounts or if mbnames is not enabled/used anymore.
Internally, offlineimap build intermediate mbnames files. They are added automatically when mbnames is enabled. However, disabling accounts so they are not synced anymore does not necessarily means they should be removed from the file built by mbnames. It is required to start offlineimap with this CLI option each time accounts are removed. When run, any account not in the accounts configuration option are removed in the mbnames file.
It is possible to manually remove intermediate files in <metadata>/mbnames/.
Notice this option honors --dry-run.
By default, we use fairly conservative settings that are safe for syncing but that might not be the best performing one. Once you got everything set up and running, you might want to look into speeding up your synchronization. Here are a couple of hints and tips on how to achieve this.
1. Synchronize more than one account.
By default we only use one connection to an IMAP server. Using 2 or even 3 speeds things up considerably in most cases. In order to synchronize more than one account concurrently, consider starting one instance of offlineimap per account.
Warning enabling the maxsyncaccounts and maxconnections options is deprecated since it’s known to have race conditions.
2. Use folderfilters.
The quickest sync is a sync that can ignore some folders. I sort my inbox into monthly folders, and ignore every folder that is more than 2-3 months old, this lets me only inspect a fraction of my Mails on every sync. If you haven’t done this yet, do it :). See the folderfilter section in offlineimap.conf.
3. The sqlite cache.
OfflineImap caches the state of the synchronisation to e.g. be able to determine if a mail has been added or deleted on either side.
The historical status cache was a plain text file that was writing out the complete file for each single new message (or even changed flag) to a temporary file. If there was plenty of files in a folder this was bound to make things slow. The latest status cache is sqlite. This saves plenty of disk activity.
The historical plain status cache is not supported anymore but migrating from a very old installation using the plain text cache is still supported. In this case, you may want to delete the old cache directory in <metadata>/Account-<account>/LocalStatus manually (the sqlite cache stands in the LocalStatus-sqlite folder). First, make sure you have run the new version of offlineimap for all your accounts so that the status cache was migrated.
4. Use quick sync.
A regular sync will request all flags and all UIDs of all mails in each folder which takes quite some time. A quick sync only compares the number of messages in a folder on the IMAP side (it will detect flag changes on the Maildir side of things though). A quick sync on my smallish account will take 7 seconds rather than 40 seconds. E.g. run a cron script that does a regular sync once a day, and does quick syncs ‘-q’ only synchronizing the ‘-f INBOX’ in between.
5. Turn off fsync.
In the [general] section you can set fsync to True or False. If you want to play 110% safe and wait for all operations to hit the disk before continuing, you can set this to True. If you set it to False, you lose some of that safety, trading it for speed.
By default, OfflineIMAP will connect using any method that openssl supports, that is SSLv2, SSLv3, or TLSv1.
Do note that SSLv2 is notoriously insecure and deprecated. Unfortunately, python2 does not offer easy ways to disable SSLv2. It is recommended you test your setup and make sure that the mail server does not use an SSLv2 connection. Use e.g. "openssl s_client -host mail.server -port 443" to find out the connection that is used by default.
•   Certificate checking
Unfortunately, by default we will not verify the certificate of an IMAP TLS/SSL server we connect to, so connecting by SSL is no guarantee against man-in-the-middle attacks. While verifying a server certificate checking the fingerprint is recommended. There is currently only one safe way to ensure that you connect to the correct server in an encrypted manner: you can specify a sslcacertfile setting in your repository section of offlineimap.conf pointing to a file that contains (among others) a CA Certificate in PEM format which validating your server certificate. In this case, we will check that:
1. The server SSL certificate is validated by the CA Certificate.
2. The server host name matches the SSL certificate.
3. The server certificate is not past its expiration date.
The FAQ has an entry on how to create your own certificate and CA certificate.
•   StartTLS
If you have not configured your account to connect via SSL anyway, OfflineImap will still attempt to set up an SSL connection via the STARTTLS function, in case the imap server supports it.
There is no certificate or fingerprint checking involved at all, when using STARTTLS (the underlying imaplib library does not support this yet). This means that you will be protected against passively listening eavesdroppers and they will not be able to see your password or email contents. However, this will not protect you from active attacks, such as Man-In-The-Middle attacks which cause you to connect to the wrong server and pretend to be your mail server.
DO NOT RELY ON STARTTLS AS A SAFE CONNECTION GUARANTEEING THE AUTHENTICITY OF YOUR IMAP SERVER!
OfflineImap listens to the unix signals SIGUSR1, SIGUSR2, SIGTERM, SIGINT, SIGHUP, SIGQUIT.
•   If sent a SIGUSR1 it will abort any current (or next future) sleep of all accounts that are configured to autorefresh. In effect, this will trigger a full sync of all accounts to be performed as soon as possible.
•   If sent a SIGUSR2 or SIGABRT, it will stop autorefresh mode for all accounts. That is, accounts will abort any current sleep and will exit after a currently running synchronization has finished. This signal can be used to gracefully exit out of a running offlineimap "daemon".
•   SIGTERM, SIGINT, SIGHUP are all treated to gracefully terminate as soon as possible. This means it will finish syncing the current folder in each account, close keep alive connections, remove locks on the accounts and exit.
It may take up to 10 seconds, if autorefresh option is used.
More than one SIGTERM will behave like SIGQUIT.
•   If sent SIGQUIT, dumps stack traces for all threads and tries to dump process core.
•   Deletions.
While in usual run the deletions are propagated. To prevent from data loss, removing a folder makes offlineimap re-sync the folder. However, propagating the removal of the whole content of a folder can happen in the two following cases:
•   The whole content of a folder is deleted but the folder directory still exists.
•   The parent directory of the folder was deleted.
•   SSL3 write pending.
Users enabling SSL may hit a bug about "SSL3 write pending". If so, the account(s) will stay unsynchronised from the time the bug appeared. Running OfflineIMAP again can help. We are still working on this bug. Patches or detailed bug reports would be appreciated. Please check you’re running the last stable version and send us a report to the mailing list including the full log.
•   IDLE support is incomplete and experimental. Bugs may be encountered.
•   No hook exists for "run after an IDLE response".
Email will show up, but may not be processed until the next refresh cycle.
•   nametrans may not be supported correctly.
•   IMAP IDLE <→ IMAP IDLE doesn’t work yet.
•   IDLE might stop syncing on a system suspend/resume.
•   IDLE may only work "once" per refresh.
If you encounter this bug, please send a report to the list!
•   Maildir support in Windows drive.
Maildir uses colon character (:) in message file names. Colon is however forbidden character in windows drives. There are several workarounds for that situation:
1. Enable file name character translation in windows registry (not tested).
•   http://support.microsoft.com/kb/289627
2. Use cygwin managed mount (not tested).
•   not available anymore since cygwin 1.7
3. Use "maildir-windows-compatible = yes" account OfflineIMAP configuration.
•   That makes OfflineIMAP to use exclamation mark (!) instead of colon for storing messages. Such files can be written to windows partitions. But you will probably loose compatibility with other programs trying to read the same Maildir.
•   Exclamation mark was chosen because of the note in http://docs.python.org/library/mailbox.html
•   If you have some messages already stored without this option, you will have to re-sync them again
•   OfflineIMAP confused after system suspend.
When resuming a suspended session, OfflineIMAP does not cleanly handles the broken socket(s) if socktimeout option is not set. You should enable this option with a value like 10.
•   OfflineIMAP confused when mails change while in a sync.
When OfflineIMAP is syncing, some events happening since the invocation on remote or local side are badly handled. OfflineIMAP won’t track for changes during the sync.
•   Sharing a maildir with multiple IMAP servers.
Generally a word of caution mixing IMAP repositories on the same Maildir root. You have to be careful that you never use the same maildir folder for 2 IMAP servers. In the best case, the folder MD5 will be different, and you will get a loop where it will upload your mails to both servers in turn (infinitely!) as it thinks you have placed new mails in the local Maildir. In the worst case, the MD5 is the same (likely) and mail UIDs overlap (likely too!) and it will fail to sync some mails as it thinks they are already existent.
I would create a new local Maildir Repository for the Personal Gmail and use a different root to be on the safe side here. You could e.g. use
`~/mail/Pro' as Maildir root for the ProGmail and `~/mail/Personal' as root for the personal one.
If you then point your local mutt, or whatever MUA you use to ‘~/mail/’ as root, it should still recognize all folders.
•   Edge cases with maxage causing too many messages to be synced.
All messages from at most maxage days ago (+/- a few hours, depending on timezones) are synced, but there are cases in which older messages can also be synced. This happens when a message’s UID is significantly higher than those of other messages with similar dates, e.g. when messages are added to the local folder behind offlineimap’s back, causing them to get assigned a new UID, or when offlineimap first syncs a pre-existing Maildir. In the latter case, it could appear as if a noticeable and random subset of old messages are synced.
•   Offlineimap hangs.
When having unexpected hangs it’s advised to set ‘singlethreadperfolder’ to yes, especially when in IMAP/IMAP mode (no maildir).
•   Passwords in netrc.
Offlineimap doesn’t know how to retrieve passwords when more than one account is stored in the netrc file. See https://github.com/OfflineIMAP/offlineimap/issues/295.
•   XOAUTH2
XOAUTH2 might be a bit tricky to set up. Make sure you’ve followed the step to step guide in offlineimap.conf. The known bugs about Gmail are tracked at https://github.com/OfflineIMAP/offlineimap/labels/Gmail.
Sometimes, you might hit one of the following error:
•   [imap]: xoauth2handler: response "{u’error': u’invalid_grant'}"
•   oauth2handler got: {u’error': u’invalid_grant'}
In such case, we had reports that generating a new refresh token from the same client ID and secret can help.
Google documentation on "invalid_grant".
When you try to use a refresh token, the following returns you an invalid_grant error:
- Your server's clock is not in sync with network time protocol - NTP. - The refresh token limit has been exceeded.
Token expiration.
It is possible that a granted token might no longer work. A token might stop working for one of these reasons:
- The user has revoked access. - The token has not been used for six months. - The user changed passwords and the token contains Gmail scopes. - The user account has exceeded a certain number of token requests.
There is currently a limit of 50 refresh tokens per user account per client. If the limit is reached, creating a new token automatically invalidates the oldest token without warning. This limit does not apply to service accounts.
See https://developers.google.com/analytics/devguides/config/mgmt/v3/authorization and https://developers.google.com/identity/protocols/OAuth2#expiration to know more.
•   "does not have message with UID" with Microsoft servers
`ERROR: IMAP server 'Server ### Remote' does not have a message with UID 'xxx'`
Microsoft IMAP servers are not compliant with the RFC. It is currently required to folderfilter some faulting folders. See http://www.offlineimap.org/doc/FAQ.html#exchange-and-office365 for a detailed list.
John Goerzen, Sebastian Spaetz, Eygene Ryabinkin, Nicolas Sebrecht.
offlineimapui(7), openssl(1), signal(7), sqlite3(1). http://www.offlineimap.org
lpr(1)                            OpenPrinting                            lpr(1)
lpr - print files
lpr [ -E ] [ -H server[:port] ] [ -U username ] [ -P destination[/instance] ] [ -# num-copies [ -h ] [ -l ] [ -m ] [ -o option[=value] ] [ -p ] [ -q ] [ -r ] [ -C title ] [ -J title ] [ -T title ] [ file(s) ]
lpr submits files for printing.  Files named on the command line are sent to the named printer or the default destination if no destination is specified.  If no files are listed on the command-line, lpr reads the print file from the standard input.
THE DEFAULT DESTINATION CUPS provides many ways to set the default destination. The LPDEST and PRINTER environment variables are consulted first.  If neither are set, the current default set using the lpoptions(1) command is used, followed by the default set using the lpadmin(8) command.
The following options are recognized by lpr:
-E   Forces encryption when connecting to the server.
-H server[:port] Specifies an alternate server.
-C "name"
-J "name"
-T "name" Sets the job name/title.
-P destination[/instance] Prints files to the named printer.
-U username Specifies an alternate username.
-# copies Sets the number of copies to print.
-h   Disables banner printing. This option is equivalent to -o job-sheets=none.
-l   Specifies that the print file is already formatted for the destination and should be sent without filtering.  This option is equivalent to -o raw.
-m   Send an email on job completion.
-o option[=value] Sets a job option.  See "COMMON JOB OPTIONS" below.
-p   Specifies that the print file should be formatted with a shaded header with the date, time, job name, and page number.  This option is equivalent to -o prettyprint and is only useful when printing text files.
-q   Hold job for printing.
-r   Specifies that the named print files should be deleted after submitting them.
COMMON JOB OPTIONS Aside from the printer-specific options reported by the lpoptions(1) command, the following generic options are available:
-o job-sheets=name Prints a cover page (banner) with the document.  The "name" can be "classified", "confidential", "secret", "standard", "topsecret", or "unclassified".
-o media=size Sets the page size to size. Most printers support at least the size names "a4", "letter", and "legal".
-o number-up={2|4|6|9|16} Prints 2, 4, 6, 9, or 16 document (input) pages on each output page.
-o orientation-requested=4 Prints the job in landscape (rotated 90 degrees counter-clockwise).
-o orientation-requested=5 Prints the job in landscape (rotated 90 degrees clockwise).
-o orientation-requested=6 Prints the job in reverse portrait (rotated 180 degrees).
-o print-quality=3
-o print-quality=4
-o print-quality=5 Specifies the output quality - draft (3), normal (4), or best (5).
-o sides=one-sided Prints on one side of the paper.
-o sides=two-sided-long-edge Prints on both sides of the paper for portrait output.
-o sides=two-sided-short-edge Prints on both sides of the paper for landscape output.
The -c, -d, -f, -g, -i, -n, -t, -v, and -w options are not supported by CUPS and produce a warning message if used.
Print two copies of a document to the default printer:
lpr -# 2 filename
Print a double-sided legal document to a printer called "foo":
lpr -P foo -o media=legal -o sides=two-sided-long-edge filename
Print a presentation document 2-up to a printer called "foo":
lpr -P foo -o number-up=2 filename
cancel(1), lp(1), lpadmin(8), lpoptions(1), lpq(1), lprm(1), lpstat(1), CUPS Online Help (http://localhost:631/help)
Copyright Â© 2021 by OpenPrinting.
BCOMPS(1)                    General Commands Manual                   BCOMPS(1)
bcomps - biconnected components filter for graphs
bcomps [ -stvx?  ] [ -ooutfile ] [ files ]
bcomps decomposes graphs into their biconnected components, printing the components to standard output.
-s     No output graph is printed. Implies the -v flag.
-t     Print the underlying block-cutvertex tree.
-x     Each biconnected component is printed as a separate root graph.
-v     Prints number of blocks and cutvertices.
-o outfile If specified, each root graph will be written to a different file with the names derived from outfile. In particular, if both -o and -x flags are used, then each block is written to a different file. If outfile does not have a suffix, the nth block of the ith graph is written to outfile_n_i. However, the 0th block of the 0th graph is written to outfile.
If outfile has a suffix, i.e., has the form base.sfx, then the files will have the same name as above, except appended with .sfx.
The block-cutvertex tree of ith graph is written to outfile_n_T, with an appended suffix if specified.
By default, each input graph is printed, with each block given as a subgraph whose name is a concatenation of the name of the input graph, the string "_bcc_" and the number of the block.
The following operand is supported:
files   Names of files containing 1 or more graphs in dot format.  If no files operand is specified, the standard input will be used.
bcomps returns 0 if all the input graphs are biconnected; and non-zero if any graph has multiple blocks, or any error occurred.
It is possible, though unlikely, that the names used for connected components and their subgraphs may conflict with existing subgraph names.
Emden R. Gansner <erg@research.att.com>
ccomps(1), gc(1), dot(1), gvpr(1), gvcolor(1), acyclic(1), sccmap(1), tred(1), libgraph(3)
REDIS-SERVER(1)              General Commands Manual             REDIS-SERVER(1)
redis-server - Persistent key-value database
redis-server configfile
Redis is a key-value database. It is similar to memcached but the dataset is not volatile and other datatypes (such as lists and sets) are natively supported.
configfile Read options from specified configuration file.
On Debian GNU/Linux systems, redis-server is typically started via the /etc/init.d/redis-server initscript, not manually. This defaults to using /etc/redis/redis.conf as a configuration file.
redis-server was written by Salvatore Sanfilippo.
This manual page was written by Chris Lamb <lamby@debian.org> for the Debian project (but may be used by others).
BOLTCTL(1)                         bolt Manual                        BOLTCTL(1)
boltctl - control the thunderbolt device manager
boltctl authorize DEVICE boltctl config boltctl domains boltctl enroll DEVICE boltctl forget DEVICE boltctl info DEVICE boltctl list boltctl monitor boltctl power
boltctl is the command line interface to interact with boltd, the system daemon that manages Thunderbolt 3(TM) devices. It can be used to query the state of devices as well as manage them.