On 2020-10-11 08:10, g4sra via Dng wrote:
> On 10/10/2020 21:47, Simon Walter wrote:
>> On 2020-10-08 21:08, g4sra via Dng wrote:
>> -- snip --
>>>
>>> Anybody enlighten me about the meaning of the phrase...
>>>
>>> 'The controller seems to be unused by "cgfsng" cgroup driver or not enabled
>>> on
On 10/10/2020 21:47, Simon Walter wrote:
> On 2020-10-08 21:08, g4sra via Dng wrote:
>-- snip --
>>
>> Anybody enlighten me about the meaning of the phrase...
>>
>> 'The controller seems to be unused by "cgfsng" cgroup driver or not enabled
>> on the cgroup hierarchy'
>
> Sorry for the late reply
On 2020-10-08 21:08, g4sra via Dng wrote:
> On 08/10/2020 04:30, Simon Walter wrote:
>> On 2020-10-05 11:23, tom wrote:
>> ...
>>>
>>> I would appreciate if we kept this on-board unless needed. Never know
>>> when someone in the future might find it useful.
>>>
>>
>> I would appreciate that too!
>>
On Sat, 2020-10-10 at 16:35 +0100, g4sra via Dng wrote:
> If anacron is installed, it will check for any outstanding jobs at
> boot and run them.
> [snip]
> Laptops are subject to power management settings which may also stop
> anacron from running.
>
If you use sleep or hibernate these can cau
On 10/10/2020 15:38, Mike Tubby wrote:
> All,
>
> I've just discovered that my various Devuan systems aren't running cron.daily
> or cron.weekly tasks because /etc/crontab performs a test on anacron being
> present.
Not quite...
cron will NOT run if anacron IS installed AND IS executable.
If
All,
I've just discovered that my various Devuan systems aren't running
cron.daily or cron.weekly tasks because /etc/crontab performs a test on
anacron being present. However /etc/crontab doesn't need anacron for
cron.hourly:
# /etc/crontab: system-wide crontab
# Unlike any other crontab yo
