Ticket #2174 (new enhancement)

Opened 2 years ago

Last modified 1 week ago

Add 'include' functionality for sensors.conf

Reported by: mmh Assigned to: mmh
Priority: major Milestone: 3.0.4
Component: libsensors Version:
Keywords: Cc:

Description

Add the ability to 'include' other files from sensors.conf. See the mailing list archives for a discussion of this feature.

Change History

07/08/07 21:13:25 changed by khali

  • component changed from misc to libsensors.

10/09/07 14:27:11 changed by khali

  • milestone changed from 3.0.0 to 3.0.1.

01/25/08 17:18:15 changed by khali

  • milestone changed from 3.0.1 to 3.0.2.

05/06/08 21:05:08 changed by khali

  • milestone changed from 3.0.2 to 3.0.3.

09/21/08 17:34:49 changed by khali

  • milestone changed from 3.0.3 to 3.0.4.

11/22/08 11:24:59 changed by khali

I have been thinking about this for some time now. I am not sure that adding an "include" keyword to sensors.conf, as had been discussed, is the best way to go.

What about having a /etc/libsensors.d directory that would work the same way as /etc/modprobe.d (and many other similar configuration directories) work? The user could simply drop board-specific configuration files there, and libsensors would take care of processing all the files it finds in this directory.

The advantage over adding an "include" keyword are:

  • No configuration file syntax change. This syntax change would cause new configuration files to fail on systems with an older version of libsensors.
  • No need for the user to maintain a central sensors.conf that includes his/her board-specific configuration files.
  • No need to deal with recursion depth issues.

One drawback I can think of is a worse control of the inclusion order. I am not sure if it really matters in practice though, and if it does, we can probably work around it by having libsensors process files in a well-defined order.