Hi there.
Thanks. I am glad to hear that. I will of course test it.
--
If you implement iterating through devices, you probably should not
use the /dev/disk directory. Udev is not present on some platforms -
including openwrt (per default).
(In this case you currently cannot configure the discs via id in
spindown.conf, but specifying devices works)
In order not to increase dependencies you could go through proc
diskstats and do it for every device which matches "sd?" or "hd?".
I think hardcoding it to these two would be ok, since your software
won't with non-linux unixes anyway. (The others don't have /proc/
diskstats.)
--
Concerning init-scripts:
Well, you could consider not supporting a fancy init-script...
Every distribution has its own convention here.
Most distributions have a skeleton init-script which simply is a
template. (/etc/init.d/skeleton)
In a perfect world your software is ready-packaged for the
distributions by the package maintainers and they would create and
integrate the script for the users.
But in the meantime you can search the web for a very basic posix
compliant init-script (without all status-stuff). This should work for
all distributions.
You can even avoid all shell and path quirks by simply doing:
at start)
killall spindownd > /dev/null 2> /dev/null
spindownd --daemon
at stop)
killall spindownd
It is not supposed to run twice anyway...
This should be sufficient for most users.
--
Regards, Michael
On Nov 24, 11:52 pm, Dimitri Michaux <
dimitri.mich...@gmail.com>
wrote: