malcontent-client

package: malcontent-tools

title: malcontent-client(8)

summary: Parental Controls Access Utility

text:
# malcontent-client(8)

## NAME
malcontent-client - Parental Controls Access Utility

## SYNOPSIS
malcontent-client get-app-filter [-q] [-n] [USER]

malcontent-client check-app-filter [-q] [-n] [USER] ARG

malcontent-client set-app-filter [-q] [-n] [USER] ARG

malcontent-client oars-section [-q] [-n] [USER] SECTION

malcontent-client get-session-limits [-q] [-n] [USER]

malcontent-client set-session-limits [-q] [-n] [USER] LIMIT-TYPE

malcontent-client monitor [-q] [USER]

malcontent-client record-usage [-q] USAGE-ENTRIES

malcontent-client query-usage [-q] USER RECORD-TYPE IDENTIFIER

malcontent-client get-estimated-times [-q] RECORD-TYPE

malcontent-client request-extension [-q] RECORD-TYPE IDENTIFIER [DURATION]

malcontent-client get-web-filter [-q] [-n] [USER]

malcontent-client set-web-filter [-q] [-n] [USER] ARG

malcontent-client update-web-filters [-q] [-n] [USER]

malcontent-client dump-web-filters [-q] [-n] [USER]

## DESCRIPTION
malcontent-client is a utility for querying and updating the parental controls settings for users on the system. It will typically require administrator access to do anything more than query the current user’s parental controls.

It communicates with accounts-service, which stores parental controls data.

Its first argument is a command to run. The supported commands are documented below.

The command line API and output format are unstable and likely to change in future versions of malcontent-client.

## get-app-filter OPTIONS
Get the app filter for a user. For example:

\# malcontent-client get-app-filter timmy

USER

Username or ID of the user to get the app filter for. If not specified, the current user will be used by default.

-q, --quiet

Only output error messages, and no informational messages, as the operation progresses. (Default: Output informational messages.)

-n, --no-interactive

Do not allow interactive authorization with polkit. If this is needed to complete the operation, the operation will fail. (Default: Allow interactive authorization.)

## check-app-filter OPTIONS
Check if a given program, content type or flatpak ref is permitted to be used by a user, according to their current app filter. For example:

\# malcontent-client check-app-filter timmy $(which gnome-calculator) # malcontent-client check-app-filter timmy x-scheme-handler/http

\# malcontent-client check-app-filter timmy app/com.realm667.WolfenDoom_Blade_of_Agony/x86_64/stable

USER

Username or ID of the user to get the app filter for. If not specified, the current user will be used by default.

ARG

Path to a program, content type or flatpak ref to check against the app filter, to see if it is allowed for the specified user.

-q, --quiet

Only output error messages, and no informational messages, as the operation progresses. (Default: Output informational messages.)

-n, --no-interactive

Do not allow interactive authorization with polkit. If this is needed to complete the operation, the operation will fail. (Default: Allow interactive authorization.)

## set-app-filter OPTIONS
Set the app filter for a user, replacing all previous values in it. For example:

\# malcontent-client set-app-filter timmy \

--disallow-user-installation \

$(which gnome-calculator) \

x-scheme-handler/http \

app/com.realm667.WolfenDoom_Blade_of_Agony/x86_64/stable

USER

Username or ID of the user to set the app filter for. If not specified, the current user will be used by default.

ARG

Item to filter in the user’s app filter. This could either be an absolute path or flatpak ref of a program to block; a content type to block all programs handling that type; or an OARS section=value pair to block installation of apps with a more extreme rating for that OARS section. Multiple items may be specified, and they will replace the user’s current app filter in entirety. If zero items are specified, the app filter is cleared.

--allow-user-installation

Allow the user to install flatpaks to their user repository.

--disallow-user-installation

Disallow the user from installing flatpaks to their user repository.

--allow-system-installation

Allow the user to install flatpaks to the system repository.

--disallow-system-installation

Disallow the user from installing flatpaks to the system repository.

-q, --quiet

Only output error messages, and no informational messages, as the operation progresses. (Default: Output informational messages.)

-n, --no-interactive

Do not allow interactive authorization with polkit. If this is needed to complete the operation, the operation will fail. (Default: Allow interactive authorization.)

## oars-section OPTIONS
Get the value set for a specific OARS section from the app filter of the given user. For example:

\# malcontent-client oars-section timmy language-profanity

USER

Username or ID of the user to get the OARS filter for. If not specified, the current user will be used by default.

SECTION

OARS section to get the restriction level of the given user for. For example, language-profanity.

-q, --quiet

Only output error messages, and no informational messages, as the operation progresses. (Default: Output informational messages.)

-n, --no-interactive

Do not allow interactive authorization with polkit. If this is needed to complete the operation, the operation will fail. (Default: Allow interactive authorization.)

## get-session-limits OPTIONS
Get the session limits set for a user. For example:

\# malcontent-client get-session-limits timmy

USER

Username or ID of the user to get the session limits for. If not specified, the current user will be used by default.

-q, --quiet

Only output error messages, and no informational messages, as the operation progresses. (Default: Output informational messages.)

-n, --no-interactive

Do not allow interactive authorization with polkit. If this is needed to complete the operation, the operation will fail. (Default: Allow interactive authorization.)

--now yyyy-mm-ddThh:mm:ssZ

Check session limits (in particular, session expiry time) against the given date/time, provided in ISO 8601 format. (Default: Current date/time.)

## set-session-limits OPTIONS
Set the session limits for a user, replacing its previous value completely. For example:

\# malcontent-client set-session-limits timmy \

daily-schedule \

--start-time 16:00 --end-time 18:00

USER

Username or ID of the user to set the app filter for. If not specified, the current user will be used by default.

LIMIT-TYPE

The type of session limit to use for this user. Possible values are:

none

- No session limits.

daily-schedule --start-time HH[:MM[:SS]] --end-time HH[:MM[:SS]]

- Daily schedule with fixed start and end times. These must be provided as two arguments giving the time of day when the schedule starts and ends.

daily-limit --daily-limit SECONDS

- Daily limit on the overall active time using the computer for the day. This must be provided as a limit length in seconds.

-q, --quiet

Only output error messages, and no informational messages, as the operation progresses. (Default: Output informational messages.)

-n, --no-interactive

Do not allow interactive authorization with polkit. If this is needed to complete the operation, the operation will fail. (Default: Allow interactive authorization.)

## monitor OPTIONS
Monitor changes to any of the parental controls settings for a specific user. For example:

\# malcontent-client monitor timmy

USER

Username or ID of the user to monitor the parental controls for. If not specified, the current user will be used by default.

-q, --quiet

Only output error messages, and no informational messages, as the operation progresses. (Default: Output informational messages.)

## record-usage OPTIONS
Record session or app usage times for the current user. For example:

\# malcontent-client record-usage 2025-04-22T08:00:00Z 2025-04-22T16:00:00Z login-session # malcontent-client record-usage 2025-04-22T08:00:00Z 2025-04-22T16:00:00Z app "org.gnome.gedit"

USAGE-ENTRIES

One or more usage entries to add. Each entry is a set of four arguments:

- the start date and time of the usage period (in ISO 8601 format),

- the end date and time of the usage period (also in ISO 8601 format),

- the record type (login-session or app) and

- the record identifier (this must be the empty string for login-session records, and the app ID for app records).

The final record identifier in the arguments list can be omitted if it’s empty. -q, --quiet

Only output error messages, and no informational messages, as the operation progresses. (Default: Output informational messages.)

## query-usage OPTIONS
Query session or app usage times for a given user. For example:

\# malcontent-client query-usage bob login-session "" # malcontent-client query-usage bob app "org.gnome.gedit"

USER

Username or ID of the user to get the usage information for.

RECORD-TYPE IDENTIFIER

The record type and identifier to query for records of. See the documentation for the record-usage command for valid values.

-q, --quiet

Only output error messages, and no informational messages, as the operation progresses. (Default: Output informational messages.)

-n, --no-interactive

Do not allow interactive authorization with polkit. If this is needed to complete the operation, the operation will fail. (Default: Allow interactive authorization.)

## get-estimated-times OPTIONS
Query the usage and session limits for the current user, to work out how much time is remaining in their session or for using apps. For example:

\# malcontent-client get-estimated-times login-session

RECORD-TYPE

Type of usage record to query for. This can be login-session or app.

-q, --quiet

Only output error messages, and no informational messages, as the operation progresses. (Default: Output informational messages.)

## request-extension OPTIONS
Request an extension to the screen time limit for the current user, for their session or the specified app. For example:

\# malcontent-client request-extension login-session ""

RECORD-TYPE IDENTIFIER

The record type and identifier to request an extension for. See the documentation for the record-usage command for valid values.

DURATION

The duration of the extension to request (in seconds), or zero to allow the parent to choose the duration (typically this means until the end of today). (Default: Zero.)

-q, --quiet

Only output error messages, and no informational messages, as the operation progresses. (Default: Output informational messages.)

## get-web-filter OPTIONS
Get the web filter for a user. For example:

\# malcontent-client get-web-filter timmy

USER

Username or ID of the user to get the web filter for. If not specified, the current user will be used by default.

-q, --quiet

Only output error messages, and no informational messages, as the operation progresses. (Default: Output informational messages.)

-n, --no-interactive

Do not allow interactive authorization with polkit. If this is needed to complete the operation, the operation will fail. (Default: Allow interactive authorization.)

## set-web-filter OPTIONS
Set the web filter for a user, replacing all previous values in it. For example:

\# malcontent-client set-web-filter timmy \

--force-safe-search \

--filter-type block-list \

adult=https://v.firebog.net/hosts/Prigent-Adult.txt \

advertising=https://v.firebog.net/hosts/Prigent-Ads.txt \

reddit.com \

~mastodon.social

USER

Username or ID of the user to set the web filter for. If not specified, the current user will be used by default.

ARG

Item to filter in the user’s web filter. This could either be an id=filter-URI pair, or an individual hostname to block. Either type of item may be prefixed with ~ (a tilde) to allow it rather than blocking it. A filter URI must point to a text file in the same format as /etc/hosts listing websites to filter. The associated ID is an arbitrary alphanumeric string used to track the filter over time, even if its canonical URI changes. Multiple items may be specified, and they will replace the user’s current web filter in entirety. If zero items are specified, the web filter is cleared.

--force-safe-search

Force ‘safe search’ mode to be enabled for known search engines and popular websites.

--filter-type

The type of web filter to use for this user. Possible values are:

none

- No web filtering.

block-list

- Websites are allowed by default unless listed in one of the block lists. The websites in the allow lists are always allowed.

allow-list

- Websites are blocked by default unless listed in one of the allow lists. The block lists are ignored.

-q, --quiet

Only output error messages, and no informational messages, as the operation progresses. (Default: Output informational messages.)

-n, --no-interactive

Do not allow interactive authorization with polkit. If this is needed to complete the operation, the operation will fail. (Default: Allow interactive authorization.)

## update-web-filters OPTIONS
Download and update the compiled web filters for a specific user, or for all users. This will read the current web filter configuration for the user and update the compiled filter database using that configuration. For example:

\# malcontent-client update-web-filters timmy

To update the web filter configuration for a user, use malcontent-client set-web-filter. USER

Username or ID of the user to update the web filters for. If not specified, the web filters will be updated for all users who have them set.

-q, --quiet

Only output error messages, and no informational messages, as the operation progresses. (Default: Output informational messages.)

-n, --no-interactive

Do not allow interactive authorization with polkit. If this is needed to complete the operation, the operation will fail. (Default: Allow interactive authorization.)

## dump-web-filters OPTIONS
Dump the compiled web filters for a specific user, or for all users. These are the filter rules which are currently being used. For example:

\# malcontent-client dump-web-filters timmy

USER

Username or ID of the user to dump the web filters for. If not specified, the web filters will be dumped for all users who have them set.

-q, --quiet

Only output error messages, and no informational messages, as the operation progresses. (Default: Output informational messages.)

-n, --no-interactive

Do not allow interactive authorization with polkit. If this is needed to complete the operation, the operation will fail. (Default: Allow interactive authorization.)

## ENVIRONMENT
malcontent-client supports the standard GLib environment variables for debugging. These variables are not intended to be used in production:

$G_MESSAGES_DEBUG

This variable can contain one or more debug domain names to display debug output for. The value all will enable all debug output. The default is for no debug output to be enabled.

## EXIT STATUS
malcontent-client may return one of several error codes if it encounters problems.

0

No problems occurred. The utility ran and successfully queried the app filter. If running the check-app-filter command, the given path, content type or flatpak ref was allowed for the given user.

1

An invalid option was passed to malcontent-client on startup.

2

The current user was not authorized to query the app filter for the given user.

3

If running the check-app-filter command, the given path, content type or flatpak ref was not allowed for the given user.

4

Malcontent is disabled at the system level, and hence parental controls are not enabled or enforced.

5

An operation failed and no more specific error information is available.

6

The service was busy; try again shortly.

## BUGS
Any bugs which are found should be reported on the project website:

https://gitlab.freedesktop.org/pwithnall/malcontent/-/issues

## AUTHOR
Endless Mobile, Inc. Philip Withnall

## COPYRIGHT
Copyright © 2018 Endless Mobile, Inc. Copyright © 2025 GNOME Foundation, Inc.


accessdb

package: man-db

title: accessdb(8)

text:
# accessdb(8)

## NAME
accessdb - dumps the content of a man-db database in a human readable format

## SYNOPSIS
/usr/sbin/accessdb [-d?V] [<index-file>]

## DESCRIPTION
accessdb will output the data contained within a man-db database in a human readable form. By default, it will dump the data from /var/cache/man/index.<db-type>, where <db-type> is dependent on the database library in use.

Supplying an argument to accessdb will override this default.

## OPTIONS
-d, --debug

Print debugging information.

-?, --help

Print a help message and exit.

--usage

Print a short usage message and exit.

-V, --version

Display version information.

## AUTHOR

```
Wilf. (G.Wilford@ee.surrey.ac.uk).
Fabrizio Polacco (fpolacco@debian.org).
Colin Watson (cjwatson@debian.org).
```

## BUGS
https://gitlab.com/man-db/man-db/-/issues

https://savannah.nongnu.org/bugs/?group=man-db

branch: sisyphus


catman

title: catman(8)

text:
# catman(8)

## NAME
catman - create or update the pre-formatted manual pages

## SYNOPSIS
catman [-d?V] [-M path] [-C file] [section] ...

## DESCRIPTION
catman is used to create an up to date set of pre-formatted manual pages known as cat pages. Cat pages are generally much faster to display than the original manual pages, but require extra storage space. The decision to support cat pages is that of the local administrator, who must provide suitable directories to contain them.

The options available to catman are the manual page hierarchies and sections to pre-format. The default hierarchies are those specified as system hierarchies in the man-db configuration file, and the default sections are either the colon-delimited contents of the environment variable $MANSECT or the standard set compiled into man if $MANSECT is undefined. Supplying catman with a set of whitespace-delimited section names will override both of the above.

catman makes use of the index database cache associated with each hierarchy to determine which files need to be formatted.

## OPTIONS
-d, --debug

Print debugging information.

-M path, --manpath=path

Specify an alternate colon-delimited manual page hierarchy search path. By default, this is all paths indicated as system hierarchies in the man-db configuration file.

-C file, --config-file=file

Use this user configuration file rather than the default of ~/.manpath.

-?, --help

Print a help message and exit.

--usage

Print a short usage message and exit.

-V, --version

Display version information.

## ENVIRONMENT
MANSECT

If $MANSECT is set, its value is a colon-delimited list of sections and it is used to determine which manual sections to search and in what order. The default is "1 1p 8 2 3 3p 4 5 6 7 9 0p n l p o 1x 2x 3x 4x 5x 6x 7x 8x", unless overridden by the SECTION directive in /etc/man_db.conf.

MANPATH

If $MANPATH is set, its value is interpreted as the colon-delimited manual page hierarchy search path to use. See the SEARCH PATH section of manpath(5) for the default behaviour and details of how this environment variable is handled.

## FILES
/etc/man_db.conf

man-db configuration file.

/usr/man/index.(bt|db|dir|pag)

A traditional global index database cache.

/var/catman/index.(bt|db|dir|pag)

An alternate or FSSTND compliant global index database cache.

## SEE ALSO
man(1), manpath(5), mandb(8)

## AUTHOR

```
Wilf. (G.Wilford@ee.surrey.ac.uk).
Fabrizio Polacco (fpolacco@debian.org).
Colin Watson (cjwatson@debian.org).
```

## BUGS
https://gitlab.com/man-db/man-db/-/issues

https://savannah.nongnu.org/bugs/?group=man-db


mandb

title: mandb(8)

text:
# mandb(8)

## NAME
mandb - create or update the manual page index caches

## SYNOPSIS
mandb [-dqsucpt?V] [-C file] [manpath]

mandb [-dqsut] [-C file] -f filename ...

## DESCRIPTION
mandb is used to initialise or manually update index database caches. The caches contain information relevant to the current state of the manual page system and the information stored within them is used by the man-db utilities to enhance their speed and functionality.

When creating or updating an index, mandb will warn of bad ROFF .so requests, bogus manual page filenames and manual pages from which the whatis cannot be parsed.

Supplying mandb with an optional colon-delimited path will override the internal system manual page hierarchy search path, determined from information found within the man-db configuration file.

## DATABASE CACHES
mandb can be compiled with support for any one of the following database types.

Name

Async

Filename

Berkeley db

Yes

index.bt

GNU gdbm

Yes

index.db

UNIX ndbm

No

index.(dir|pag)

Those database types that support asynchronous updates provide enhanced speed at the cost of possible corruption in the event of unusual termination. In an unusual case where this has occurred, it may be necessary to rerun mandb with the -c option to re-create the databases from scratch.

## OPTIONS
-d, --debug

Print debugging information.

-q, --quiet

Produce no warnings.

-s, --no-straycats

Do not spend time looking for or adding information to the databases regarding stray cats.

-p, --no-purge

Do not spend time checking for deleted manual pages and purging them from the databases.

-c, --create

By default, mandb will try to update any previously created databases. If a database does not exist, it will create it. This option forces mandb to delete previous databases and re-create them from scratch, and implies --no-purge. This may be necessary if a database becomes corrupt or if a new database storage scheme is introduced in the future.

-u, --user-db

Create user databases only, even with write permissions necessary to create system databases.

-t, --test

Perform correctness checks on manual pages in the hierarchy search path. With this option, mandb will not alter existing databases.

-f, --filename

Update only the entries for the given filename. This option is not for general use; it is used internally by man when it has been compiled with the MAN_DB_UPDATES option and finds that a page is out of date. It implies -p and disables -c and -s.

-C file, --config-file=file

Use this user configuration file rather than the default of ~/.manpath.

-?, --help

Show the usage message, then exit.

--usage

Print a short usage message and exit.

-V, --version

Show the version, then exit.

## EXIT STATUS
0

Successful program execution.

1

Usage, syntax, or configuration file error.

2

Operational error.

3

A child process failed.

## DIAGNOSTICS
The following warning messages can be emitted during database building.

<filename>: whatis parse for page(sec) failed

An attempt to extract whatis line(s) from the given <filename> failed. This is usually due to a poorly written manual page, but if many such messages are emitted it is likely that the system contains non-standard manual pages which are incompatible with the man-db whatis parser. See the WHATIS PARSING section in lexgrog(1) for more information.

<filename>: is a dangling symlink

<filename> does not exist but is referenced by a symbolic link. Further diagnostics are usually emitted to identify the <filename> of the offending link.

<filename>: bad symlink or ROFF `.so' request

<filename> is either a symbolic link to, or contains a ROFF include request to, a non existent file.

<filename>: ignoring bogus filename

The <filename> may or may not be a valid manual page but its name is invalid. This is usually due to a manual page with sectional extension <x> being put in manual page section <y>.

<filename_mask>: competing extensions

The wildcard <filename_mask> is not unique. This is usually caused by the existence of both a compressed and uncompressed version of the same manual page. All but the most recent are ignored.

## FILES
/etc/man_db.conf

man-db configuration file.

/var/cache/man/index.(bt|db|dir|pag)

An FHS compliant global index database cache.

Older locations for the database cache included:

/usr/man/index.(bt|db|dir|pag)

A traditional global index database cache.

/var/catman/index.(bt|db|dir|pag)

An alternate or FSSTND compliant global index database cache.

## SEE ALSO
lexgrog(1), man(1), manpath(5), catman(8)

The WHATIS PARSING section formerly in this manual page is now part of lexgrog(1).

## AUTHOR

```
Wilf. (G.Wilford@ee.surrey.ac.uk).
Fabrizio Polacco (fpolacco@debian.org).
Colin Watson (cjwatson@debian.org).
```

## BUGS
https://gitlab.com/man-db/man-db/-/issues

https://savannah.nongnu.org/bugs/?group=man-db


iconvconfig

package: man-pages

title: iconvconfig(8)

summary: create iconv module configuration cache

text:
# iconvconfig(8)

## NAME
iconvconfig - create iconv module configuration cache

## SYNOPSIS
iconvconfig [options] [directory]...

## DESCRIPTION
The iconv(3) function internally uses gconv modules to convert to and from a character set. A configuration file is used to determine the needed modules for a conversion. Loading and parsing such a configuration file would slow down programs that use iconv(3), so a caching mechanism is employed.

The iconvconfig program reads iconv module configuration files and writes a fast-loading gconv module configuration cache file.

In addition to the system provided gconv modules, the user can specify custom gconv module directories with the environment variable GCONV_PATH. However, iconv module configuration caching is used only when the environment variable GCONV_PATH is not set.

## OPTIONS
--nostdlib

Do not search the system default gconv directory, only the directories provided on the command line.

-o outputfile, --output=outputfile

Use outputfile for output instead of the system default cache location.

--prefix=pathname

Set the prefix to be prepended to the system pathnames. See FILES, below. By default, the prefix is empty. Setting the prefix to foo, the gconv module configuration would be read from foo/usr/lib/gconv/gconv-modules and the cache would be written to foo/usr/lib/gconv/gconv-modules.cache.

-?, --help

Print a usage summary and exit.

--usage

Print a short usage summary and exit.

-V, --version

Print the version number, license, and disclaimer of warranty for iconv.

## EXIT STATUS
Zero on success, nonzero on errors.

## FILES
/usr/lib/gconv

Usual default gconv module path.

/usr/lib/gconv/gconv-modules

Usual system default gconv module configuration file.

/usr/lib/gconv/gconv-modules.cache

Usual system gconv module configuration cache.

Depending on the architecture, the above files may instead be located at directories with the path prefix /usr/lib64.

## SEE ALSO
iconv(1), iconv(3)


intro

title: intro(8)

text:
# intro(8)

## NAME
intro - introduction to administration and privileged commands

## DESCRIPTION
Section 8 of the manual describes commands which either can be or are used only by the superuser, like system-administration commands, daemons, and hardware-related commands.

As with the commands described in Section 1, the commands described in this section terminate with an exit status that indicates whether the command succeeded or failed. See intro(1) for more information.

## NOTES

### Authors and copyright conditions
Look at the header of the manual page source for the author(s) and copyright conditions. Note that these can be different from page to page!


ld.so

title: ld.so(8)

summary: dynamic linker/loader

text:
# ld.so(8)

## NAME
ld.so, ld-linux.so - dynamic linker/loader

## SYNOPSIS
The dynamic linker can be run either indirectly by running some dynamically linked program or shared object (in which case no command-line options to the dynamic linker can be passed and, in the ELF case, the dynamic linker which is stored in the .interp section of the program is executed) or directly by running:

/lib/ld-linux.so.* [OPTIONS] [PROGRAM [ARGUMENTS]]

## DESCRIPTION
The programs ld.so and ld-linux.so* find and load the shared objects (shared libraries) needed by a program, prepare the program to run, and then run it.

Linux binaries require dynamic linking (linking at run time) unless the -static option was given to ld(1) during compilation.

The program ld.so handles a.out binaries, a binary format used long ago. The program ld-linux.so* (/lib/ld-linux.so.1 for libc5, /lib/ld-linux.so.2 for glibc2) handles binaries that are in the more modern ELF format. Both programs have the same behavior, and use the same support files and programs (ldd(1), ldconfig(8), and /etc/ld.so.conf).

When resolving shared object dependencies, the dynamic linker first inspects each dependency string to see if it contains a slash (this can occur if a shared object pathname containing slashes was specified at link time). If a slash is found, then the dependency string is interpreted as a (relative or absolute) pathname, and the shared object is loaded using that pathname.

If a shared object dependency does not contain a slash, then it is searched for in the following order:

(1)

Using the directories specified in the DT_RPATH dynamic section attribute of the binary if present and DT_RUNPATH attribute does not exist. Use of DT_RPATH is deprecated.

(2)

Using the environment variable LD_LIBRARY_PATH, unless the executable is being run in secure-execution mode (see below), in which case this variable is ignored.

(3)

Using the directories specified in the DT_RUNPATH dynamic section attribute of the binary if present. Such directories are searched only to find those objects required by DT_NEEDED (direct dependencies) entries and do not apply to those objects' children, which must themselves have their own DT_RUNPATH entries. This is unlike DT_RPATH, which is applied to searches for all children in the dependency tree.

(4)

From the cache file /etc/ld.so.cache, which contains a compiled list of candidate shared objects previously found in the augmented library path. If, however, the binary was linked with the -z nodefaultlib linker option, shared objects in the default paths are skipped. Shared objects installed in hardware capability directories (see below) are preferred to other shared objects.

(5)

In the default path /lib, and then /usr/lib. (On some 64-bit architectures, the default paths for 64-bit shared objects are /lib64, and then /usr/lib64.) If the binary was linked with the -z nodefaultlib linker option, this step is skipped.

### Dynamic string tokens
In several places, the dynamic linker expands dynamic string tokens:

•

In the environment variables LD_LIBRARY_PATH, LD_PRELOAD, and LD_AUDIT,

•

inside the values of the dynamic section tags DT_NEEDED, DT_RPATH, DT_RUNPATH, DT_AUDIT, and DT_DEPAUDIT of ELF binaries,

•

in the arguments to the ld.so command line options --audit, --library-path, and --preload (see below), and

•

in the filename arguments to the dlopen(3) and dlmopen(3) functions.

The substituted tokens are as follows:

$ORIGIN (or equivalently ${ORIGIN})

This expands to the directory containing the program or shared object. Thus, an application located in somedir/app could be compiled with

```
gcc -Wl,-rpath,'$ORIGIN/../lib'

```

so that it finds an associated shared object in somedir/lib no matter where somedir is located in the directory hierarchy. This facilitates the creation of "turn-key" applications that do not need to be installed into special directories, but can instead be unpacked into any directory and still find their own shared objects.

$LIB (or equivalently ${LIB})

This expands to lib or lib64 depending on the architecture (e.g., on x86-64, it expands to lib64 and on x86-32, it expands to lib).

$PLATFORM (or equivalently ${PLATFORM})

This expands to a string corresponding to the processor type of the host system (e.g., "x86_64"). On some architectures, the Linux kernel doesn't provide a platform string to the dynamic linker. The value of this string is taken from the AT_PLATFORM value in the auxiliary vector (see getauxval(3)).

Note that the dynamic string tokens have to be quoted properly when set from a shell, to prevent their expansion as shell or environment variables.

## OPTIONS
--argv0 string (since glibc 2.33)

Set argv[0] to the value string before running the program.

--audit list

Use objects named in list as auditors. The objects in list are delimited by colons.

--inhibit-cache

Do not use /etc/ld.so.cache.

--library-path path

Use path instead of LD_LIBRARY_PATH environment variable setting (see below). The names ORIGIN, LIB, and PLATFORM are interpreted as for the LD_LIBRARY_PATH environment variable.

--inhibit-rpath list

Ignore RPATH and RUNPATH information in object names in list. This option is ignored when running in secure-execution mode (see below). The objects in list are delimited by colons or spaces.

--list

List all dependencies and how they are resolved.

--list-tunables (since glibc 2.33)

Print the names and values of all tunables, along with the minimum and maximum allowed values.

--preload list (since glibc 2.30)

Preload the objects specified in list. The objects in list are delimited by colons or spaces. The objects are preloaded as explained in the description of the LD_PRELOAD environment variable below.

By contrast with LD_PRELOAD, the --preload option provides a way to perform preloading for a single executable without affecting preloading performed in any child process that executes a new program.

--verify

Verify that program is dynamically linked and this dynamic linker can handle it.

## ENVIRONMENT
Various environment variables influence the operation of the dynamic linker.

### Secure-execution mode
For security reasons, if the dynamic linker determines that a binary should be run in secure-execution mode, the effects of some environment variables are voided or modified, and furthermore those environment variables are stripped from the environment, so that the program does not even see the definitions. Some of these environment variables affect the operation of the dynamic linker itself, and are described below. Other environment variables treated in this way include: GCONV_PATH, GETCONF_DIR, HOSTALIASES, LOCALDOMAIN, LOCPATH, MALLOC_TRACE, NIS_PATH, NLSPATH, RESOLV_HOST_CONF, RES_OPTIONS, TMPDIR, and TZDIR.

A binary is executed in secure-execution mode if the AT_SECURE entry in the auxiliary vector (see getauxval(3)) has a nonzero value. This entry may have a nonzero value for various reasons, including:

•

The process's real and effective user IDs differ, or the real and effective group IDs differ. This typically occurs as a result of executing a set-user-ID or set-group-ID program.

•

A process with a non-root user ID executed a binary that conferred capabilities to the process.

•

A nonzero value may have been set by a Linux Security Module.

### Environment variables
Among the more important environment variables are the following:

LD_ASSUME_KERNEL (since glibc 2.2.3)

Each shared object can inform the dynamic linker of the minimum kernel ABI version that it requires. (This requirement is encoded in an ELF note section that is viewable via readelf -n as a section labeled NT_GNU_ABI_TAG.) At run time, the dynamic linker determines the ABI version of the running kernel and will reject loading shared objects that specify minimum ABI versions that exceed that ABI version.

LD_ASSUME_KERNEL can be used to cause the dynamic linker to assume that it is running on a system with a different kernel ABI version. For example, the following command line causes the dynamic linker to assume it is running on Linux 2.2.5 when loading the shared objects required by myprog:

```
$ LD_ASSUME_KERNEL=2.2.5 ./myprog

```

On systems that provide multiple versions of a shared object (in different directories in the search path) that have different minimum kernel ABI version requirements, LD_ASSUME_KERNEL can be used to select the version of the object that is used (dependent on the directory search order).

Historically, the most common use of the LD_ASSUME_KERNEL feature was to manually select the older LinuxThreads POSIX threads implementation on systems that provided both LinuxThreads and NPTL (which latter was typically the default on such systems); see pthreads(7).

LD_BIND_NOW (since glibc 2.1.1)

If set to a nonempty string, causes the dynamic linker to resolve all symbols at program startup instead of deferring function call resolution to the point when they are first referenced. This is useful when using a debugger.

LD_LIBRARY_PATH

A list of directories in which to search for ELF libraries at execution time. The items in the list are separated by either colons or semicolons, and there is no support for escaping either separator. A zero-length directory name indicates the current working directory.

This variable is ignored in secure-execution mode.

Within the pathnames specified in LD_LIBRARY_PATH, the dynamic linker expands the tokens $ORIGIN, $LIB, and $PLATFORM (or the versions using curly braces around the names) as described above in Dynamic string tokens. Thus, for example, the following would cause a library to be searched for in either the lib or lib64 subdirectory below the directory containing the program to be executed:

```
$ LD_LIBRARY_PATH='$ORIGIN/$LIB' prog

```

(Note the use of single quotes, which prevent expansion of $ORIGIN and $LIB as shell variables!)

LD_PRELOAD

A list of additional, user-specified, ELF shared objects to be loaded before all others. This feature can be used to selectively override functions in other shared objects.

The items of the list can be separated by spaces or colons, and there is no support for escaping either separator. The objects are searched for using the rules given under DESCRIPTION. Objects are searched for and added to the link map in the left-to-right order specified in the list.

In secure-execution mode, preload pathnames containing slashes are ignored. Furthermore, shared objects are preloaded only from the standard search directories and only if they have set-user-ID mode bit enabled (which is not typical).

Within the names specified in the LD_PRELOAD list, the dynamic linker understands the tokens $ORIGIN, $LIB, and $PLATFORM (or the versions using curly braces around the names) as described above in Dynamic string tokens. (See also the discussion of quoting under the description of LD_LIBRARY_PATH.)

There are various methods of specifying libraries to be preloaded, and these are handled in the following order:

(1)

The LD_PRELOAD environment variable.

(2)

The --preload command-line option when invoking the dynamic linker directly.

(3)

The /etc/ld.so.preload file (described below).

LD_TRACE_LOADED_OBJECTS

If set (to any value), causes the program to list its dynamic dependencies, as if run by ldd(1), instead of running normally.

Then there are lots of more or less obscure variables, many obsolete or only for internal use.

LD_AUDIT (since glibc 2.4)

A list of user-specified, ELF shared objects to be loaded before all others in a separate linker namespace (i.e., one that does not intrude upon the normal symbol bindings that would occur in the process) These objects can be used to audit the operation of the dynamic linker. The items in the list are colon-separated, and there is no support for escaping the separator.

LD_AUDIT is ignored in secure-execution mode.

The dynamic linker will notify the audit shared objects at so-called auditing checkpoints—for example, loading a new shared object, resolving a symbol, or calling a symbol from another shared object—by calling an appropriate function within the audit shared object. For details, see rtld-audit(7). The auditing interface is largely compatible with that provided on Solaris, as described in its Linker and Libraries Guide, in the chapter Runtime Linker Auditing Interface.

Within the names specified in the LD_AUDIT list, the dynamic linker understands the tokens $ORIGIN, $LIB, and $PLATFORM (or the versions using curly braces around the names) as described above in Dynamic string tokens. (See also the discussion of quoting under the description of LD_LIBRARY_PATH.)

Since glibc 2.13, in secure-execution mode, names in the audit list that contain slashes are ignored, and only shared objects in the standard search directories that have the set-user-ID mode bit enabled are loaded.

LD_BIND_NOT (since glibc 2.1.95)

If this environment variable is set to a nonempty string, do not update the GOT (global offset table) and PLT (procedure linkage table) after resolving a function symbol. By combining the use of this variable with LD_DEBUG (with the categories bindings and symbols), one can observe all run-time function bindings.

LD_DEBUG (since glibc 2.1)

Output verbose debugging information about operation of the dynamic linker. The content of this variable is one of more of the following categories, separated by colons, commas, or (if the value is quoted) spaces:

help

Specifying help in the value of this variable does not run the specified program, and displays a help message about which categories can be specified in this environment variable.

all

Print all debugging information (except statistics and unused; see below).

bindings

Display information about which definition each symbol is bound to.

files

Display progress for input file.

libs

Display library search paths.

reloc

Display relocation processing.

scopes

Display scope information.

statistics

Display relocation statistics.

symbols

Display search paths for each symbol look-up.

unused

Determine unused DSOs.

versions

Display version dependencies.

Since glibc 2.3.4, LD_DEBUG is ignored in secure-execution mode, unless the file /etc/suid-debug exists (the content of the file is irrelevant).

LD_DEBUG_OUTPUT (since glibc 2.1)

By default, LD_DEBUG output is written to standard error. If LD_DEBUG_OUTPUT is defined, then output is written to the pathname specified by its value, with the suffix "." (dot) followed by the process ID appended to the pathname.

LD_DEBUG_OUTPUT is ignored in secure-execution mode.

LD_DYNAMIC_WEAK (since glibc 2.1.91)

By default, when searching shared libraries to resolve a symbol reference, the dynamic linker will resolve to the first definition it finds.

Old glibc versions (before glibc 2.2), provided a different behavior: if the linker found a symbol that was weak, it would remember that symbol and keep searching in the remaining shared libraries. If it subsequently found a strong definition of the same symbol, then it would instead use that definition. (If no further symbol was found, then the dynamic linker would use the weak symbol that it initially found.)

The old glibc behavior was nonstandard. (Standard practice is that the distinction between weak and strong symbols should have effect only at static link time.) In glibc 2.2, the dynamic linker was modified to provide the current behavior (which was the behavior that was provided by most other implementations at that time).

Defining the LD_DYNAMIC_WEAK environment variable (with any value) provides the old (nonstandard) glibc behavior, whereby a weak symbol in one shared library may be overridden by a strong symbol subsequently discovered in another shared library. (Note that even when this variable is set, a strong symbol in a shared library will not override a weak definition of the same symbol in the main program.)

Since glibc 2.3.4, LD_DYNAMIC_WEAK is ignored in secure-execution mode.

LD_HWCAP_MASK (since glibc 2.1)

Mask for hardware capabilities.

LD_ORIGIN_PATH (since glibc 2.1)

Path where the binary is found.

Since glibc 2.4, LD_ORIGIN_PATH is ignored in secure-execution mode.

LD_POINTER_GUARD (from glibc 2.4 to glibc 2.22)

Set to 0 to disable pointer guarding. Any other value enables pointer guarding, which is also the default. Pointer guarding is a security mechanism whereby some pointers to code stored in writable program memory (return addresses saved by setjmp(3) or function pointers used by various glibc internals) are mangled semi-randomly to make it more difficult for an attacker to hijack the pointers for use in the event of a buffer overrun or stack-smashing attack. Since glibc 2.23, LD_POINTER_GUARD can no longer be used to disable pointer guarding, which is now always enabled.

LD_PROFILE (since glibc 2.1)

The name of a (single) shared object to be profiled, specified either as a pathname or a soname. Profiling output is appended to the file whose name is: $LD_PROFILE_OUTPUT/$LD_PROFILE.profile.

Since glibc 2.2.5, LD_PROFILE is ignored in secure-execution mode.

LD_PROFILE_OUTPUT (since glibc 2.1)

Directory where LD_PROFILE output should be written. If this variable is not defined, or is defined as an empty string, then the default is /var/tmp.

LD_PROFILE_OUTPUT is ignored in secure-execution mode; instead /var/profile is always used. (This detail is relevant only before glibc 2.2.5, since in later glibc versions, LD_PROFILE is also ignored in secure-execution mode.)

LD_SHOW_AUXV (since glibc 2.1)

If this environment variable is defined (with any value), show the auxiliary array passed up from the kernel (see also getauxval(3)).

Since glibc 2.3.4, LD_SHOW_AUXV is ignored in secure-execution mode.

LD_TRACE_PRELINKING (since glibc 2.4)

If this environment variable is defined, trace prelinking of the object whose name is assigned to this environment variable. (Use ldd(1) to get a list of the objects that might be traced.) If the object name is not recognized, then all prelinking activity is traced.

LD_USE_LOAD_BIAS (since glibc 2.3.3)

By default (i.e., if this variable is not defined), executables and prelinked shared objects will honor base addresses of their dependent shared objects and (nonprelinked) position-independent executables (PIEs) and other shared objects will not honor them. If LD_USE_LOAD_BIAS is defined with the value 1, both executables and PIEs will honor the base addresses. If LD_USE_LOAD_BIAS is defined with the value 0, neither executables nor PIEs will honor the base addresses.

Since glibc 2.3.3, this variable is ignored in secure-execution mode.

LD_VERBOSE (since glibc 2.1)

If set to a nonempty string, output symbol versioning information about the program if the LD_TRACE_LOADED_OBJECTS environment variable has been set.

LD_WARN (since glibc 2.1.3)

If set to a nonempty string, warn about unresolved symbols.

LD_PREFER_MAP_32BIT_EXEC (x86-64 only; since glibc 2.23)

According to the Intel Silvermont software optimization guide, for 64-bit applications, branch prediction performance can be negatively impacted when the target of a branch is more than 4 GB away from the branch. If this environment variable is set (to any value), the dynamic linker will first try to map executable pages using the mmap(2) MAP_32BIT flag, and fall back to mapping without that flag if that attempt fails. NB: MAP_32BIT will map to the low 2 GB (not 4 GB) of the address space.

Because MAP_32BIT reduces the address range available for address space layout randomization (ASLR), LD_PREFER_MAP_32BIT_EXEC is always disabled in secure-execution mode.

## FILES
/lib/ld.so

a.out dynamic linker/loader

/lib/ld-linux.so.{1,2}

ELF dynamic linker/loader

/etc/ld.so.cache

File containing a compiled list of directories in which to search for shared objects and an ordered list of candidate shared objects. See ldconfig(8).

/etc/ld.so.preload

File containing a whitespace-separated list of ELF shared objects to be loaded before the program. See the discussion of LD_PRELOAD above. If both LD_PRELOAD and /etc/ld.so.preload are employed, the libraries specified by LD_PRELOAD are preloaded first. /etc/ld.so.preload has a system-wide effect, causing the specified libraries to be preloaded for all programs that are executed on the system. (This is usually undesirable, and is typically employed only as an emergency remedy, for example, as a temporary workaround to a library misconfiguration issue.)

lib*.so*

shared objects

## NOTES

### Hardware capabilities
Some shared objects are compiled using hardware-specific instructions which do not exist on every CPU. Such objects should be installed in directories whose names define the required hardware capabilities, such as /usr/lib/sse2/. The dynamic linker checks these directories against the hardware of the machine and selects the most suitable version of a given shared object. Hardware capability directories can be cascaded to combine CPU features. The list of supported hardware capability names depends on the CPU. The following names are currently recognized:

Alpha

ev4, ev5, ev56, ev6, ev67

MIPS

loongson2e, loongson2f, octeon, octeon2

PowerPC

4xxmac, altivec, arch_2_05, arch_2_06, booke, cellbe, dfp, efpdouble, efpsingle, fpu, ic_snoop, mmu, notb, pa6t, power4, power5, power5+, power6x, ppc32, ppc601, ppc64, smt, spe, ucache, vsx

SPARC

flush, muldiv, stbar, swap, ultra3, v9, v9v, v9v2

s390

dfp, eimm, esan3, etf3enh, g5, highgprs, hpage, ldisp, msa, stfle, z900, z990, z9-109, z10, zarch

x86 (32-bit only)

acpi, apic, clflush, cmov, cx8, dts, fxsr, ht, i386, i486, i586, i686, mca, mmx, mtrr, pat, pbe, pge, pn, pse36, sep, ss, sse, sse2, tm

## SEE ALSO
ld(1), ldd(1), pldd(1), sprof(1), dlopen(3), getauxval(3), elf(5), capabilities(7), rtld-audit(7), ldconfig(8), sln(8)


ldconfig

title: ldconfig(8)

text:
# ldconfig(8)

## NAME
ldconfig - configure dynamic linker run-time bindings

## SYNOPSIS
/sbin/ldconfig

[-nNvVX] [-C cache] [-f conf] [-r root] directory ...

/sbin/ldconfig

-l [-v] library ...

/sbin/ldconfig

-p

## DESCRIPTION
ldconfig creates the necessary links and cache to the most recent shared libraries found in the directories specified on the command line, in the file /etc/ld.so.conf, and in the trusted directories, /lib and /usr/lib. On some 64-bit architectures such as x86-64, /lib and /usr/lib are the trusted directories for 32-bit libraries, while /lib64 and /usr/lib64 are used for 64-bit libraries.

The cache is used by the run-time linker, ld.so or ld-linux.so. ldconfig checks the header and filenames of the libraries it encounters when determining which versions should have their links updated. ldconfig should normally be run by the superuser as it may require write permission on some root owned directories and files.

ldconfig will look only at files that are named lib*.so* (for regular shared objects) or ld-*.so* (for the dynamic loader itself). Other files will be ignored. Also, ldconfig expects a certain pattern to how the symbolic links are set up, like this example, where the middle file (libfoo.so.1 here) is the SONAME for the library:

```
libfoo.so -> libfoo.so.1 -> libfoo.so.1.12
```

Failure to follow this pattern may result in compatibility issues after an upgrade.

## OPTIONS
-c fmt

--format=fmt

(Since glibc 2.2) Use cache format fmt, which is one of old, new, or compat. Since glibc 2.32, the default is new. Before that, it was compat.

-C cache

Use cache instead of /etc/ld.so.cache.

-f conf

Use conf instead of /etc/ld.so.conf.

-i

--ignore-aux-cache

(Since glibc 2.7) Ignore auxiliary cache file.

-l

(Since glibc 2.2) Interpret each operand as a library name and configure its links. Intended for use only by experts.

-n

Process only the directories specified on the command line; don't process the trusted directories, nor those specified in /etc/ld.so.conf. Implies -N.

-N

Don't rebuild the cache. Unless -X is also specified, links are still updated.

-p

--print-cache

Print the lists of directories and candidate libraries stored in the current cache.

-r root

Change to and use root as the root directory.

-v

--verbose

Verbose mode. Print current version number, the name of each directory as it is scanned, and any links that are created. Overrides quiet mode.

-V

--version

Print program version.

-X

Don't update links. Unless -N is also specified, the cache is still rebuilt.

## FILES
/lib/ld.so

is the run-time linker/loader.

/etc/ld.so.conf

contains a list of directories, one per line, in which to search for libraries.

/etc/ld.so.cache

contains an ordered list of libraries found in the directories specified in /etc/ld.so.conf, as well as those found in the trusted directories.

## SEE ALSO
ldd(1), ld.so(8)


nscd

title: nscd(8)

summary: name service cache daemon

text:
# nscd(8)

## NAME
nscd - name service cache daemon

## DESCRIPTION
nscd is a daemon that provides a cache for the most common name service requests. The default configuration file, /etc/nscd.conf, determines the behavior of the cache daemon. See nscd.conf(5).

nscd provides caching for accesses of the passwd(5), group(5), hosts(5) services(5) and netgroup databases through standard libc interfaces, such as getpwnam(3), getpwuid(3), getgrnam(3), getgrgid(3), gethostbyname(3), and others.

There are two caches for each database: a positive one for items found, and a negative one for items not found. Each cache has a separate TTL (time-to-live) period for its data. Note that the shadow file is specifically not cached. getspnam(3) calls remain uncached as a result.

## OPTIONS
--help

will give you a list with all options and what they do.

## NOTES
The daemon will try to watch for changes in configuration files appropriate for each database (e.g., /etc/passwd for the passwd database or /etc/hosts and /etc/resolv.conf for the hosts database), and flush the cache when these are changed. However, this will happen only after a short delay (unless the inotify(7) mechanism is available and glibc 2.9 or later is available), and this auto-detection does not cover configuration files required by nonstandard NSS modules, if any are specified in /etc/nsswitch.conf. In that case, you need to run the following command after changing the configuration file of the database so that nscd invalidates its cache:

```
$ nscd -i <database>
```

## SEE ALSO
nscd.conf(5), nsswitch.conf(5)


sln

title: sln(8)

summary: create symbolic links

text:
# sln(8)

## NAME
sln - create symbolic links

## SYNOPSIS

```
sln source dest
sln filelist
```

## DESCRIPTION
The sln program creates symbolic links. Unlike the ln(1) program, it is statically linked. This means that if for some reason the dynamic linker is not working, sln can be used to make symbolic links to dynamic libraries.

The command line has two forms. In the first form, it creates dest as a new symbolic link to source.

In the second form, filelist is a list of space-separated pathname pairs, and the effect is as if sln was executed once for each line of the file, with the two pathnames as the arguments.

The sln program supports no command-line options.

## SEE ALSO
ln(1), ld.so(8), ldconfig(8)


tzselect

title: tzselect(8)

summary: select a timezone

text:
# tzselect(8)

## NAME
tzselect - select a timezone

## SYNOPSIS
tzselect [ -c coord ] [ -n limit ] [ --help ] [ --version ]

## DESCRIPTION
The tzselect program asks the user for information about the current location, and outputs the resulting timezone to standard output. The output is suitable as a value for the TZ environment variable.

All interaction with the user is done via standard input and standard error.

## OPTIONS
-c coord

Instead of asking for continent and then country and then city, ask for selection from time zones whose largest cities are closest to the location with geographical coordinates coord. Use ISO 6709 notation for coord, that is, a latitude immediately followed by a longitude. The latitude and longitude should be signed integers followed by an optional decimal point and fraction: positive numbers represent north and east, negative south and west. Latitudes with two and longitudes with three integer digits are treated as degrees; latitudes with four or six and longitudes with five or seven integer digits are treated as DDMM, DDDMM, DDMMSS, or DDDMMSS representing DD or DDD degrees, MM minutes, and zero or SS seconds, with any trailing fractions represent fractional minutes or (if SS is present) seconds. The decimal point is that of the current locale. For example, in the (default) C locale, -c +40.689-074.045 specifies 40.689 degrees N, 74.045 degrees W, -c +4041.4-07402.7 specifies 40 degrees 41.4 minutes N, 74 degrees 2.7 minutes W, and -c +404121-0740240 specifies 40 degrees 41 minutes 21 seconds N, 74 degrees 2 minutes 40 seconds W. If coord is not one of the documented forms, the resulting behavior is unspecified.

-n limit

When -c is used, display the closest limit locations (default 10).

--help

Output help information and exit.

--version

Output version information and exit.

## ENVIRONMENT VARIABLES
AWK

Name of a Posix-compliant awk program (default: awk).

TZDIR

Name of the directory containing timezone data files (default: /usr/share/zoneinfo).

## FILES
TZDIR/iso3166.tab

Table of ISO 3166 2-letter country codes and country names.

TZDIR/zone1970.tab

Table of country codes, latitude and longitude, timezones, and descriptive comments.

TZDIR/TZ

Timezone data file for timezone TZ.

## EXIT STATUS
The exit status is zero if a timezone was successfully obtained from the user, nonzero otherwise.

## SEE ALSO
newctime(3), tzfile(5), zdump(8), zic(8)

## NOTES
Applications should not assume that tzselect's output matches the user's political preferences.


zdump

title: zdump(8)

summary: timezone dumper

text:
# zdump(8)

## NAME
zdump - timezone dumper

## SYNOPSIS
zdump [ option ... ] [ timezone ... ]

## DESCRIPTION
The zdump program prints the current time in each timezone named on the command line.

## OPTIONS
--version

Output version information and exit.

--help

Output short usage message and exit.

-i

Output a description of time intervals. For each timezone on the command line, output an interval-format description of the timezone. See “INTERVAL FORMAT” below.

-v

Output a verbose description of time intervals. For each timezone on the command line, print the times at the two extreme time values, the times (if present) at and just beyond the boundaries of years that localtime(3) and gmtime(3) can represent, and the times both one second before and exactly at each detected time discontinuity. Each line is followed by isdst=D where D is positive, zero, or negative depending on whether the given time is daylight saving time, standard time, or an unknown time type, respectively. Each line is also followed by gmtoff=N if the given local time is known to be N seconds east of Greenwich.

-V

Like -v, except omit output concerning extreme time and year values. This generates output that is easier to compare to that of implementations with different time representations.

-c [loyear,]hiyear

Cut off interval output at the given year(s). Cutoff times are computed using the proleptic Gregorian calendar with year 0 and with Universal Time (UT) ignoring leap seconds. Cutoffs are at the start of each year, where the lower-bound timestamp is inclusive and the upper is exclusive; for example, -c 1970,2070 selects transitions on or after 1970-01-01 00:00:00 UTC and before 2070-01-01 00:00:00 UTC. The default cutoff is -500,2500.

-t [lotime,]hitime

Cut off interval output at the given time(s), given in decimal seconds since 1970-01-01 00:00:00 Coordinated Universal Time (UTC). The timezone determines whether the count includes leap seconds. As with -c, the cutoff's lower bound is inclusive and its upper bound is exclusive.

## INTERVAL FORMAT
The interval format is a compact text representation that is intended to be both human- and machine-readable. It consists of an empty line, then a line “TZ=string” where string is a double-quoted string giving the timezone, a second line “- - interval” describing the time interval before the first transition if any, and zero or more following lines “date time interval”, one line for each transition time and following interval. Fields are separated by single tabs.

Dates are in yyyy-mm-dd format and times are in 24-hour hh:mm:ss format where hh<24. Times are in local time immediately after the transition. A time interval description consists of a UT offset in signed ±hhmmss format, a time zone abbreviation, and an isdst flag. An abbreviation that equals the UT offset is omitted; other abbreviations are double-quoted strings unless they consist of one or more alphabetic characters. An isdst flag is omitted for standard time, and otherwise is a decimal integer that is unsigned and positive (typically 1) for daylight saving time and negative for unknown.

In times and in UT offsets with absolute value less than 100 hours, the seconds are omitted if they are zero, and the minutes are also omitted if they are also zero. Positive UT offsets are east of Greenwich. The UT offset -00 denotes a UT placeholder in areas where the actual offset is unspecified; by convention, this occurs when the UT offset is zero and the time zone abbreviation begins with “-” or is “zzz”.

In double-quoted strings, escape sequences represent unusual characters. The escape sequences are \s for space, and \", \\, \f, \n, \r, \t, and \v with their usual meaning in the C programming language. E.g., the double-quoted string “"CET\s\"\\"” represents the character sequence “CET "\”.

Here is an example of the output, with the leading empty line omitted. (This example is shown with tab stops set far enough apart so that the tabbed columns line up.)

```
TZ="Pacific/Honolulu"
-	-	-103126	LMT
1896-01-13	12:01:26	-1030	HST
1933-04-30	03	-0930	HDT	1
1933-05-21	11	-1030	HST
1942-02-09	03	-0930	HWT	1
1945-08-14	13:30	-0930	HPT	1
1945-09-30	01	-1030	HST
1947-06-08	02:30	-10	HST
```

Here, local time begins 10 hours, 31 minutes and 26 seconds west of UT, and is a standard time abbreviated LMT. Immediately after the first transition, the date is 1896-01-13 and the time is 12:01:26, and the following time interval is 10.5 hours west of UT, a standard time abbreviated HST. Immediately after the second transition, the date is 1933-04-30 and the time is 03:00:00 and the following time interval is 9.5 hours west of UT, is abbreviated HDT, and is daylight saving time. Immediately after the last transition the date is 1947-06-08 and the time is 02:30:00, and the following time interval is 10 hours west of UT, a standard time abbreviated HST. Here are excerpts from another example:

```
TZ="Europe/Astrakhan"
-	-	+031212	LMT
1924-04-30	23:47:48	+03
1930-06-21	01	+04
1981-04-01	01	+05		1
1981-09-30	23	+04
...
2014-10-26	01	+03
2016-03-27	03	+04
```

This time zone is east of UT, so its UT offsets are positive. Also, many of its time zone abbreviations are omitted since they duplicate the text of the UT offset.

## LIMITATIONS
Time discontinuities are found by sampling the results returned by localtime(3) at twelve-hour intervals. This works in all real-world cases; one can construct artificial time zones for which this fails.

In the -v and -V output, “UT” denotes the value returned by gmtime(3), which uses UTC for modern timestamps and some other UT flavor for timestamps that predate the introduction of UTC. No attempt is currently made to have the output use “UTC” for newer and “UT” for older timestamps, partly because the exact date of the introduction of UTC is problematic.

## SEE ALSO
tzfile(5), zic(8)


zic

title: zic(8)

summary: timezone compiler

text:
# zic(8)

## NAME
zic - timezone compiler

## SYNOPSIS
zic [ option ... ] [ filename ... ]

## DESCRIPTION
The zic program reads text from the file(s) named on the command line and creates the timezone information format (TZif) files specified in this input. If a filename is “-”, standard input is read.

## OPTIONS
--version

Output version information and exit.

--help

Output short usage message and exit.

-b bloat

Output backward-compatibility data as specified by bloat. If bloat is fat, generate additional data entries that work around potential bugs or incompatibilities in older software, such as software that mishandles the 64-bit generated data. If bloat is slim, keep the output files small; this can help check for the bugs and incompatibilities. The default is slim, as software that mishandles 64-bit data typically mishandles timestamps after the year 2038 anyway. Also see the -r option for another way to alter output size.

-d directory

Create time conversion information files in the named directory rather than in the standard directory named below.

-l timezone

Use timezone as local time. zic will act as if the input contained a link line of the form Link timezone localtime

If timezone is -, any already-existing link is removed.

-L leapsecondfilename

Read leap second information from the file with the given name. If this option is not used, no leap second information appears in output files.

-p timezone

Use timezone's rules when handling nonstandard TZ strings like "EET-2EEST" that lack transition rules. zic will act as if the input contained a link line of the form Link timezone posixrules

Unless timezone is “-”, this option is obsolete and poorly supported. Among other things it should not be used for timestamps after the year 2037, and it should not be combined with -b slim if timezone's transitions are at standard time or Universal Time (UT) instead of local time.

If timezone is -, any already-existing link is removed.

-r [@lo][/@hi]

Limit the applicability of output files to timestamps in the range from lo (inclusive) to hi (exclusive), where lo and hi are possibly signed decimal counts of seconds since the Epoch (1970-01-01 00:00:00 UTC). Omitted counts default to extreme values. The output files use UT offset 0 and abbreviation “-00” in place of the omitted timestamp data. For example, “zic -r @0” omits data intended for negative timestamps (i.e., before the Epoch), and “zic -r @0/@2147483648” outputs data intended only for nonnegative timestamps that fit into 31-bit signed integers. On platforms with GNU date, “zic -r @$(date +%s)” omits data intended for past timestamps. Although this option typically reduces the output file's size, the size can increase due to the need to represent the timestamp range boundaries, particularly if hi causes a TZif file to contain explicit entries for pre-hi transitions rather than concisely representing them with an extended POSIX TZ string. Also see the -b slim option for another way to shrink output size.

-R @hi

Generate redundant trailing explicit transitions for timestamps that occur less than hi seconds since the Epoch, even though the transitions could be more concisely represented via the extended POSIX TZ string. This option does not affect the represented timestamps. Although it accommodates nonstandard TZif readers that ignore the extended POSIX TZ string, it increases the size of the altered output files.

-t file

When creating local time information, put the configuration link in the named file rather than in the standard location.

-v

Be more verbose, and complain about the following situations:

The input specifies a link to a link, something not supported by some older parsers, including zic itself through release 2022e.

A year that appears in a data file is outside the range of representable years.

A time of 24:00 or more appears in the input. Pre-1998 versions of zic prohibit 24:00, and pre-2007 versions prohibit times greater than 24:00.

A rule goes past the start or end of the month. Pre-2004 versions of zic prohibit this.

A time zone abbreviation uses a %z format. Pre-2015 versions of zic do not support this.

A timestamp contains fractional seconds. Pre-2018 versions of zic do not support this.

The input contains abbreviations that are mishandled by pre-2018 versions of zic due to a longstanding coding bug. These abbreviations include “L” for “Link”, “mi” for “min”, “Sa” for “Sat”, and “Su” for “Sun”.

The output file does not contain all the information about the long-term future of a timezone, because the future cannot be summarized as an extended POSIX TZ string. For example, as of 2023 this problem occurs for Morocco's daylight-saving rules, as these rules are based on predictions for when Ramadan will be observed, something that an extended POSIX TZ string cannot represent.

The output contains data that may not be handled properly by client code designed for older zic output formats. These compatibility issues affect only timestamps before 1970 or after the start of 2038.

The output contains a truncated leap second table, which can cause some older TZif readers to misbehave. This can occur if the -L option is used, and either an Expires line is present or the -r option is also used.

The output file contains more than 1200 transitions, which may be mishandled by some clients. The current reference client supports at most 2000 transitions; pre-2014 versions of the reference client support at most 1200 transitions.

A time zone abbreviation has fewer than 3 or more than 6 characters. POSIX requires at least 3, and requires implementations to support at least 6.

An output file name contains a byte that is not an ASCII letter, “-”, “/”, or “_”; or it contains a file name component that contains more than 14 bytes or that starts with “-”.

## FILES
Input files use the format described in this section; output files use tzfile(5) format.

Input files should be text files, that is, they should be a series of zero or more lines, each ending in a newline byte and containing at most 2048 bytes counting the newline, and without any NUL bytes. The input text's encoding is typically UTF-8 or ASCII; it should have a unibyte representation for the POSIX Portable Character Set (PPCS) ⟨https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap06.html⟩ and the encoding's non-unibyte characters should consist entirely of non-PPCS bytes. Non-PPCS characters typically occur only in comments: although output file names and time zone abbreviations can contain nearly any character, other software will work better if these are limited to the restricted syntax described under the -v option.

Input lines are made up of fields. Fields are separated from one another by one or more white space characters. The white space characters are space, form feed, carriage return, newline, tab, and vertical tab. Leading and trailing white space on input lines is ignored. An unquoted sharp character (#) in the input introduces a comment which extends to the end of the line the sharp character appears on. White space characters and sharp characters may be enclosed in double quotes (") if they're to be used as part of a field. Any line that is blank (after comment stripping) is ignored. Nonblank lines are expected to be of one of three types: rule lines, zone lines, and link lines.

Names must be in English and are case insensitive. They appear in several contexts, and include month and weekday names and keywords such as maximum, only, Rolling, and Zone. A name can be abbreviated by omitting all but an initial prefix; any abbreviation must be unambiguous in context.

A rule line has the form

```
Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S

For example:

Rule	US	1967	1973	-	Apr	lastSun	2:00w	1:00d	D
```

The fields that make up a rule line are: NAME

Gives the name of the rule set that contains this line. The name must start with a character that is neither an ASCII digit nor “-” nor “+”. To allow for future extensions, an unquoted name should not contain characters from the set “!$%&'()*,/:;<=>?@[\]^`{|}~”. “!$%&'()*,/:;<=>?@[\]^`{|}~”.

FROM

Gives the first year in which the rule applies. Any signed integer year can be supplied; the proleptic Gregorian calendar is assumed, with year 0 preceding year 1. The word minimum (or an abbreviation) means the indefinite past. The word maximum (or an abbreviation) means the indefinite future. Rules can describe times that are not representable as time values, with the unrepresentable times ignored; this allows rules to be portable among hosts with differing time value types.

TO

Gives the final year in which the rule applies. In addition to minimum and maximum (as above), the word only (or an abbreviation) may be used to repeat the value of the FROM field.

-

Is a reserved field and should always contain “-” for compatibility with older versions of zic. It was previously known as the TYPE field, which could contain values to allow a separate script to further restrict in which “types” of years the rule would apply.

IN

Names the month in which the rule takes effect. Month names may be abbreviated.

ON

Gives the day on which the rule takes effect. Recognized forms include:

