On Fri, Jul 25, 2008 at 08:44:19PM +0800, [EMAIL PROTECTED] wrote: > I have an idea. Instead of adding or adjusting the commented out > examples in /etc/smartd.conf, which causes the user to have to deal > with: > Configuration file `/etc/smartd.conf' > ==> Modified (by you or by a script) since installation. > ==> Package distributor has shipped an updated version. > What would you like to do about it ? Your options are: > > Why not just keep all the comments on the man page, that way the user > would not need to repair the file upon upgrade. I agree here. A smartd.conf like:
# The file gives a list of devices to monitor using smartd, with one # device per line. Text after a hash (#) is ignored, and you may use # spaces and tabs for white space. You may use '\' to continue lines. # You can usually identify which hard disks are on your system by # looking in /proc/ide and in /proc/scsi. # The word DEVICESCAN will cause any remaining lines in this # configuration file to be ignored: it tells smartd to scan for all # ATA and SCSI devices. DEVICESCAN -m root -M exec /usr/share/smartmontools/smartd-runner # For many more detailes examples please see: # /usr/share/doc/smartmontools/examples/smartd.conf would ease upgrades a lot. -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
