Comment 52 for bug 568120

Steve,

The problem is kind of related because previously init.d script used to set the spindown interval during boot. After init.d script was removed, the spindown interval is not being set during boot, which causes hard drives to always spin.

However on the other hand side, it is different, because spindown interval is not set inside command_line block.

My findings are in comment #38, and a temp workaround in comment #40, but I don't know how to fix the actual issue properly.

I consider this a serious issue, as I only noticed due to smartd sending me emails of high disk temperatures. It definitely needs to be addressed.

The thing to work out is if a separate bug needs to be created for this, or should we change this bug's description to cover the wider problem of moving away from init.d script?