Section 5: file formats
freeipmi_interpret_sel.conf – specify system event log (SEL) interpretation rules Description The /etc/freeipmi//freeipmi_interpret_sel.conf defines how IPMI system event log entries should be interpreted. IPMI system events specify a number of states/thresholds when they are read. Based on those states/thresholds, libraries and tools such as libipmimonitoring(3) and ipmi-sel(8) can report if an event is "good" or "bad"…
freeipmi.conf – specify default values to FreeIPMI Description The FreeIPMI configuration file can be used to set alternate default values to many FreeIPMI tools so values don’t have to be configured on the command line. This allows users to avoid typing in a long list of command line options everytime a command is executed. It…
freeipmi.conf – specify default values to FreeIPMI Description The FreeIPMI configuration file can be used to set alternate default values to many FreeIPMI tools so values don’t have to be configured on the command line. This allows users to avoid typing in a long list of command line options everytime a command is executed. It…
Makefile.fpc – Configuration file for fpcmake. Synopsis Makefile.fpc is a configuration file for the fpcmake command. Starting from this file a Makefile is created to compile Free Pascal units and programs. Description Makefile.fpc is a plain ASCII file that contains a number of sections as in a Windows ini file. The following sections are recognized…
fpc.cfg – Free Pascal Compiler (FPC) configuration file, name derived from Free Pascal Compiler. Description This is the main configuration file of the Free Pascal Compiler (FPC) All commandline options of the compiler (described in fpc(1) ) can be specified in fpc.cfg When the configuration file is found, it is read, and the lines it…
forward – email forwarding information file Description Users may put a .forward file in their home directory. If this file exists, smtpd(8) forwards email to the destinations specified therein. A .forward file contains a list of expansion values, as described in aliases(5). Each expansion value should be on a line by itself. However, the .forward…
forbidden_words.conf – configuration file for libreport. Description This configuration file specifies which words are highlighted in User Interface during the process of reporting a problem for the purpose of warning a user and getting his attention before he publish security sensitive data. The configuration format is one line per forbidden word. Users can provide own…
forbidden_words.conf – configuration file for libreport. Description This configuration file specifies which words are highlighted in User Interface during the process of reporting a problem for the purpose of warning a user and getting his attention before he publish security sensitive data. The configuration format is one line per forbidden word. Users can provide own…
fonts.conf – Font configuration files Synopsis /etc/fonts/fonts.conf /etc/fonts/fonts.dtd /etc/fonts/conf.d $XDG_CONFIG_HOME/fontconfig/conf.d $XDG_CONFIG_HOME/fontconfig/fonts.conf ~/.fonts.conf.d ~/.fonts.conf Description Fontconfig is a library designed to provide system-wide font configuration, customization and application access. Functional Overview Fontconfig contains two essential modules, the configuration module which builds an internal configuration from XML files and the matching module which accepts font patterns and…
fontcap – A list of supported NCAR Graphics font definition files for use with ctrans and Plotchar. Description font1 A very simple ASCII font. font2 Character fontcap for: HERSHEY:CARTOGRAPHIC_ROMAN font3 Character fontcap for: HERSHEY:CARTOGRAPHIC_GREEK font4 Character fontcap for: HERSHEY:SIMPLEX_ROMAN font5 Character fontcap for: HERSHEY:SIMPLEX_GREEK font6 Character fontcap for: HERSHEY:SIMPLEX_SCRIPT font7 Character fontcap for: HERSHEY:COMPLEX_ROMAN font8…
fmtutil.cnf – configuration file for fmtutil Description The fmtutil.cnf file contains the configuration information for fmtutil(8). Each line contains the name of the format (e.g., “tex”, “latex”, “omega”), the name of the engine that is used by that format (e.g., “tex”, “etex”, “omega”), the pattern file (e.g., language.dat, language.def), and any arguments (name of an…
fmtutil.cnf – configuration file for fmtutil Description The fmtutil.cnf file contains the configuration information for fmtutil(8). Each line contains the name of the format (e.g., “tex”, “latex”, “omega”), the name of the engine that is used by that format (e.g., “tex”, “etex”, “omega”), the pattern file (e.g., language.dat, language.def), and any arguments (name of an…
fluxbox-style – A comprehensive look at styles/themes for fluxbox(1). Synopsis This document describes various options available for fluxbox styles. Description What is a Style? Styles, sometimes referred to as Themes, are a graphical overlay for the fluxbox(1) window manager. If you wanted to get to know fluxbox, the styles would be the look of the…
fluxbox-menu – fluxbox(1) menu syntax Synopsis /usr/local/share/fluxbox/menu ~/.fluxbox/menu ~/.fluxbox/windowmenu Syntax Variable parameters are shown in emphasis: argument All other characters shown are required verbatim. Whitespace is only required to delimit words, but it is fine to add more whitespace. Description There are two types of menus in fluxbox which can be configured. The first is…
fluxbox-keys – keyboard shortcuts configuration for fluxbox(1) Synopsis ~/.fluxbox/keys Syntax Variable parameters are shown in emphasis: argument Optional parameters are shown in square brackets: [argument] All other characters shown are required verbatim. Whitespace is required where shown, but it is fine to add more whitespace. Description The keys file defines the keyboard shortcuts for fluxbox(1)….
fluxbox-apps – per-window attribute configuration for fluxbox(1) Synopsis ~/.fluxbox/apps Syntax Variable parameters are shown in emphasis: argument All other characters shown are required verbatim. Whitespace is only required to delimit words, but it is fine to add more whitespace. Description It is possible to force an application to always have the same dimensions, position, and…
flatpak-remote – Configuration for a remote Description Flatpak stores information about configured remotes for an installation location in $installation/repo/config. For example, the remotes for the default system-wide installation are in $prefix/var/lib/flatpak/repo/config, and the remotes for the per-user installation are in $HOME/.local/share/flatpak/repo/config. Normally, it is not necessary to edit remote config files directly, the flatpak remote-modify…
flatpak-metadata – Information about an application or runtime Description Flatpak uses metadata files to describe applications and runtimes. The metadata file for a deployed application or runtime is placed in the toplevel deploy directory. For example, the metadata for the locally installed application org.gnome.Calculator is in ~/.local/share/flatpak/app/org.gnome.Calculator/current/active/metadata. Most aspects of the metadata configuration can be…
flatpak-installation – Configuration for an installation location Description flatpak can operate in system-wide or per-user mode. The system-wide data is located in $prefix/var/lib/flatpak/, and the per-user data is in $HOME/.local/share/flatpak/. In addition to the default installation locations, more system-wide installations can be defined via configuration files /etc/flatpak/installations.d/, which must have the .conf extension and follow…
flatpak-flatpakrepo – Reference to a remote Description Flatpak uses flatpakrepo files to share information about remotes. The flatpakrepo file contains enough information to add the remote. Use the flatpak remote-add –from command to do so. flatpakrepo files may also contain additional information that is useful when displaying a remote to the user, e.g. in an…