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

Roger Shimizu rogershimizu at gmail.com
Mon Dec 14 16:18:45 GMT 2015


On Tue, Dec 15, 2015 at 12:42 AM, Michael Biebl <biebl at debian.org> wrote:
> Am 14.12.2015 um 16:35 schrieb Roger Shimizu:
>> On Tue, Dec 15, 2015 at 12:29 AM, Michael Biebl <biebl at debian.org> wrote:
>>> Am 14.12.2015 um 16:26 schrieb Michael Biebl:
>>>> You could check for the existence of a config file in your sysv init
>>>> script and simply exit if it doesn't exist.
>>>> Under systemd the equivalent is a ConditionPathExists=/etc/foobar.conf
>
>> adjtimexconfig produces /etc/default/adjtimex
>> So "ConditionPathExists=/etc/default/adjtimex" can simply avoid to
>> split the package!
>
> That sounds good. I would then suggest to drop the debconf machinery and
> the handwritten code which calls update-rc.d/invoke-rc.d directly
> and simply let dh_installinit/dh_systemd do the job.

It's clear to me now. Thanks for your advice!
I'll merge your idea with Felipe's suggestion to remove the 70-second
adjtimexconfig during install.

Cheers,
Roger




More information about the Pkg-systemd-maintainers mailing list