sensors(1)
๐ sensors โ bestie, let's read ur temps ๐
okay so this is the sensors(1) page from the Linux User's Manual, and honestly? she's a baddie. let's get into it ๐ซถ
โจ NAME โจ
sensors โ print sensors information ๐ก๏ธโจ
๐ธ SYNOPSIS ๐ธ
sensors [ options ] [ chips ]
sensors -s [ chips ]
sensors --bus-list
๐ฆ DESCRIPTION ๐ฆ
okay so sensors is literally the girl who tells you what all ur sensor chips are currently reading. main character energy fr.
sensors -s is her in her setter era โ she goes and sets all the limits exactly as they're specified in the configuration file. periodt.
and sensors --bus-list? she generates bus statements that are suitable for the configuration file. iconic behavior ๐
๐ OPTIONS ๐
-c,--config-fileconfig-file โ bestie, tell her which configuration file to use. if you don't specify a file, the libsensors default configuration file gets used instead. and if you wanna temporarily disable that default config file? use-c /dev/nulland she'll act like it never existed ๐-h,--helpโ prints a help text and dips. that's it. that's the whole vibe โจ-s,--setโ she evaluates all thesetstatements in the configuration file and then exits. no cap: you must berootto do this. and if this parameter isn't specified, then likeโฆ nosetstatement gets evaluated at all. zero. none. ๐-A,--no-adapterโ do not show the adapter for each chip. she's keeping it lowkey ๐-uโ raw output. this mode is giving debugging energy, and it's also suitable for post-processing the output by scripts. it's also highkey useful when you're writing a configuration file, because it shows the raw input names which must be referenced in the configuration file. iykyk ๐-jโ Json output. yeah bestie, json ๐-Jโ new json output. this mode is suitable for post-processing of the output by scripts. she leveled up fr fr ๐ฅ-v,--versionโ print the program version and exit. short n sweet ๐-f,--fahrenheitโ print the temperatures in degrees Fahrenheit instead of Celsius. for my american besties ๐ฆ (affectionate) โญ--bus-listโ generate bus statements suitable for using insensors.conf. so like, these bus statements are only needed if you have several chips sharing the same address on different buses of the same type. and the reason is that bus numbers are usually not guaranteed to be stable over reboots, so these statements let you refer to each bus by its name rather than numbers. she's solving a real problem, ok?? ๐ง-n,--allow-no-sensorsโ do not fail if no sensors found. the error message will be printed in the log. she's not gonna crash out over it, she's just gonna journal about it ๐ ๐ญ
๐ FILES ๐
/etc/sensors3.conf/etc/sensors.conf
these are the system wide configuration file(s). see sensors.conf(5) for further details ๐โจ
๐ SEE ALSO ๐
sensors.conf(5), sensors-detect(8).
๐ AUTHOR ๐
Frodo Looijaard and the lm_sensors group https://hwmon.wiki.kernel.org/lm_sensors
bestie reminder: the-sthing needsroot, and the default config file can be ghosted with-c /dev/null. that's the whole tea โ
and that's the page!! this was lm-sensors 3, dated November 2012, and she's still out here being sensors(1) for us. mwah ๐๐
โจ
๐ฆ where this page comes from
- debian trixie: lm-sensors 1:3.6.2-2
- ubuntu questing: lm-sensors 1:3.6.2-2
- ubuntu resolute: lm-sensors 1:3.6.2-2build1
- ubuntu stonking: lm-sensors 1:3.6.2-2build1
- Copyright 1999 Frodo Looijaard <frodol@dds.nl>
- Copyright (C) 2007-2012 Jean Delvare <jdelvare@suse.de>
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms