sos.conf(5)

πŸ“¦
version 4.12.1 Β· 3 versions
, in centos-stream 10, centos-stream 9, debian trixie, fedora 43, fedora 44, nixos 26.05, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ NAME ✨

okay bestie, this is the sos.conf(5) page from the File Formats Manual πŸŽ€ and it's all about sos.conf, the sos report configuration file πŸ’–


🌸 DESCRIPTION 🌸

okay so sos report reads a config file at /etc/sos/sos.conf πŸ“, and there are a few subdirectories under /etc/sos that each do their own specific job 🧚

ngl, non-root users get to override anything in /etc/sos/sos.conf by making their own sos.conf under $HOME/.config/sos 🫢

the order options get loaded in is:

  1. the system config file at /etc/sos/sos.conf 🏠
  2. the user-specific config file at $HOME/.config/sos/sos.conf (for sos components that support non-root πŸ™‹β€β™€οΈ)
  3. when you run sos report, presets, either auto-loaded because of the system config or picked with --preset 🎯
  4. command line values πŸ’…

so basically: config files beat the defaults, presets beat config files, and command line values beat literally everything πŸ‘‘


πŸ¦‹ SUBDIRECTORIES πŸ¦‹

these subdirectories live under /etc/sos, and each one has its own vibe πŸ’œ

🧩 extras.d

this one stores config files for the sos_extras plugin ✨

the plugin walks through this directory, and for each file in there it runs commands or collects files (optionally with a sizelimit) πŸ“¦

an extras file should look like this πŸ‘‡:

  • empty lines, or lines starting with #, get ignored πŸ™ˆ
  • lines starting with : call add_copy_spec, and you can optionally tack on a sizelimit after the path πŸ“„
  • anything else gets run as a command πŸƒβ€β™€οΈ

here's an example πŸ“:

command1 --arg1 val1
command2
:/path/to/file
:/path/to/files* sizelimit
⚠️ WARNING ⚠️ be careful about what files you collect and what commands you run, bestie 😭 - avoid anything potentially dangerous or system altering, like: - chaining multiple commands on one line (with pipes, semicolons, etc.) - running commands in the background - setting env.variables (those get ignored anyway) - altering a system (and yes, that includes more than just rm -rf) - be aware that no secret obfuscation happens πŸ”“

πŸ‘― groups.d

this one stores host group config files for sos collect πŸ«‚

these files can specify any or all of the primary, nodes, and cluster-type options πŸ’œ

users can make their own private host groups in $HOME/.config/sos/groups.d/ 🏑. if a host group has the same name in both your homedir and this directory, your homedir version wins πŸ‘‘. when you run as non-root, sos collect saves host groups to your home dir, and it'll create the directory structure it needs if it's missing πŸ› οΈ

heads up: non-root users can load host groups defined under /etc/sos/groups.d/, but they can't write new groups or update existing ones saved there πŸ™…β€β™€οΈ

πŸŽ€ presets.d

this one stores preset config files for sos report 🎯

presets are how you save standard sets of options πŸ’…. check out sos-report (see man sos-report) for more info 🧚


🌈 PARAMETERS 🌈

there are sections for each sos component, plus global values and plugin options 🧁. options are set as ini-style name = value pairs πŸ“. you turn a boolean option on or off the same way you would on the command line, like process.lsof=off πŸ”

some options take a comma separated list of values πŸ“

options that don't expect a value (like all-logs or no-report) get enabled no matter what value you set πŸ™ƒ

sections get parsed in this order:

  • [global] 🌍
  • [component] 🧩
  • [plugin_options] πŸ”Œ

🌍 [global]

  • <option> β€” sets the (long) option value. short options (like z=auto) are not supported, so don't even try πŸ™…β€β™€οΈ

🧩 [component]

each component gets its own section, and it supports the options that particular component offers ✨. you can spot them easily in the --help output for each component, like sos report --help πŸ‘€

πŸ”Œ [plugin_options]

this lets you change available options for defined (and loaded) plugins πŸ”§

it takes the form plugin.option = value, for example rpm.rpmva = true πŸ’œ


πŸŽ€ EXAMPLES πŸŽ€

okay here are some examples so you can see it in action 🫢

to use quiet and batch mode with 10 threads:

[global]
batch=yes
build=true
threads=10

to disable the host and filesys plugins:

[report]
skip-plugins = host,filesys

to disable rpm package verification in the RPM plugin:

[plugin_options]
rpm.rpmva = off

πŸ“ FILES πŸ“

  • /etc/sos/sos.conf 🏠
  • $HOME/.config/sos/sos.conf (optional) πŸ™‹β€β™€οΈ

πŸ‘‘ SEE ALSO πŸ‘‘


okay that's the whole tea β˜• go configure something iconic, bestie πŸ’…βœ¨ sos configuration file Β· SOS Β· sos.conf(5) πŸ¦‹πŸ’–