Although it's easy to modify /etc/default/smartmontools it should be asked
at install time though.

tags 204613 +wontfix
Thanks,
Well, this would involve running smartd with DEVICESCAN the first time
which clutters people's syslog and might cause problems. I'd prefer to
let people read the docs before starting the daemon. (In the not so near
future) I plan to implement DEVICESCAN as a seperate tool that is able
to write out smartd.conf, once this is there (and Bruce doesn't object
to such a tool) making /e/d/smartmontools debconf handeld will be easy.
Regards,
 -- Guido

I also think that's the right approach, since there are some devices that
can apparently cause system hangs when probed by smartmontools.
(1) Scan hardware database (/etc/sysconfig/hwconf on Redhat, for
    example) and use a pearl/python script to make /etc/smartd.conf

(2) Add a -o filename option to smartd.  This option makes it run silently
in the foreground, construct a device list, probe devices (once) for SMART
capabilities, print device list in correct format, and then exit.  We
could make smartd set itself an alarm and kill signal at the start so
that it would be guaranteed to exit after (say) 20 seconds.

Guido, if you like option 2, everything is already in place, with the
exception of a routine to print the output file.  This is nice because it
keeps us from having to maintain a separate tool, and evolves in parallel
with smartd.

Cheers,
	Bruce

Debian lacks a hw database at the moment. Are hot pluggable devices
listed there too?
This sounds very good.
I've put this on my TODO list but I don't think I'll find the time to
look into this in the very near future.
 -- Guido

Interesting -- I had some email exchange with Arjan van de Ven about how
to improve the smartmontools packaging in redhat.  He thought that every
major distribution has some type of hardware database engine.

I don't know if the redhat database has hot pluggable devices -- but I'll
find out.

I've been working on the internal structure of smartd quite a lot during
the past days - in particular to make all the important internal
structures dynamically allocated/deallocated.  So it should make it easy
to accomodate a future where we could actually track devices as they are
added and removed without having to even restart smartd.

It's quite easy -- in fact documenting it is harder than writing the code.

Tell me if you want to do it.  Or tell me if you think you'd use it -
since this may be the motive that I need to push me to add it myself!

Cheers,
	Bruce

Hi Bruce,
This only makes sense if I change the debian packaging quiet a bit. When
I do this I can add the function to write out smartd.conf too.
Regards,
 -- Guido

Tell me when the time comes and I'll either do it or help you do it.

Cheers,
	Bruce

Dear Purchasing Manager,

This is Mr. Paul Lee from Guangzhou, China.
We production and wholesale DC Motors for Smart device application.
If you know it and need to pruchase these products, welcome contact me.

Thank you.

Best reagards,
Paul

2022-05-31



Yeshion Enterprise Co., Ltd.
Tel: +86-20-32235863
Fax: +86-20-32288329
E-mail: saleseurope@yeshion.com
Website: motors.yeshion.com
Guangzhou · China - DC Motors Supplier