Cron not working in appVMs

[cprise]

Cron and anacron haven't been running in my Fedora appvms: systemctl
says crond.service is enabled (I enabled it from the templatevm), but
/var/log/cron isn't being updated and the tasks I have scheduled aren't
getting executed. I also don't see a running crond process. (BTW,
/var/spool is now moved and symlinked to a subfolder in /rw so anacron
can keep track.)

Any thoughts on getting cron to work in Qubes?

[Marek Marczykowski-Górecki]

On 20.10.2014 22:37, cprise wrote:
> Cron and anacron haven't been running in my Fedora appvms: systemctl says
> crond.service is enabled (I enabled it from the templatevm)

Enabled, but is it running? Check "Active" field in systemctl status. If it
says it's inactive, try to start the service and check again.

> , but /var/log/cron
> isn't being updated and the tasks I have scheduled aren't getting executed. I
> also don't see a running crond process. (BTW, /var/spool is now moved and
> symlinked to a subfolder in /rw so anacron can keep track.)
>
> Any thoughts on getting cron to work in Qubes?

I've just tried and when I start it manually (sudo systemctl start
crond.service) it just works.

--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[cprise]

On 10/20/14 16:56, Marek Marczykowski-Górecki wrote:
> On 20.10.2014 22:37, cprise wrote:
>> Cron and anacron haven't been running in my Fedora appvms: systemctl says
>> crond.service is enabled (I enabled it from the templatevm)
> Enabled, but is it running? Check "Active" field in systemctl status. If it
> says it's inactive, try to start the service and check again.
>> , but /var/log/cron
>> isn't being updated and the tasks I have scheduled aren't getting executed. I
>> also don't see a running crond process. (BTW, /var/spool is now moved and
>> symlinked to a subfolder in /rw so anacron can keep track.)
>>
>> Any thoughts on getting cron to work in Qubes?
> I've just tried and when I start it manually (sudo systemctl start
> crond.service) it just works.
>

It does run if I manually do 'systemctl start crond.service'. But no
matter how many times I boot with the service enabled, crond doesn't run.

I've searched around for a Fedora-specific lead, but I'm not finding
anything that's applicable.

[cprise]

Do you think this indicates systemd isn't working correctly?