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

[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
>
> Fwiw, the rsync package is comparable to yours.
> It ships a tool (rsync) which can be used manually or act as a daemon.
>
> It ships a service file which has
>
> ConditionPathExists=/etc/rsyncd.conf
>
> The service is enabled during installation, but since the config file
> doesn't exist by default, the rsync daemon is not started unless the
> admin creates it.

adjtimexconfig produces /etc/default/adjtimex
So "ConditionPathExists=/etc/default/adjtimex" can simply avoid to
split the package!
Thanks for your advice!

Cheers,
Roger