-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-09-10 at 01:15 +1000, Basil Chupin wrote:
That may be because the script/program responsible does not run, ie, exits, if it doesn't find the configuration file.
I feel that we are starting to lose the plot here.
I posted my original message for the simple reason that by having the lm_sensors file created a high-pitched noise started up when I booted into SUSE. It took a while to locate the reason for this noise so I posted the message in case someone else, at some future time, strikes the same problem and wonders what may be the sudden cause of the noise.
Joe Morris responded with the statement that nothing happens with lm_sensors until one copies the startup script from /usr/share/doc/packages/sensors/prog/init to /etc/init.d and then enables the script; he asked if I did this and I answered NO.
This is not really true. I have a "/etc/init.d/lm_sensors" file, which was installed automatically by yast; just ask rpm: nimrodel:~ # rpm -q -f /etc/init.d/lm_sensors sensors-2.10.0-10 It is a system file. See the code: CONFIG=/etc/sysconfig/lm_sensors ... start() { echo -n "Starting up sensors" unset ${!MODULE_*} test -r "$CONFIG" && . "$CONFIG" Now, what does that "test" line? `-r FILE' True if FILE exists and read permission is granted. But I'm unsure of what does the part to the right of &&. I think it runs the config file, setting up variables, if it exists. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFA0mHtTMYHG2NR9URAmu4AJ9cI0g65CBBXq4n4KTOG3uyth7SVwCeMeyT oGYxMC/lXwSYH/OJToqBiHk= =FO3k -----END PGP SIGNATURE-----