On 22/11/2017 04:48 pm, Martin Gregorie wrote:
> On Wed, 22 Nov 2017 15:26:19 +0000, Richard Kettlewell wrote:
>
>> Martin Gregorie  writes:
>>> On Wed, 22 Nov 2017 13:28:19 +0000, Richard Kettlewell wrote:
>>>> Martin Gregorie  writes:
>>>>> I have a cronjob set up on my Fedora systems to run updatedb every
>>>>> night, but I run it manually with a "sudo updatedb" command on my RPi
>>>>> before running 'apropos' or 'locate' (the latter is a fast file
>>>>> finder).
>>>>
>>>> Note that there is no need for these manual steps on Debian (or
>>>> Raspbian).
>>>
>>> I presume that's due to atd?
>>
>> No, the packages contain cron jobs that keep things up to date.
>>
> Fedora uses both crond and atd: crond runs jobs as they come due but
> misses jobs if it wasn't running at that time. atd runs all the jobs that
> crond missed and runs them as some short random time after Lunux was
> booted or comes out of suspension/hibernation.
>
> I though all Linux distros used this same duality and I was right, but
> some distros don't install atd by default. Fedora does and Raspbian
> doesn't.
>
> The 'at' package, which includes at and atd, is now installed on my RPi,
> so updatedb will now get run automatically a bit more often. I'm no
> longer surprised that updatedb has never been automatically run here
> because all daily jobs are run at 06:30 and AFAICR my RPi has never been
> running at that time.
>
> Related point: I thought 'locate' was installed by default for Raspbian,
> but it ain't. It turns out its in the 'locate' package and I'd installed
> that a long time ago.
>
>

If your computer isn't on 24x7, you should install anacron which will
take care of all /etc/cron.daily, .weekly and .monthly jobs (see
/etc/anacrontab). /etc/crontab, /etc/cron.d and individual crontabs are
still run by cron.

'atd' runs 'at' jobs, not 'cron' jobs

--

Chris Elvidge, England

--- SoupGate-Win32 v1.05