Bug#492340: don't comment smartd.conf

2008-07-25 Thread Guido Günther
On Fri, Jul 25, 2008 at 02:51:42PM -0500, Bruce Allen wrote: > Sorry Guido, I just saw this. I suggest that you just make a custom > smartd.conf for Debian. THanks for the comments! It's nicer to have upstream's blessing. -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject

Bug#492340: don't comment smartd.conf

2008-07-25 Thread Bruce Allen
Sorry Guido, I just saw this. I suggest that you just make a custom smartd.conf for Debian. On Fri, 25 Jul 2008, Guido Günther wrote: 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.co

Bug#492340: don't comment smartd.conf

2008-07-25 Thread Bruce Allen
Dear Guido, I don't like this idea for the generic case -- for example Win32 systems might not have man pages. So if you want this for the Debian version, I suggest that you just modify /etc/smartd.conf by using a sed script that deletes all lines that are comments: cat smartd.conf.upstream

Bug#492340: don't comment smartd.conf

2008-07-25 Thread jidanni
GG> I agree here. A smartd.conf like: Or better, just: #For documentation see man smartd.conf DEVICESCAN -m root -M exec /usr/share/smartmontools/smartd-runner and the man page would say where the examples file is, etc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscri

Bug#492340: don't comment smartd.conf

2008-07-25 Thread Guido Günther
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 i

Bug#492340: don't comment smartd.conf

2008-07-25 Thread jidanni
Package: smartmontools Version: 5.38-2 Severity: wishlist File: /etc/smartd.conf 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) si