From owner-freebsd-current  Thu Apr  4 01:47:08 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id BAA16155
          for current-outgoing; Thu, 4 Apr 1996 01:47:08 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA16117
          Thu, 4 Apr 1996 01:46:59 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id TAA05128; Thu, 4 Apr 1996 19:45:39 +1000
Date: Thu, 4 Apr 1996 19:45:39 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199604040945.TAA05128@godzilla.zeta.org.au>
To: ache@freefall.freebsd.org, jdp@polstra.com
Subject: Re: adjkerntz (was: cvs commit: src/usr.sbin/tzsetup ...)
Cc: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>> > Is this really what is supposed to be happening?  If there's a persistent
>> > daemon, why must there also be separate periodic runs of the same program?
>>
>> IMHO reading one screen of adjkerntz manpage is more quick thing
>> then writting such letter.

>IMHO the manual page is unclear.  I read it over several times, and also
>looked at the source.  Yet I still have this question.  Your reply did
>nothing to change that.

The persistent daemon is used because there's no better way to ensure that
adjkerntz is run on reboot.  (See another discussion about SYSV run control
vs BSD run control.)

The periodic runs from cron are because it's easier to schedule such things
using cron.

The man page is clear enough about what running adjkerntz does and why you
might want to run it at boot time and at 03:01.

Bruce