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

[Roger Shimizu]

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'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.
Thanks and look forward to your reply!

Cheers,
Roger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: adjtimex.service
Type: application/octet-stream
Size: 310 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20151214/27bbd47d/attachment.obj>