neulab/tldr huggingface dataset:
You can force searching everything by specifying "all" as the first argument.
info   Is used to list a description and summary information about available packages; takes the same arguments as in the List Options section below.
clean  Is used to clean up various things which accumulate in the yum cache directory over time.  More complete details can be found in the Clean Options section below.
makecache Is used to download and make usable all the metadata for the currently enabled yum repos.
groups A command, new in 3.4.2, that collects all the subcommands that act on groups together.
"group install" is used to install all of the individual packages in a group, of the specified types (this works as if you'd taken each of those package names and put them on the command line for a "yum install" command). The group_package_types configuration option specifies which types will be installed.
"group update" is just an alias for groupinstall, which will do the right thing because "yum install X" and "yum update X" do the same thing, when X is already installed.
"group list" is used to list the available groups from all yum repos. Groups are marked as "installed" if all mandatory packages are installed, or if a group doesn't have any mandatory packages then it is installed if any of the optional or default package are installed.  The optional "hidden" argument will also list groups marked as not being "user visible". If you pass the -v option, to enable verbose mode, then the groupids are displayed.
"group remove" is used to remove all of the packages in a group, unlike "groupinstall" this will remove everything regardless of group_package_types. It is worth pointing out that packages can be in more than one group, so "group install X Y" followed by "group remove Y" does not do give you the same result as "group install X".
The groupremove_leaf_only configuration changes the behaviour of this command to only remove packages which aren't required by something else.
"group info" is used to give the description and package list of a group (and which type those packages are marked as). Note that you can use the yum-filter-data and yum-list-data plugins to get/use the data the other way around (Ie. what groups own packages need updating). If you pass the -v option, to enable verbose mode, then the package names are matched against installed/available packages similar to the list command.
shell  Is used to enter the 'yum shell', when a filename is specified the contents of that file is executed in yum shell mode. See yum- shell(8) for more info
resolvedep Is used to list packages providing the specified dependencies, at most one package is listed per dependency.
localinstall Is used to install a set of local rpm files. If required the enabled repositories will be used to resolve dependencies. Note that the install command will do a local install, if given a filename. This option is maintained for legacy reasons only.
localupdate Is used to update the system by specifying local rpm files. Only the specified rpm files of which an older version is already installed will be installed, the remaining specified packages will be ignored.  If required the enabled repositories will be used to resolve dependencies. Note that the update command will do a local update, if given a filename. This option is maintained for legacy reasons only.
reinstall Will reinstall the identically versioned package as is currently installed.  This does not work for "installonly" packages, like Kernels. reinstall operates on groups, files, provides and filelists just like the "install" command.
downgrade Will try and downgrade a package from the version currently installed to the previously highest version (or the specified version).  The depsolver will not necessarily work, but if you specify all the packages it should work (and thus. all the simple cases will work). Also this does not work for "installonly" packages, like Kernels. downgrade operates on groups, files, provides, filelists and rpm files just like the "install" command.
deplist Produces a list of all dependencies and what packages provide those dependencies for the given packages. As of 3.2.30 it now just shows the latest version of each package that matches (this can be changed by using --showduplicates) and it only shows the newest providers (which can be changed by using --verbose).
repolist Produces a list of configured repositories. The default is to list all enabled repositories. If you pass -v, for verbose mode, more information is listed. If the first argument is 'enabled', 'disabled' or 'all' then the command will list those types of repos.
You can pass repo id or name arguments, or wildcards which to match against both of those. However if the id or name matches exactly then the repo will be listed even if you are listing enabled repos. and it is disabled.
In non-verbose mode the first column will start with a '*' if the repo. has metalink data and the latest metadata is not local. For non-verbose mode the last column will also display the number of packages in the repo. and (if there are any user specified excludes) the number of packages excluded.
One last special feature of repolist, is that if you are in non- verbose mode then yum will ignore any repo errors and output the information it can get (Eg. "yum clean all; yum -C repolist" will output something, although the package counts/etc. will be zeroed out).
version Produces a "version" of the rpmdb, and of the enabled repositories if "all" is given as the first argument. You can also specify version groups in the version-groups config. file. If you pass -v, for verbose mode, more information is listed. The version is calculated by taking a sha1 hash of the packages (in sorted order), and the checksum_type/checksum_data entries from the yumdb. Note that this rpmdb version is now also used significantly within yum (esp. in yum history).
The version command will now show "groups" of packages as a separate version, and so takes sub-commands:
"version grouplist" - List the defined version groups.
"version groupinfo" - Get the complete list of packages within one or more version groups.
"version installed" - This is the default, only show the version information for installed packages.
"version available" - Only show the version information for available packages.
"version all" - Show the version information for installed and available packages.
"version nogroups | nogroups-*" - Just show the main version information.
"version group-*" - Just show the grouped version information, if more arguments are given then only show the data for those groups.
history The history command allows the user to view what has happened in past transactions (assuming the history_record config. option is set). You can use info/list/packages-list/summary to view what happened, undo/redo/rollback to act on that information and new to start a new history file.
The info/list/summary commands take either a transaction id or a package (with wildcards, as in Specifying package names), all three can also be passed no arguments. list can be passed the keyword "all" to list all the transactions.
The packages-list command takes a package  (with wildcards, as in Specifying package names).
The undo/redo/rollback commands take either a single transaction id or the keyword last and an offset from the last transaction (Eg. if you've done 250 transactions, "last" refers to transaction 250, and "last-4" refers to transaction 246).
The undo/redo commands act on the specified transaction, undo'ing or repeating the work of that transaction. While the rollback command will undo all transactions upto the point of the specified transaction. For example, if you have 3 transactions, where package A; B and C where installed respectively.  Then "undo 1" will try to remove pacakge A, "redo 1" will try to install package A (if it is not still installed), and "rollback 1" will try to remove packages B and C. Note that after a "rollback 1" you will have a fourth transaction, although the ending rpmdb version (see: yum version) should be the same in transactions 1 and 4.
The addon-info command takes a transaction ID, and the packages- list command takes a package (with wildcards).
In "history list" you can change the behaviour of the 2nd column via. the configuration option history_list_view.
In "history list" output the Altered column also gives some extra information if there was something not good with the transaction (this is also shown at the end of the package column in the packages-list command).
> - The rpmdb was changed, outside yum, after the transaction. < - The rpmdb was changed, outside yum, before the transaction. * - The transaction aborted before completion. # - The transaction completed, but with a non-zero status. E - The transaction completed fine, but had warning/error output during the transaction. P - The transaction completed fine, but problems already existed in the rpmdb. s - The transaction completed fine, but --skip-broken was enabled and had to skip some packages.
check  Checks the local rpmdb and produces information on any problems it finds. You can pass the check command the arguments "dependencies" or "duplicates", to limit the checking that is performed (the default is "all" which does both).
The info command can also take ranges of transaction ids, of the form start..end, which will then display a merged history as if all the transactions in the range had happened at once. Eg. "history info 1..4" will merge the first four transactions and display them as a single transaction.
help   Produces help, either for all commands or if given a command name then the help for that particular command.
Most command line options can be set using the configuration file as well and the descriptions indicate the necessary configuration option to set.
-h, --help Help; display a help message and then quit.
-y, --assumeyes Assume yes; assume that the answer to any question which would be asked is yes. Configuration Option: assumeyes
-c, --config=[config file] Specifies the config file location - can take HTTP and FTP URLs and local file paths.
-q, --quiet Run without output.  Note that you likely also want to use -y.
-v, --verbose Run with a lot of debugging output.
-d, --debuglevel=[number] Sets the debugging level to [number] - turns up or down the amount of things that are printed. Practical range: 0 - 10 Configuration Option: debuglevel
-e, --errorlevel=[number] Sets the error level to [number] Practical range 0 - 10. 0 means print only critical errors about which you must be told. 1 means print all errors, even ones that are not overly important. 1+ means print more errors (if any) -e 0 is good for cron jobs. Configuration Option: errorlevel
--rpmverbosity=[name] Sets the debug level to [name] for rpm scriplets. 'info' is the default, other options are: 'critical', 'emergency', 'error', 'warn' and 'debug'. Configuration Option: rpmverbosity
-R, --randomwait=[time in minutes] Sets the maximum amount of time yum will wait before performing a command - it randomizes over the time.
-C, --cacheonly Tells yum to run entirely from system cache - does not download or update any headers unless it has to to perform the requested action. If you're using this as a user yum will not use the tempcache for the user but will only use the system cache in the system cachedir.
--version Reports the yum version number and installed package versions for everything in history_record_packages (can be added to by plugins).
--showduplicates Doesn't limit packages to their latest versions in the info, list and search commands (will also affect plugins which use the doPackageLists() API).
--installroot=root Specifies an alternative installroot, relative to which all packages will be installed. Think of this like doing "chroot <root> yum" except using --installroot allows yum to work before the chroot is created.  Note: You may also want to use the option --releasever=/ when creating the installroot as otherwise the $releasever value is taken from the rpmdb within the installroot (and thus. will be empty, before creation). Configuration Option: installroot
--enablerepo=repoidglob Enables specific repositories by id or glob that have been disabled in the configuration file using the enabled=0 option. Configuration Option: enabled
--disablerepo=repoidglob Disables specific repositories by id or glob. Configuration Option: enabled
--obsoletes This option only has affect for an update, it enables yumÂ´s obsoletes processing logic. For more information see the update command above. Configuration Option: obsoletes
-x, --exclude=package Exclude a specific package by name or glob from updates on all repositories.  Configuration Option: exclude
--color=[always|auto|never] Display colorized output automatically, depending on the output terminal, always (using ANSI codes) or never. Note that some commands (Eg. list and info) will do a little extra work when color is enabled.  Configuration Option: color
--disableexcludes=[all|main|repoid] Disable the excludes defined in your config files. Takes one of three options: all == disable all excludes main == disable excludes defined in [main] in yum.conf repoid == disable excludes defined for that repo
--disableplugin=plugin Run with one or more plugins disabled, the argument is a comma separated list of wildcards to match against plugin names.
--noplugins Run with all plugins disabled. Configuration Option: plugins
--nogpgcheck Run with GPG signature checking disabled. Configuration Option: gpgcheck
--skip-broken Resolve depsolve problems by removing packages that are causing problems from the transaction. Configuration Option: skip_broken
--releasever=version Pretend the current release version is the given string. This is very useful when combined with --installroot. You can also use --releasever=/ to take the releasever information from outside the installroot.  Note that with the default upstream cachedir, of /var/cache/yum, using this option will corrupt your cache (and you can use $releasever in your cachedir configuration to stop this).
-t, --tolerant This option currently does nothing.
--setopt=option=value Set any config option in yum config or repo files. For options in the global config just use: --setopt=option=value for repo options use: --setopt=repoid.option=value
The following are the ways which you can invoke yum in list mode.  Note that all list commands include information on the version of the package.
The format of the output of yum list is:
name.arch [epoch:]version-release  repo or @installed-from-repo
yum list [all | glob_exp1] [glob_exp2] [...] List all available and installed packages.
yum list available [glob_exp1] [...] List all packages in the yum repositories available to be installed.
yum list updates [glob_exp1] [...] List all packages with updates available in the yum repositories.
yum list installed [glob_exp1] [...] List the packages specified by args.  If an argument does not match the name of an available package, it is assumed to be a shell-style glob and any matches are printed.
yum list extras [glob_exp1] [...] List the packages installed on the system that are not available in any yum repository listed in the config file.
yum list obsoletes [glob_exp1] [...] List the packages installed on the system that are obsoleted by packages in any yum repository listed in the config file.
yum list recent List packages recently added into the repositories. This is often not helpful, but what you may really want to use is "yum list- updateinfo new" from the security yum plugin.
A package can be referred to for install, update, remove, list, info etc with any of the following as well as globs of any of the following:
name name.arch name-ver name-ver-rel name-ver-rel.arch name-epoch:ver-rel.arch epoch:name-ver-rel.arch
For example: yum remove kernel-2.4.1-10.i686 this will remove this specific kernel-ver-rel.arch.
Or:          yum list available 'foo*' will list all available packages that match 'foo*'. (The single quotes will keep your shell from expanding the globs.)
The following are the ways which you can invoke yum in clean mode. Note that "all files" in the commands below means "all files in currently enabled repositories".  If you want to also clean any (temporarily) disabled repositories you need to use --enablerepo='*' option.
yum clean expire-cache Eliminate the local data saying when the metadata and mirrorlists were downloaded for each repo. This means yum will revalidate the cache for each repo. next time it is used. However if the cache is still valid, nothing significant was deleted.
yum clean packages Eliminate any cached packages from the system.  Note that packages are not automatically deleted after they are downloaded.
yum clean headers Eliminate all of the header files, which old versions of yum used for dependency resolution.
yum clean metadata Eliminate all of the files which yum uses to determine the remote availability of packages. Using this option will force yum to download all the metadata the next time it is run.
yum clean dbcache Eliminate the sqlite cache used for faster access to metadata. Using this option will force yum to download the sqlite metadata the next time it is run, or recreate the sqlite metadata if using an older repo.
yum clean rpmdb Eliminate any cached data from the local rpmdb.
yum clean plugins Tell any enabled plugins to eliminate their cached data.
yum clean all Does all of the above.
Yum can be extended through the use of plugins. A plugin is a Python ".py" file which is installed in one of the directories specified by the pluginpath option in yum.conf. For a plugin to work, the following conditions must be met:
1. The plugin module file must be installed in the plugin path as just described.
2. The global plugins option in /etc/yum/yum.conf must be set to `1'.
3. A configuration file for the plugin must exist in /etc/yum/pluginconf.d/<plugin_name>.conf and the enabled setting in this file must set to `1'. The minimal content for such a configuration file is:
[main] enabled = 1
See the yum.conf(5) man page for more information on plugin related configuration options.
/etc/yum/yum.conf /etc/yum/version-groups.conf /etc/yum/repos.d/ /etc/yum/pluginconf.d/ /var/cache/yum/
pkcon (1) yum.conf (5) yum-updatesd (8) package-cleanup (1) repoquery (1) yum-complete-transaction (1) yumdownloader (1) yum-utils (1) yum-security (8) http://yum.baseurl.org/ http://yum.baseurl.org/wiki/Faq yum search yum
See the Authors file included with this program.
There of course aren't any bugs, but if you find any, you should first consult the FAQ mentioned above and then email the mailing list: yum@lists.baseurl.org or filed in bugzilla.
wuzz(1)                      General Commands Manual                     wuzz(1)
wuzz - interactive tool for HTTP inspection
Wuzz is an interactive tool for generating and sending HTTP requests, as well as viewing the responses. Instead of having to specify the HTTP headers, parameters, body etc. on the command-line, a simple and intuitive CUI (console user interface) can be used. Wuzz's command line arguments are similar to cURL's arguments, so it can be used to inspect and modify requests copied from a browser's network inspector with the "copy as cURL" feature.
wuzz [OPTIONS]... [URL]
-H, --header HEADER Specify an HTTP Header
-d, --data-, --data-binary DATA Specify a (binary) data to be sent
-X, --request METHOD Select an HTTP Request Method (GET, POST, PUT, DELETE, HEAD)
-t, --timeout MILLISECONDS Request timeout in Milliseconds
-c, --config PATH Use a custom configuration file
-h, --help Show wuzz's built-in help (may be more up to date)
-j, --json JSON Add JSON request data and set related request headers
-k, --insecure Allow untrusted TLS certificates
-R, --disable-redirects Do not follow HTTP redirects
-T, --tls MINX,MAX Restrict allowed TLS versions (SSL3.0, TLS1.0, TLS1.1, TLS1.2)
wuzz -T TLS1.1 (TLS1.1 only)
wuzz -T TLS1.0,TLS1.1 (from TLS1.0 up to TLS1.1)
--tlsv1.0 Force TLS1.0 only
--tlsv1.1 Force TLS1.1 only
--tlsv1.2 Force TLS1.2 only
-1, --tlsv1 Force TLS version 1.x (1.0, 1.1 or 1.2)
-v, --version Display wuzz version number
-x, --proxy URL Use HTTP(S) or SOCKS5 proxy
The default location for the configuration file is $XDG_CONFIG_HOME/wuzz/config.toml. The -c / --config switch can be used to load a configuration file from a different location.  This package ships with an example configuration in /usr/share/doc/wuzz/examples/.
┌───────────────────┬────────────────────────────────────┐ │Ctrl+R             │  Send request                      │ ├───────────────────┼────────────────────────────────────┤ │Return (Enter)     │  Send request (only from URL view) │ ├───────────────────┼────────────────────────────────────┤ │Ctrl+S             │  Save response                     │ ├───────────────────┼────────────────────────────────────┤ │Ctrl+C             │  Quit                              │ ├───────────────────┼────────────────────────────────────┤ │Ctrl+K, Shift+Tab  │  Previous view                     │ ├───────────────────┼────────────────────────────────────┤ │Ctrl+J, Tab        │  Next view                         │ ├───────────────────┼────────────────────────────────────┤ │Alt+H              │  Toggle History                    │ ├───────────────────┼────────────────────────────────────┤ │Down (Arrow Keys)  │  Move down one view line           │ ├───────────────────┼────────────────────────────────────┤ │Up (Arrow Keys)    │  Move up one view line             │ ├───────────────────┼────────────────────────────────────┤ │Page down          │  Move down one view page           │ ├───────────────────┼────────────────────────────────────┤ │Page up            │  Move up one view page             │ ├───────────────────┼────────────────────────────────────┤ │F1                 │  Display help                      │ ├───────────────────┼────────────────────────────────────┤ │F2                 │  Jump to URL                       │ ├───────────────────┼────────────────────────────────────┤ │F3                 │  Jump to query parameters          │ ├───────────────────┼────────────────────────────────────┤ │F4                 │  Jump to HTTP method               │ ├───────────────────┼────────────────────────────────────┤ │F5                 │  Jump to request body              │ ├───────────────────┼────────────────────────────────────┤ │F6                 │  Jump to headers                   │ ├───────────────────┼────────────────────────────────────┤ │F7                 │  Jump to search                    │ ├───────────────────┼────────────────────────────────────┤ │F8                 │  Jump to response headers          │ ├───────────────────┼────────────────────────────────────┤ │F9                 │  Jump to response body             │ └───────────────────┴────────────────────────────────────┘
curl(1)
This manual page was written by Jack Henschel <jackdev@mailbox.org>, for the Debian project (and may be used by others).
CLOCK(1)                     General Commands Manual                    CLOCK(1)
hwclock - a hardveróra (Real Time Clock) lekérdezése és beállítása
hwclock --show [ --utc ] [ --test ] [ --debug ] hwclock --set --date=dátum [ --utc ] [ --test ] [ --debug] hwclock --systohc [ --utc ] [ --test ] [ --debug ] hwclock --hctosys [ --utc ] [ --test ] [ --debug ] hwclock --adjust [ --utc ] [ --test ] [ --debug ] hwclock --version [ --debug ]
Az opciókat egyértelmű rövidítéssel is alkalmazhatjuk.
A "clock" programmal való kompatibilitás érdekében használhatók az -r, -w, -s, -a, -v, -u, és -D opciók is.
A hwclock egy eszköz a Hardverórához. A segítségével ki lehet íratni az aktuális időt, be lehet állítani a Hardverórát egy megadott időhöz vagy a Rendszerórához, vagy be lehet állítani a Rendszerórát a Hardverórához.
A hwclock programot rendszeresen futtathatjuk, hogy kiegyenlítsük azt az időeltérést, amit a magára hagyott rendszer létrehoz.
Az alábbiak közül pontosan 1 opciót kell megadni a hwclock programnak, attól függően, hogy milyen funkciót szeretnénk.
--show Kiolvassa a Hardverórát és kiírja az időt.
--set  Beállítja a Hardverórát a --date opció által megadott időpontra.
--hctosys Beállítja a Rendszerórát a Hardverórához. Ezt az opciót legjobban egy olyan szkriptben tudjuk kihasználni, ami a rendszer indításakor lefut.
--systohc Hozzáállítja a Hardverórát a pillanatnyi Rendszerórához.
--adjust Az ismert eltérés alapján hozzáadja a Hardverórához (vagy kivonja) a szükséges korrekciót. (A működés leírását lásd lejjebb).
--version Kiírja a hwclock verzióját. Ha megadod a --set opciót, meg kell adnod a következő opciót is :
--date="dátum és időpont" Ide írjuk be azt a dátumot és időpontot, amire a Hardverórát be akarjuk állítani. Ennek az opciónak a tartalmát átadjuk a date(1) programnak. Például
hwclock --set --date="11/27/98 18:45:00"
A következő opciókat a legtöbb funkció mellett használhatjuk.
--utc  Azt jelzi, hogy a Hardveróra a 'Universal Coordinated Time'-nak ('Koordinált Világidő', korábbi nevén 'Greenwich Mean Time') megfelelő időt tartalmazza. A felhasználó választásától függ, hogy az óra az UTC vagy a helyi időzónának megfelelő idő szerint jár-e.
Figyelem ! Ha nem adod meg az --utc opciót, vagy fordítva, megadod, amikor nem kellene, mindkét esetben összezavarodik a Hardveróra beállítása vagy a lekérdezés.
--test Mindent megcsinál, kivéve a Hardveróra tényleges beállítását.  Ez hasznos, különösen a --debug opcióval együtt.
--debug A hwclock kiírja, hogy mit is csinál éppen.
MEGJEGYZÉSEK : Órák egy Linux rendszerben. Egy Linux rendszerben két fő óra van :
A Hardveróra : Ez egy olyan óra, ami bármely programtól függetlenül fut, még akkor is, ha a gép ki van kapcsolva. Az ISA szabvány részeként van meghatározva.  Egy vezérlő program ki tudja ezt az órát olvasni, vagy be tudja állítani.  Lehetséges az 1 másodperces impulzusok kezdetének érzékelése, így az órának látszólag végtelen lehet a pontossága.
Ezt az órát nevezik hardverórának, 'real time clock'-nak, 'RTC'-nek, valós idejű órának, BIOS órának, vagy CMOS órának is.
A Rendszeróra : Ez az az idő, amit a Linux kernelen belüli óra mutatni tud, és az ISA időzítő megszakítása vezérli. Csak akkor van értelmezve, ha a Linux fut. A Rendszeridő az 1970. január 1. 00:00:00 óta eltelt időt tartalmazza másodpercekben. Ennek ellenére a Rendszeridő nem egész szám, így a pontossága tetszőlegesen javítható.
A Rendszeróra tartalmazza azt az időt, ami fontos számunkra. A Hardveróra alapvető feladata bármely rendszerben az, hogy az óra akkor is fusson, amikor a gép ki van kapcsolva. Amikor elindul a Linux rendszer, beállítja a Rendszerórát a Hardverórához, így a Hardverórát ezután nem használjuk. Megjegyezzük, hogy a DOS operációs rendszerekben (illetve az arra épülő egyéb rendszerekben) - amihez az ISA tervezve lett - a Hardveróra az egyetlen valós idejű óra.
Fontos, hogy a date(1L) használatával ne okozzunk időugrást a Rendszerórában, amikor a rendszer fut.
Ezzel szemben a Hardverórát tetszőlegesen lehet állítani, mialatt a rendszer fut.  Mint programozó, használhatod az adjtimex(8) programot is a Rendszeróra beállításához.
Az 'Adjust', vagyis 'Beállítás' funkció A Hardveróra általában nem túl pontos. Azonban a pontatlanság nagyrészt jól kezelhető, mert az óra azonos mértékű időt siet vagy késik minden nap.  Ezt rendszeres időeltérésnek nevezhetjük.  A hwclock program 'adjust' funkciója teszi lehetővé azt, hogy rendszeres kiigazítást végezzünk ennek a rendszeres időeltérésnek a kiküszöbölésére.
Röviden : A hwclock a /etc/adjtime fájlban tárol néhány információt, ami az óra pontosításához szükséges.
Tegyük fel kiindulásként, hogy nincs 'adjtime' fájlunk. Ekkor kiadhatjuk a hwclock --set --date=...  parancsot, hogy a Hardverórát beállítsuk a megadott időhöz.  A hwclock program létrehozza az 'adjtime' fájlt és beleírja az aktuális időt.  Ez egyúttal az óra beállításának az utolsó ideje is lesz.  Tegyük fel, hogy mondjuk 5 nap alatt az óra 10 másodpercet siet, így újból kiadjuk a hwclock --set --date=... parancsot, hogy visszaállítsuk a 10 másodpercet.  A hwclock program frissíti az 'adjtime' fájlt, beleírja az utolsó órabeállítás időpontját és rögzíti benne, hogy az óra napi 2 másodpercet siet.  24 óra elteltével újból kiadhatjuk a hwclock --adjust parancsot.  A hwclock program megnézi az 'adjtime' fájlt, látja benne, hogy az óránk napi 2 másodpercet siet, és most már éppen eltelt egy nap. Igy kivon 2 másodpercet a Hardverórából.  Rögzíti a fájlban az aktuális időt, mint az utolsó beállítás időpontját.
Minden alkalommal, amikor beállítjuk az órát a --set opcióval, a hwclock újra kiszámolja a rendszeres idő-eltérés mértékét, figyelembe véve, hogy mikor volt utoljára pontosítva az óra, milyen idő-eltérés volt korábban kiszámolva és hogy jelenleg mennyivel tér el az óra.
Egy kis hiba az óra beállításába mindig becsúszik, amikor a hwclock programmal szeretnénk pontosítani az órát, így a hwclock nem hajtja végre azokat a beállításokat, amikor az eltérés kevesebb 1 másodpercnél.
Hasznos egy hwclock --adjust parancsot kiadni közvetlenül a hwclock --hctosys parancs előtt a rendszer indításakor, illetve akkor is, ha a 'cron' segítségével végeztetjük a beállítást.
Az '/etc/adjtime' fájl formátuma :
1. sor : 3 számból áll :
1) rendszeres idő-eltérés másodperc / nap mértékegységben, lebegőpontos, decimális kijelzéssel;
2) az utolsó beállítás ideje 1970. jan. 1. óta, másodpercekben, decimális egész szám;
3) nulla, a clock programmal való kompatibilitás miatt.
2. sor : 1 számból áll :
A legelső beállítás ideje másodpercben 1970. jan. 1. óta.
Használhatod a hwclock programhoz azt az 'adjtime' fájlt, amit előzőleg a clock programmal hoztál létre.
/etc/adjtime
adjtimex(8), date(1), gettimeofday(2), settimeofday(2), crontab(1)
A hwclock programot Bryan Henderson írta 1996 szeptemberében, Charles Hedrick, Rob Hooft, és Harald Koenig, a clock program íróinak munkája alapján. A program készítésének története nyomon követhető a forráskódban.
Gyulai Mihály <mgyulai@freemail.c3.hu>
MSSH(1)                      General Commands Manual                     MSSH(1)
mssh - tool to administrate multiple servers at once
mssh [OPTION]... (-a ALIAS | HOSTS[:PORT])
MultiSSH is a GTK+ based ssh client to issue the same commands to multiple servers.
MultiSSH will connect to the servers specified in HOSTS into optional PORT.
-a, --alias=ALIAS Open hosts associated with named alias
-V, --version Output version information and exit
The configuration file for MultiSSH should be located in $HOME/.mssh_clusters
It uses a simple key: value pair system with an alias on the left of the colon and a space separated list of hosts on the right.
Also uses a combination of {key} value system with a command alias inside curls on the left and a text to send to the terminals on the right.
Modifier key (configurable throught preferences) + arrow key to move around terminals.
Ctrl + Shift + x to toggling maximize terminal.
Ctrl + Shift + n to show the dialog for adding new host.
MultiSSH was originally written by Bradley Smith <brad@brad-smith.co.uk> and it is currently develop by Héctor García <hector@debian.org>
Copyright (C) 2014 Héctor García <hector@debian.org> Copyright (C) 2009 Bradley Smith <brad@brad-smith.co.uk>
Report bugs to <hector@debian.org>.
dotnet restore command(1)           .NET Core          dotnet restore command(1)
dotnet restore - Restores the dependencies and tools of a project.
.NET Core 2.x dotnet restore [<ROOT>] [--configfile] [--disable-parallel] [--force] [--ignore-failed-sources] [--no-cache] [--no-dependencies] [--packages] [-r|--runtime] [-s|--source] [-v|--verbosity] [--interactive] dotnet restore [-h|--help]
.NET Core 1.x dotnet restore [<ROOT>] [--configfile] [--disable-parallel] [--ignore-failed-sources] [--no-cache] [--no-dependencies] [--packages] [-r|--runtime] [-s|--source] [-v|--verbosity] dotnet restore [-h|--help]
The dotnet restore command uses NuGet to restore dependencies as well as project-specific tools that are specified in the project file.  By default, the restoration of dependencies and tools are executed in parallel.
To restore the dependencies, NuGet needs the feeds where the packages are located.  Feeds are usually provided via the nuget.config configuration file.  A default configuration file is provided when the CLI tools are installed.  You specify additional feeds by creating your own nuget.config file in the project directory.  You also specify additional feeds per invocation at a command prompt.
For dependencies, you specify where the restored packages are placed during the restore operation using the --packages argument.  If not specified, the default NuGet package cache is used, which is found in the .nuget/packages directory in the user’s home directory on all operating systems.  For example, /home/user1 on Linux or C:1 on Windows.
For project-specific tooling, dotnet restore first restores the package in which the tool is packed, and then proceeds to restore the tool’s dependencies as specified in its project file.
nuget.config differences The behavior of the dotnet restore command is affected by the settings in the nuget.config file, if present.  For example, setting the globalPackagesFolder in nuget.config places the restored NuGet packages in the specified folder.  This is an alternative to specifying the --packages option on the dotnet restore command.  For more information, see the nuget.config reference.
There are three specific settings that dotnet restore ignores:
• bindingRedirects
Binding redirects don’t work with <PackageReference> elements and .NET Core only supports <PackageReference> elements for NuGet packages.
• solution
This setting is Visual Studio specific and doesn’t apply to .NET Core. .NET Core doesn’t use a packages.config file and instead uses <PackageReference> elements for NuGet packages.
• trustedSigners
This setting isn’t applicable as NuGet doesn’t yet support cross- platform verification of trusted packages.
Implicit dotnet restore Starting with .NET Core 2.0, dotnet restore is run implicitly if necessary when you issue the following commands:
• dotnet new
• dotnet build
• dotnet build-server
• dotnet run
• dotnet test
• dotnet publish
• dotnet pack
In most cases, you no longer need to explicitly use the dotnet restore command.
Sometimes, it might be inconvenient to run dotnet restore implicitly. For example, some automated systems, such as build systems, need to call dotnet restore explicitly to control when the restore occurs so that they can control network usage.  To prevent dotnet restore from running implicitly, you can use the --no-restore flag with any of these commands to disable implicit restore.
Arguments ROOT
Optional path to the project file to restore.
.NET Core 2.x --configfile <FILE>
The NuGet configuration file (nuget.config) to use for the restore operation.
--disable-parallel
Disables restoring multiple projects in parallel.
--ignore-failed-sources
Only warn about failed sources if there are packages meeting the version requirement.
Specifies to not cache packages and HTTP requests.
When restoring a project with project-to-project (P2P) references, restores the root project and not the references.
--packages <PACKAGES_DIRECTORY>
Specifies the directory for restored packages.
Specifies a runtime for the package restore.  This is used to restore packages for runtimes not explicitly listed in the <RuntimeIdentifiers> tag in the .csproj file.  For a list of Runtime Identifiers (RIDs), see the RID catalog.  Provide multiple RIDs by specifying this option multiple times.
-s|--source <SOURCE>
Specifies a NuGet package source to use during the restore operation. This setting overrides all of the sources specified in the nuget.config files.  Multiple sources can be provided by specifying this option multiple times.
--verbosity <LEVEL>
Sets the verbosity level of the command.  Allowed values are q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic].  Default value is minimal.
Allows the command to stop and wait for user input or action (for example to complete authentication).  Since .NET Core 2.1.400.
.NET Core 1.x --configfile <FILE>
Specifies a NuGet package source to use during the restore operation. This overrides all of the sources specified in the nuget.config files, effectively reading the nuget.config file as if the <packageSource> element was not there.  Multiple sources can be provided by specifying this option multiple times.
Sets the verbosity level of the command.  Allowed values are q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic].  The default is minimal.
Restore dependencies and tools for the project in the current directory:
Restore dependencies and tools for the app1 project found in the given path:
dotnet restore ~/projects/app1/app1.csproj
Restore the dependencies and tools for the project in the current directory using the file path provided as the source:
dotnet restore -s c:\packages\mypackages
Restore the dependencies and tools for the project in the current directory using the two file paths provided as sources:
dotnet restore -s c:\packages\mypackages -s c:\packages\myotherpackages
Restore dependencies and tools for the project in the current directory showing detailed output:
dotnet restore --verbosity detailed
QUTEBROWSER(1)                 qutebrowser manpage                QUTEBROWSER(1)
qutebrowser - a keyboard-driven, vim-like browser based on PyQt5.
qutebrowser [-OPTION [...]] [:COMMAND [...]] [URL [...]]
qutebrowser is a keyboard-focused browser with a minimal GUI. It’s based on Python and Qt5 and is free software, licensed under the GPL.
It was inspired by other browsers/addons like dwb and Vimperator/Pentadactyl.
Note the commands and settings of qutebrowser are not described in this manpage, but in the help integrated in qutebrowser - use the ":help" command to show it.
positional arguments :command Commands to execute on startup.
URL URLs to open on startup (empty as a window separator).
optional arguments -h, --help show this help message and exit
-B BASEDIR, --basedir BASEDIR Base directory for all storage.
-C CONFIG, --config-py CONFIG Path to config.py.
-V, --version Show version and quit.
-s OPTION VALUE, --set OPTION VALUE Set a temporary setting for this session.
-r SESSION, --restore SESSION Restore a named session.
-R, --override-restore Don’t restore a session even if one would be restored.
--target {auto,tab,tab-bg,tab-silent,tab-bg-silent,window,private-window} How URLs should be opened if there is already a qutebrowser instance running.
--backend {webkit,webengine} Which backend to use.
--desktop-file-name DESKTOP_FILE_NAME Set the base name of the desktop entry for this application. Used to set the app_id under Wayland. See https://doc.qt.io/qt-5/qguiapplication.html#desktopFileName-prop
--untrusted-args Mark all following arguments as untrusted, which enforces that they are URLs/search terms (and not flags or commands)
debug arguments -l {critical,error,warning,info,debug,vdebug}, --loglevel {critical,error,warning,info,debug,vdebug} Override the configured console loglevel
--logfilter LOGFILTER Comma-separated list of things to be logged to the debug log on stdout.
--loglines LOGLINES How many lines of the debug log to keep in RAM (-1: unlimited).
-d, --debug Turn on debugging options.
--json-logging Output log lines in JSON format (one object per line).
--nocolor Turn off colored logging.
--force-color Force colored logging
--nowindow Don’t show the main window.
-T, --temp-basedir Use a temporary basedir.
--no-err-windows Don’t show any error windows (used for tests/smoke.py).
--qt-arg NAME VALUE Pass an argument with a value to Qt. For example, you can do --qt-arg geometry 650x555+200+300 to set the window geometry.
--qt-flag QT_FLAG Pass an argument to Qt as flag.
-D DEBUG_FLAGS, --debug-flag DEBUG_FLAGS Pass name of debugging feature to be turned on.
•   ~/.config/qutebrowser/config.py: Configuration file.
•   ~/.config/qutebrowser/autoconfig.yml: Configuration done via the GUI.
•   ~/.config/qutebrowser/quickmarks: Saved quickmarks.
•   ~/.local/share/qutebrowser/: Various state information.
•   ~/.cache/qutebrowser/: Temporary data.
Note qutebrowser conforms to the XDG basedir specification - if XDG_CONFIG_HOME, XDG_DATA_HOME or XDG_CACHE_HOME are set in the environment, the directories configured there are used instead of the above defaults.
Bugs are tracked in the Github issue tracker at https://github.com/qutebrowser/qutebrowser/issues.
If you found a bug, use the built-in :report command to create a bug report with all information needed.
If you prefer, you can also write to the mailinglist at qutebrowser@lists.qutebrowser.org instead.
For security bugs, please contact me directly at me@the-compiler.org, GPG ID 0xFD55A072.
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
You should have received a copy of the GNU General Public License along with this program. If not, see https://www.gnu.org/licenses/.
•   Website: https://www.qutebrowser.org/
•   Mailinglist: qutebrowser@lists.qutebrowser.org / https://lists.schokokeks.org/mailman/listinfo.cgi/qutebrowser
•   Announce-only mailinglist: qutebrowser-announce@lists.qutebrowser.org / https://lists.schokokeks.org/mailman/listinfo.cgi/qutebrowser-announce
•   IRC: #qutebrowser on Libera Chat (webchat, via Matrix)
•   Github: https://github.com/qutebrowser/qutebrowser
qutebrowser was written by Florian Bruhin. All contributors can be found in the README file distributed with qutebrowser.
HOST(1)                              BIND 9                              HOST(1)
host - DNS lookup utility
host [-aACdlnrsTUwv] [-c class] [-N ndots] [-p port] [-R number] [-t type] [-W wait] [-m flag] [ [-4] | [-6] ] [-v] [-V] {name} [server]
host is a simple utility for performing DNS lookups. It is normally used to convert names to IP addresses and vice versa. When no arguments or options are given, host prints a short summary of its command-line arguments and options.
name is the domain name that is to be looked up. It can also be a dotted-decimal IPv4 address or a colon-delimited IPv6 address, in which case host by default performs a reverse lookup for that address.  server is an optional argument which is either the name or IP address of the name server that host should query instead of the server or servers listed in /etc/resolv.conf.
-4     This option specifies that only IPv4 should be used for query transport. See also the -6 option.
-6     This option specifies that only IPv6 should be used for query transport. See also the -4 option.
-a     The -a ("all") option is normally equivalent to -v -t ANY. It also affects the behavior of the -l list zone option.
-A     The -A ("almost all") option is equivalent to -a, except that RRSIG, NSEC, and NSEC3 records are omitted from the output.
-c class This option specifies the query class, which can be used to lookup HS (Hesiod) or CH (Chaosnet) class resource records. The default class is IN (Internet).
-C     This option indicates that named should check consistency, meaning that host queries the SOA records for zone name from all the listed authoritative name servers for that zone. The list of name servers is defined by the NS records that are found for the zone.
-d     This option prints debugging traces, and is equivalent to the -v verbose option.
-l     This option tells named` to list the zone, meaning the ``host command performs a zone transfer of zone name and prints out the NS, PTR, and address records (A/AAAA).
Together, the -l -a options print all records in the zone.
-N ndots This option specifies the number of dots (ndots) that have to be in name for it to be considered absolute. The default value is that defined using the ndots statement in /etc/resolv.conf, or 1 if no ndots statement is present. Names with fewer dots are interpreted as relative names, and are searched for in the domains listed in the search or domain directive in /etc/resolv.conf.
-p port This option specifies the port to query on the server. The default is 53.
-r     This option specifies a non-recursive query; setting this option clears the RD (recursion desired) bit in the query. This means that the name server receiving the query does not attempt to resolve name. The -r option enables host to mimic the behavior of a name server by making non-recursive queries, and expecting to receive answers to those queries that can be referrals to other name servers.
-R number This option specifies the number of retries for UDP queries. If number is negative or zero, the number of retries is silently set to 1. The default value is 1, or the value of the attempts option in /etc/resolv.conf, if set.
-s     This option tells named not to send the query to the next nameserver if any server responds with a SERVFAIL response, which is the reverse of normal stub resolver behavior.
-t type This option specifies the query type. The type argument can be any recognized query type: CNAME, NS, SOA, TXT, DNSKEY, AXFR, etc.
When no query type is specified, host automatically selects an appropriate query type. By default, it looks for A, AAAA, and MX records. If the -C option is given, queries are made for SOA records. If name is a dotted-decimal IPv4 address or colon-delimited IPv6 address, host queries for PTR records.
If a query type of IXFR is chosen, the starting serial number can be specified by appending an equals sign (=), followed by the starting serial number, e.g., -t IXFR=12345678.
-T; -U This option specifies TCP or UDP. By default, host uses UDP when making queries; the -T option makes it use a TCP connection when querying the name server. TCP is automatically selected for queries that require it, such as zone transfer (AXFR) requests. Type ANY queries default to TCP, but can be forced to use UDP initially via -U.
-m flag This option sets memory usage debugging: the flag can be record, usage, or trace. The -m option can be specified more than once to set multiple flags.
-v     This option sets verbose output, and is equivalent to the -d debug option. Verbose output can also be enabled by setting the debug option in /etc/resolv.conf.
-V     This option prints the version number and exits.
-w     This option sets "wait forever": the query timeout is set to the maximum possible. See also the -W option.
-W wait This options sets the length of the wait timeout, indicating that named should wait for up to wait seconds for a reply. If wait is less than 1, the wait interval is set to 1 second.
By default, host waits for 5 seconds for UDP responses and 10 seconds for TCP connections. These defaults can be overridden by the timeout option in /etc/resolv.conf.
See also the -w option.
If host has been built with IDN (internationalized domain name) support, it can accept and display non-ASCII domain names. host appropriately converts character encoding of a domain name before sending a request to a DNS server or displaying a reply from the server.  To turn off IDN support, define the IDN_DISABLE environment variable. IDN support is disabled if the variable is set when host runs.
dig(1), named(8).
Internet Systems Consortium
2021, Internet Systems Consortium
CMP(1P)                     POSIX Programmer's Manual                    CMP(1P)
cmp — compare two files
cmp [-l|-s] file1 file2
The cmp utility shall compare two files. The cmp utility shall write no output if the files are the same. Under default options, if they differ, it shall write to standard output the byte and line number at which the first difference occurred. Bytes and lines shall be numbered beginning with 1.
The cmp utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines.
-l        (Lowercase ell.) Write the byte number (decimal) and the differing bytes (octal) for each difference.
-s        Write nothing to standard output or standard error when files differ; indicate differing files through exit status only.  It is unspecified whether a diagnostic message is written to standard error when an error is encountered; if a message is not written, the error is indicated through exit status only.
If both file1 and file2 refer to standard input or refer to the same FIFO special, block special, or character special file, the results are undefined.
The standard input shall be used only if the file1 or file2 operand refers to standard input. See the INPUT FILES section.
The input files can be any file type.
The following environment variables shall affect the execution of cmp: