Section 5: file formats
coredump.conf – Coredump storage configuration file Synopsis /etc/systemd/coredump.conf Description This file configures the behaviour of systemd-coredump, a handler for core dumps invoked by the kernel. Options All options are configured in the "[Coredump]" section: Storage= Controls where to store cores. One of "none", "external", "journal", and "both". When "none", the coredumps will be logged but…
coredump.conf, coredump.conf.d – Coredump storage configuration files Synopsis /etc/systemd/coredump.conf /etc/systemd/coredump.conf.d/*.conf /run/systemd/coredump.conf.d/*.conf /usr/lib/systemd/coredump.conf.d/*.conf Description These files configure the behaviour of systemd-coredump(8), a handler for core dumps invoked by the kernel. Configuration Directories And Precedence Default configuration is defined during compilation, so a configuration file is only needed when it is necessary to deviate from those defaults….
coredump.conf, coredump.conf.d – Coredump storage configuration files Synopsis /etc/systemd/coredump.conf /etc/systemd/coredump.conf.d/*.conf /run/systemd/coredump.conf.d/*.conf /usr/lib/systemd/coredump.conf.d/*.conf Description These files configure the behaviour of systemd-coredump(8), a handler for core dumps invoked by the kernel. Configuration Directories And Precedence Default configuration is defined during compilation, so a configuration file is only needed when it is necessary to deviate from those defaults….
core – core dump file Description The default action of certain signals is to cause a process to terminate and produce a core dump file, a file containing an image of the process’s memory at the time of termination. This image can be used in a debugger (e.g., gdb(1)) to inspect the state of the…
control.ctl – Specify handling of Usenet control messages Description The file pathetc/control.ctl is used to determine what action is taken when a control message is received. It is read by controlchan, which is normally invoked as a channel program by innd. When control.ctl is modified, controlchan notices this automatically and reloads it. If a control.ctl.local…
control.ctl – Specify handling of Usenet control messages Description The file pathetc/control.ctl is used to determine what action is taken when a control message is received. It is read by controlchan, which is normally invoked as a channel program by innd. When control.ctl is modified, controlchan notices this automatically and reloads it. If a control.ctl.local…
containerd-config.toml – configuration file for containerd Synopsis The config.toml file is a configuration file for the containerd daemon. The file must be placed at /etc/containerd/config.toml or specified with the –config option of containerd to be used by the daemon. If the file does not exist at the appropriate location or is not provided via the…
console.perms – permissions control file for users at the system console Description /etc/security/console.perms and .perms files in the /etc/security/console.perms.d directory determine the permissions that will be given to priviledged users of the console at login time, and the permissions to which to revert when the users log out. They are read by the pam_console_apply helper…
console.perms – permissions control file for users at the system console Description /etc/security/console.perms and .perms files in the /etc/security/console.perms.d directory determine the permissions that will be given to priviledged users of the console at login time, and the permissions to which to revert when the users log out. They are read by the pam_console_apply helper…
console.handlers – file specifying handlers of console lock and unlock events Description /etc/security/console.handlers determines which programs will be run when an user obtains the console lock at login time, and when the user loses it on log out. It is read by the pam_console module. The format is: handler-filename lock|unlock [flag …] Where handler-filename is…
console.apps – specify console-accessible privileged applications Description The /etc/security/console.apps/ directory should contain one file per application that wishes to allow access to console users. The filename should be the same as the servicename, and the contents are irrelevant; the file may be a zero-length file. The application that the file is used by is free…
console-setup – configuration file for setupcon Description The file console-setup specifies the encoding and the font to be used by setupcon(1) in order to setup the console. It can be used also to specify the keyboard layout but it is not recommended to do so, use keyboard(5) instead. The font specification consists of three parameters…
conserver.passwd – user access information for conserver(8) Synopsis username:password Description The conserver.passwd file is the user authentication and authorization file for conserver(8). Upon each incoming client connection, conserver opens and reads the conserver.passwd file, so edits to the file take effect immediately. It reads only until the first username match. Blank lines and comment lines…
conserver.cf – console configuration file for conserver(8) Description The format of the conserver.cf file is made up of named blocks of keyword/value pairs, comments, and optional whitespace for formatting flexibility. The block types as well as the keywords are pre-defined and explained in the BLOCKS section. A comment is an unquoted pound-sign to a newline….
main.conf – ConnMan configuration file Synopsis /etc/connman/main.conf or <SYSCONFDIR>/connman/main.conf where <SYSCONFDIR> depends on your distribution or build. Description main.conf is a configuration file for ConnMan. The configuration file is optional but it can be used to set up various aspects of ConnMan’s behavior. The location of the file may be changed through use of the…
conman.conf – ConMan daemon configuration file Description The conman.conf configuration file is used to specify the consoles being managed by conmand. Comments are introduced by a hash sign (#), and continue until the end of the line. Blank lines and white-space are ignored. Directives are terminated by a newline, but may span multiple lines by…
config-util – Common PAM configuration file for configuration utilities Synopsis /etc/pam.d/config-util Description The purpose of this configuration file is to provide common configuration file for all configuration utilities which must be run from the supervisor account and use the userhelper wrapper application. The config-util configuration file is included from all individual configuration files of such…
complex – xxQS_NAMExx complexes configuration file format Description Complex reflects the format of the xxQS_NAMExx complex configuration. The definition of complex attributes provides all pertinent information concerning the resource attributes a user may request for a xxQS_NAMExx job via the -l option, and for the interpretation of these parameters within the xxQS_NAMExx system. The xxQS_NAMExx…
collectd.conf – Configuration for the system statistics collection daemon collectd Synopsis BaseDir "/var/lib/collectd" PIDFile "/run/collectd.pid" Interval 10.0 LoadPlugin cpu LoadPlugin load <LoadPlugin df> Interval 3600 </LoadPlugin> <Plugin df> ValuesPercentage true </Plugin> LoadPlugin ping <Plugin ping> Host "example.org" Host "provider.net" </Plugin> Description This config file controls how the system statistics collection daemon collectd behaves. The most…
collectd-unixsock – Documentation of collectd’s "unixsock plugin" Synopsis # See collectd.conf(5) LoadPlugin unixsock # … <Plugin unixsock> SocketFile "/path/to/socket" SocketGroup "collectd" SocketPerms "0770" DeleteSocket false </Plugin> Description The "unixsock plugin" opens an UNIX-socket over which one can interact with the daemon. This can be used to use the values collected by collectd in other applications,…