On Mon, Dec 14, 2015 at 11:57 PM, Felipe Sateler <[email protected]> wrote: > Another option is to simply not enable/start the service, and just > ship instructions on how to do that in README.Debian. > > Running it on postinst looks weird to me. We normally do not run > possibly long processes synchronously on package installs.
I agree to removing adjtimexconfig from postinst, which takes 70 seconds during install, is a good idea. But the defconf selection on enable/disable service is another issue. Yes, without adjtimexconfig running on install implies the service is disabled by default. But user need an easy way to enable adjtimex service after adjtimexconfig running. Do you think it's okay to run debconf to let user decide whether to start the service after manually running adjtimexconf? Thank you! Cheers, Roger