```
5	the fifth of the month
lastSun	the last Sunday in the month
lastMon	the last Monday in the month
Sun>=8	first Sunday on or after the eighth
Sun<=25	last Sunday on or before the 25th
```

A weekday name (e.g., Sunday) or a weekday name preceded by “last” (e.g., lastSunday) may be abbreviated or spelled out in full. There must be no white space characters within the ON field. The “<=” and “>=” constructs can result in a day in the neighboring month; for example, the IN-ON combination “Oct Sun>=31” stands for the first Sunday on or after October 31, even if that Sunday occurs in November.

AT

Gives the time of day at which the rule takes effect, relative to 00:00, the start of a calendar day. Recognized forms include:

```
2	time in hours
2:00	time in hours and minutes
01:28:14	time in hours, minutes, and seconds
00:19:32.13	time with fractional seconds
12:00	midday, 12 hours after 00:00
15:00	3 PM, 15 hours after 00:00
24:00	end of day, 24 hours after 00:00
260:00	260 hours after 00:00
-2:30	2.5 hours before 00:00
-	equivalent to 0
```

Although zic rounds times to the nearest integer second (breaking ties to the even integer), the fractions may be useful to other applications requiring greater precision. The source format does not specify any maximum precision. Any of these forms may be followed by the letter w if the given time is local or “wall clock” time, s if the given time is standard time without any adjustment for daylight saving, or u (or g or z) if the given time is universal time; in the absence of an indicator, local (wall clock) time is assumed. These forms ignore leap seconds; for example, if a leap second occurs at 00:59:60 local time, “1:00” stands for 3601 seconds after local midnight instead of the usual 3600 seconds. The intent is that a rule line describes the instants when a clock/calendar set to the type of time specified in the AT field would show the specified date and time of day.

SAVE

Gives the amount of time to be added to local standard time when the rule is in effect, and whether the resulting time is standard or daylight saving. This field has the same format as the AT field except with a different set of suffix letters: s for standard time and d for daylight saving time. The suffix letter is typically omitted, and defaults to s if the offset is zero and to d otherwise. Negative offsets are allowed; in Ireland, for example, daylight saving time is observed in winter and has a negative offset relative to Irish Standard Time. The offset is merely added to standard time; for example, zic does not distinguish a 10:30 standard time plus an 0:30 SAVE from a 10:00 standard time plus a 1:00 SAVE.

LETTER/S

Gives the “variable part” (for example, the “S” or “D” in “EST” or “EDT”) of time zone abbreviations to be used when this rule is in effect. If this field is “-”, the variable part is null.

A zone line has the form

```
Zone	NAME	STDOFF	RULES	FORMAT	[UNTIL]

For example:

Zone	Asia/Amman	2:00	Jordan	EE%sT	2017 Oct 27 01:00
```

The fields that make up a zone line are: NAME

The name of the timezone. This is the name used in creating the time conversion information file for the timezone. It should not contain a file name component “.” or “..”; a file name component is a maximal substring that does not contain “/”.

STDOFF

The amount of time to add to UT to get standard time, without any adjustment for daylight saving. This field has the same format as the AT and SAVE fields of rule lines, except without suffix letters; begin the field with a minus sign if time must be subtracted from UT.

RULES

The name of the rules that apply in the timezone or, alternatively, a field in the same format as a rule-line SAVE column, giving the amount of time to be added to local standard time and whether the resulting time is standard or daylight saving. If this field is - then standard time always applies. When an amount of time is given, only the sum of standard time and this amount matters.

FORMAT

The format for time zone abbreviations. The pair of characters %s is used to show where the “variable part” of the time zone abbreviation goes. Alternatively, a format can use the pair of characters %z to stand for the UT offset in the form ±hh, ±hhmm, or ±hhmmss, using the shortest form that does not lose information, where hh, mm, and ss are the hours, minutes, and seconds east (+) or west (-) of UT. Alternatively, a slash (/) separates standard and daylight abbreviations. To conform to POSIX, a time zone abbreviation should contain only alphanumeric ASCII characters, “+” and “-”. By convention, the time zone abbreviation “-00” is a placeholder that means local time is unspecified.

UNTIL

The time at which the UT offset or the rule(s) change for a location. It takes the form of one to four fields YEAR [MONTH [DAY [TIME]]]. If this is specified, the time zone information is generated from the given UT offset and rule change until the time specified, which is interpreted using the rules in effect just before the transition. The month, day, and time of day have the same format as the IN, ON, and AT fields of a rule; trailing fields can be omitted, and default to the earliest possible value for the missing fields.

The next line must be a “continuation” line; this has the same form as a zone line except that the string “Zone” and the name are omitted, as the continuation line will place information starting at the time specified as the “until” information in the previous line in the file used by the previous line. Continuation lines may contain “until” information, just as zone lines do, indicating that the next line is a further continuation.

If a zone changes at the same instant that a rule would otherwise take effect in the earlier zone or continuation line, the rule is ignored. A zone or continuation line L with a named rule set starts with standard time by default: that is, any of L's timestamps preceding L's earliest rule use the rule in effect after L's first transition into standard time. In a single zone it is an error if two rules take effect at the same instant, or if two zone changes take effect at the same instant.

If a continuation line subtracts N seconds from the UT offset after a transition that would be interpreted to be later if using the continuation line's UT offset and rules, the “until” time of the previous zone or continuation line is interpreted according to the continuation line's UT offset and rules, and any rule that would otherwise take effect in the next N seconds is instead assumed to take effect simultaneously. For example:

```
# Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
Rule	US	1967	2006	-	Oct	lastSun	2:00	0	S
Rule	US	1967	1973	-	Apr	lastSun	2:00	1:00	D
# Zone  NAME	STDOFF	RULES	FORMAT	[UNTIL]
Zone  America/Menominee	-5:00	-	EST	1973 Apr 29 2:00
	-6:00	US	C%sT
```

Here, an incorrect reading would be there were two clock changes on 1973-04-29, the first from 02:00 EST (-05) to 01:00 CST (-06), and the second an hour later from 02:00 CST (-06) to 03:00 CDT (-05). However, zic interprets this more sensibly as a single transition from 02:00 CST (-05) to 02:00 CDT (-05). A link line has the form

```
Link	TARGET	LINK-NAME

For example:

Link	Europe/Istanbul	Asia/Istanbul
```

The TARGET field should appear as the NAME field in some zone line or as the LINK-NAME field in some link line. The LINK-NAME field is used as an alternative name for that zone; it has the same syntax as a zone line's NAME field. Links can chain together, although the behavior is unspecified if a chain of one or more links does not terminate in a Zone name. A link line can appear before the line that defines the link target. For example:

```
Link	Greenwich	G_M_T
Link	Etc/GMT	Greenwich
Zone	Etc/GMT  0  -  GMT
```

The two links are chained together, and G_M_T, Greenwich, and Etc/GMT all name the same zone. Except for continuation lines, lines may appear in any order in the input. However, the behavior is unspecified if multiple zone or link lines define the same name.

The file that describes leap seconds can have leap lines and an expiration line. Leap lines have the following form:

```
Leap	YEAR	MONTH	DAY	HH:MM:SS	CORR	R/S

For example:

Leap	2016	Dec	31	23:59:60	+	S
```

The YEAR, MONTH, DAY, and HH:MM:SS fields tell when the leap second happened. The CORR field should be “+” if a second was added or “-” if a second was skipped. The R/S field should be (an abbreviation of) “Stationary” if the leap second time given by the other fields should be interpreted as UTC or (an abbreviation of) “Rolling” if the leap second time given by the other fields should be interpreted as local (wall clock) time. Rolling leap seconds were implemented back when it was not clear whether common practice was rolling or stationary, with concerns that one would see Times Square ball drops where there'd be a “3... 2... 1... leap... Happy New Year” countdown, placing the leap second at midnight New York time rather than midnight UTC. However, this countdown style does not seem to have caught on, which means rolling leap seconds are not used in practice; also, they are not supported if the -r option is used.

