Buy GNU books!
|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|
To get its configuration, zlibc first looks into the file described by
the environment variable
LD_ZLIB_CONFFILE (if any), then in
`~/.zlibrc' and finally in `/usr/local/etc/zlibc.conf'
(`/etc/zlibc.conf' on Linux (2)). If the desired information is found in neither of
these files, the compiled-in defaults are used. It is possible to
supply only part of the needed information in the configuration
files. In that case, the missing information is retrieved from the
compiled-in defaults. This allows you to have really small runtime
configuration files, which only list the differences between the desired
configuration and the compiled-in configuration.
If an error occurs while parsing one of the configuration files, the
offending file is skipped, and the search continues with the next
file. However, no error message is printed unless the environmental
LD_ZLIB_VERBOSE is turned on (i.e. set to
If two files contain contradictory information, the information in the file which is scanned first is retained (usually `~/.zlibrc'). If any flags have been set or unset using environmental variables, these settings override the flags specified in the configuration files.
The configuration files are read by each process. For each process, they are read at most once, at the time when zlibc is first used (attempt to access a compressed file). Afterwards they are cached in the process's virtual memory. Thus, changing zlibc configuration files doesn't generally have any effect on already running processes.
|webmaster||delorie software privacy|
|Copyright © 2003 by The Free Software Foundation||Updated Jun 2003|