You are not logged in.
Pages: 1
Can anyone help please?? We're talking about a stand-alone,
domestic PC, that gets powered on and booted up when it's
needed and then powered off again when the work's done
(to save electricity). There is no fixed schedule for using the PC.
I've installed and (systemctl) enabled cronie to run an anacron
job shortly after power-ON, boot-up. The job does run BUT the
problem is the delayed start of the execution of the anacron job.
The intention is that the anacron job will run a couple of minutes
after boot-up, without having to wait for one-minute past the
hour as dictated by cron.hourly.
Can anybody suggest a remedy please???
Thanks in advance.
Dynosaw
--
Last edited by dynosaw (2021-03-12 20:42:14)
Offline
considered systemd.timer?
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
Just fire "anacron -n" with a "powerd up" service/script/hook?
Offline
Seth, Mr. Elendig
Thank you for your inputs. Both appreciated.
Mr. Elendig's input opened a whole new set of
perspectives from which the main conclusion
is that what works with one Linux distro cannot
be blindly carried over mutatis mutandis to
another distro. This anacron story is an example.
The delay in replying from this side is because
Mr. Elendig prompted me to search the web and
start reading. Amongst others, I turned up the
following (which may be useful for those who
come after me). For specific info:
1. Steven Vona <https://www.putorius.net/using-systemd-timers.html>
and for general info:
2. Systemd/Timers <https://wiki.archlinux.org/index.php/Systemd/Timers>
Again thanks. For my part this enquiry is sucessfully closed out.
Dynosaw
--
Offline
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
Pages: 1