The expiration line, if present, has the form:

```
Expires	YEAR	MONTH	DAY	HH:MM:SS

For example:

Expires	2020	Dec	28	00:00:00
```

The YEAR, MONTH, DAY, and HH:MM:SS fields give the expiration timestamp in UTC for the leap second table.

## EXTENDED EXAMPLE
Here is an extended example of zic input, intended to illustrate many of its features.

```
# Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
Rule	Swiss	1941	1942	-	May	Mon>=1	1:00	1:00	S
Rule	Swiss	1941	1942	-	Oct	Mon>=1	2:00	0	-

Rule	EU	1977	1980	-	Apr	Sun>=1	1:00u	1:00	S
Rule	EU	1977	only	-	Sep	lastSun	1:00u	0	-
Rule	EU	1978	only	-	Oct	 1	1:00u	0	-
Rule	EU	1979	1995	-	Sep	lastSun	1:00u	0	-
Rule	EU	1981	max	-	Mar	lastSun	1:00u	1:00	S
Rule	EU	1996	max	-	Oct	lastSun	1:00u	0	-

# Zone	NAME	STDOFF	RULES	FORMAT	[UNTIL]
Zone	Europe/Zurich	0:34:08	-	LMT	1853 Jul 16
		0:29:45.50	-	BMT	1894 Jun
		1:00	Swiss	CE%sT	1981
		1:00	EU	CE%sT

Link	Europe/Zurich	Europe/Vaduz
```

In this example, the EU rules are for the European Union and for its predecessor organization, the European Communities. The timezone is named Europe/Zurich and it has the alias Europe/Vaduz. This example says that Zurich was 34 minutes and 8 seconds east of UT until 1853-07-16 at 00:00, when the legal offset was changed to 7 degrees 26 minutes 22.50 seconds, which works out to 0:29:45.50; zic treats this by rounding it to 0:29:46. After 1894-06-01 at 00:00 the UT offset became one hour and Swiss daylight saving rules (defined with lines beginning with “Rule Swiss”) apply. From 1981 to the present, EU daylight saving rules have applied, and the UTC offset has remained at one hour.

In 1941 and 1942, daylight saving time applied from the first Monday in May at 01:00 to the first Monday in October at 02:00. The pre-1981 EU daylight-saving rules have no effect here, but are included for completeness. Since 1981, daylight saving has begun on the last Sunday in March at 01:00 UTC. Until 1995 it ended the last Sunday in September at 01:00 UTC, but this changed to the last Sunday in October starting in 1996.

For purposes of display, “LMT” and “BMT” were initially used, respectively. Since Swiss rules and later EU rules were applied, the time zone abbreviation has been CET for standard time and CEST for daylight saving time.

## FILES
/etc/localtime

Default local timezone file.

/usr/share/zoneinfo

Default timezone information directory.

## NOTES
For areas with more than two types of local time, you may need to use local standard time in the AT field of the earliest transition time's rule to ensure that the earliest transition time recorded in the compiled file is correct.

If, for a particular timezone, a clock advance caused by the start of daylight saving coincides with and is equal to a clock retreat caused by a change in UT offset, zic produces a single transition to daylight saving at the new UT offset without any change in local (wall clock) time. To get separate transitions use multiple zone continuation lines specifying transition instants using universal time.

## SEE ALSO
tzfile(5), zdump(8)


mariadbd

package: mariadb-server

title: mariadbd(8)

text:
# mariadbd(8)

## NAME
mariadbd - the MariaDB server (mariadbd is now a symlink to mariadbd)

## SYNOPSIS
mariadbd [options]

## DESCRIPTION
mariadbd, also known as MariaDB Server, is the main program that does most of the work in a MariaDB installation. MariaDB Server manages access to the MariaDB data directory that contains databases and tables. The data directory is also the default location for other information such as log files and status files.

When MariaDB server starts, it listens for network connections from client programs and manages access to databases on behalf of those clients.

The mariadbd program has many options that can be specified at startup. For a complete list of options, run this command:

```
shell> mariadbd --verbose --help
```

MariaDB Server also has a set of system variables that affect its operation as it runs. System variables can be set at server startup, and many of them can be changed at runtime to effect dynamic server reconfiguration. MariaDB Server also has a set of status variables that provide information about its operation. You can monitor these status variables to access runtime performance characteristics.

For a full description of MariaDB Server command options, system variables, and status variables, see the MariaDB Documentation.

## COPYRIGHT
Copyright 2007-2008 MySQL AB, 2008-2010 Sun Microsystems, Inc., 2010-2025 MariaDB Foundation

This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.

This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1335 USA or see http://www.gnu.org/licenses/.

## SEE ALSO
For more information, please refer to the MariaDB Documentation, available online at https://mariadb.com/docs/

## AUTHOR
MariaDB Foundation (http://www.mariadb.org/).


mathopd

package: mathopd

title: mathopd(8)

text:
# mathopd(8)

## NAME
mathopd - Advanced Hypertext Tranfer Protocol Server

## SYNOPSIS
mathopd [ -ndtv ] [ -f config_file ]

## OPTIONS
-n

If this option is supplied, Mathopd continues to run in the foreground after initialization. This is useful for debugging purposes.

-d

If this option is supplied, Mathopd starts up in debugging mode. Debugging can be turned on and off while the server is running; see the section on signals below.

-t

If this option is supplied, Mathopd will write diagnostics to the standard error channel as well as the error log. The option is named after the tee(1) program.

-v

If this option is supplied, Mathopd prints its version number and exits.

-f config_file

Use the configuration file specified by config_file. If the -f option is not used, Mathopd expects a configuration file from standard input. This is mainly for historic reasons; there is no reason why one should not use the -f flag. mathopd.conf(5) describes the syntax of the mathopd configuration file.

## SIGNALS
While the server is running, is reacts to certain signals. If a PIDFile is specified in the configuration file, you can send signals to Mathopd using something like

\# kill -<signal> `cat /var/run/mathopd.pid`

from the command line, assuming the PIDFile is /var/run/mathopd.pid.

A list of signals and their effects follows.

SIGHUP

If this signal is received, Mathopd will reopen its access and error log files. See the section on log files below.

SIGTERM SIGINT

These signals have identical effects: they stop Mathopd immediately, that is, all connections are closed and all server sockets as well. Note that the fact that SIGINT stops the server means that you can stop Mathopd by pressing Ctrl-C (or whatever key has the interrupt function) if it was started with the -n flag.

SIGQUIT

This signal toggles the debugging flag: if debugging was turned off before this signal was sent, it will be turned on, and vice versa.

SIGUSR1

This signal disconnects all clients, if any from the server. New connections can still be made after this.

SIGUSR2

This signal closes the server socket(s). No more connections will be received after this. Requests that are active at the time of the signal will be completed. After all active requests are timed out or done, Mathopd will exit. Use this signal for a 'graceful exit'.

## EXIT
Mathopd will exit voluntarily (as opposed to crash :) for a few reasons:

-

after reception of a SIGTERM or SIGINT signal

-

when no active connections and no active servers remain; this will be the case some time after delivery of SIGUSR2, or (rather perversely) if Mathopd was started up with a configuration file that did not contain any Server keywords

-

if it cannot open the Log, ErrorLog, or PIDFile; this can only be the case when the server is started up; if Mathopd fails to open a logfile while it is running, it will continue to use the logfile that it already opened (see below)

-

when it can not write to the access or error log; for example, if the disk partition that contains the access or error log gets filled up, Mathopd will die when it tries to write there.

## LOG FILES
Each hour Mathopd will re-open its access and error log, as if it had received a SIGHUP signal. For example, if you have the following in your configuration file

Log /var/mathopd/accesslog

ErrorLog /var/mathopd/errorlog

and rename /var/mathopd/accesslog to /var/mathopd/accesslog.old, Mathopd will continue to log in accesslog.old, but will switch to accesslog at the start of the next hour (with one exception: if Mathopd cannot open a new accesslog for any reason, it will *still* continue to log to accesslog.old.) Something similar applies to the ErrorLog.

There are two exceptions to the above: if the value of Log or ErrorLog is either "/dev/stdout" or "/dev/stderr", then the log will not be rotated: mathopd will not try to re-open these files. This is because /dev/stdout and /dev/stderr will be gone once the server has started up.

The name of the Log, ErrorLog and ChildLog will be 'strftime- expanded'. This means that any occurrence of, say, '%Y' in the name will be expanded to the current (4-digit) year.

For example: suppose the configuration file reads as follows

Log /var/mathopd/log.%Y%m%d

In that case, Mathopd will open /var/mathopd/log.20031204 when it is started up on 4 Dec 2003, and will automatically close that file and open /var/mathopd/log.20031205 at the start of the next day.

For more information on the % constructions, see the manual pages for date(1) and strftime(3).

## AUTHOR
Mathopd was written and is copyright by Michiel Boland.

## SEE ALSO
mathopd.conf(5)


mbpfan

package: mbpfan

title: mbpfan(8)

text:
# mbpfan(8)

## NAME
mbpfan - A simple daemon to control fan speed on all Apple computers — (enhanced version of Allan McRae mbpfan)

## SYNOPSIS
mbpfan [OPTIONS]

## DESCRIPTION
mbpfan is a daemon that uses input from coretemp module and sets the fan speed using the applesmc module. This enhanced version assumes any number of processors and fans (max. 10), and it is distro- and kernel-independent.

## OPTIONS
-h

Show the help screen

-f

Run in the foreground

-v

Be (alot) verbose

## FILES
/etc/mbpfan.conf

The system wide configuration file.

## AUTHOR
Daniel Graziotin <daniel@ineed.coffee>

## MORE INFO
https://github.com/dgraziotin/mbpfan/

https://ineed.coffee/3838/a-beginners-tutorial-for-mbpfan-under-ubuntu/

http://allanmcrae.com/2010/05/simple-macbook-pro-fan-daemon/