Bug796588#: adjtimex: Has init script in runlevel S but no matching service file

[Felipe Sateler]

On 14 December 2015 at 11:20, Roger Shimizu <rogershimizu at gmail.com> wrote:
> Dear systemd maintainers,
>
> Thanks for helping for the adjtimex systemd service file last time.
> I write again because I find an issue related to the service file.
>
> When installing, adjtimex's postinst script will ask user whether to
> start the service by debconf, for the service file currently (enclosed
> here), it doesn't respect the debconf if user choose "No".
>
> I find a temporary solution to patch postinst to run "systemctl
> disable adjtimex.service" if user choose not to start the service when
> in "configure" mode.
> I call it "temporary" because it will miss some rare case such as:
> - installing adjtimex when in sysvinit and choose not to start the
> service, then installing systemd to replace sysvinit, it but this
> won't trigger adjtimex's postinst script to disable adjtimex's
> service.

I don't follow. What exactly is the current behavior, and how does the
new systemd service file does not respect it? Please add more context.

I'd even question the need to ask about enabling the service. If I
don't want the service, why did I install the package? Admins can
manually disable later if they don't want to run it.

>
> I'm wondering whether do you already have a patch to get debconf's
> result in service file. I think it's the better solution than the
> temporary one above.

Don't do this. debconf is not a registry. The results of the debconf
question must be stored in the proper configuration (eg, enablement
state) and then read back to ask the user on the next install run.



-- 

Saludos,
Felipe Sateler