Sent from ProtonMail, encrypted email based in Switzerland.
------- Original Message -------
On Wednesday, April 6th, 2022 at 8:09 PM, Tim via users
<users(a)lists.fedoraproject.org> wrote:
> On Tue, 2022-04-05 at 20:18 +0000, olivares33561 via users wrote:
>
>> How can I convert a crontab
>> #
>> [olivares@fedora Downloads]$ crontab -l
>> # min hour day-of-month month day-of-week command
>> # 0-59 0-23 1-31 1-12 0-6 0=sun 1=mon
>> #50 04 * * 1-5 ~/.xalarm >/dev/null 2>&1
>> #50 04 * * 0,6 ~/.salarm >/dev/null 2>&1
>> #59 09 * * 0,6 ~/.salarm >/dev/null 2>&1
>> #00 07 * * 1-5 ~/.xalarm >/dev/null 2>&1
>> 42 08 * * 1-5 ~/.dalarm >/dev/null 2>&1
>> 52 09 * * 1-5 ~/.dalarm >/dev/null 2>&1
>> 40 10 * * 1-5 ~/.dalarm >/dev/null 2>&1
>> 28 11 * * 1-5 ~/.dalarm >/dev/null 2>&1
>> 16 12 * * 1-5 ~/.dalarm >/dev/null 2>&1
>> 57 12 * * 1-5 ~/.dalarm >/dev/null 2>&1
>> 40 14 * * 1-5 ~/.dalarm >/dev/null 2>&1
>> 28 15 * * 1-5 ~/.dalarm >/dev/null 2>&1
>> 17 16 * * 1-5 ~/.dalarm >/dev/null 2>&1
>> #30 16 * * 1-5 ~/.lalarm > /dev/null 2>&1
>> 25 16 * * 1-5 /usr/sbin/poweroff >/dev/null 2>&1
>>
>> #
>> to systemd timers? An easy idiot proof way. The .dalarm script
>> calls mplayer and plays from a playlist.
>
>
> Tangentially, can you get mplayer to make sounds when it's not you
> that runs it? i.e. A system user rather than a real user.
>
>> I have read
https://opensource.com/article/20/7/systemd-timers
>> and
https://www.maketecheasier.com/use-systemd-timers-as-cron-replacement/
>>
>> but have not tried it out. Any help on this is appreciated.
>
>
> You could look at this, too:
>
https://wiki.archlinux.org/title/Systemd/Timers
> Archlinux docs often get good recommendations
>
> NB: I've only just looked at this just now, I've only ever done the
> odd crontab thing a few times. Each time I have to work it out.
>
> --
>
> uname -rsvp
> Linux 3.10.0-1160.59.1.el7.x86_64 #1 SMP Wed Feb 23 16:47:03 UTC 2022 x86_64
>
> Boilerplate: All unexpected mail to my mailbox is automatically deleted.
> I will only get to see the messages that are posted to the mailing list.
Thanks to all who have responded. I am trying it out, but I have it not working. I
created a poweroff.service and poweroff.timer.
[olivares@fedora ~]$ cat /etc/systemd/system/poweroff.service
# /etc/systemd/system/poweroff.service
[Unit]
Description = Poweroff maschine at 16:20 PM Mo-Fri
[Service]
Type=oneshot
ExecStart=sudo systemctl poweroff
[olivares@fedora ~]$ cat /etc/systemd/system/poweroff.
poweroff.service poweroff.timer
[olivares@fedora ~]$ cat /etc/systemd/system/poweroff.timer
# /etc/systemd/system/poweroff.timer
[Unit]
Description=Poweroff maschine at 4:20 PM Mo-Fri
[Timer]
OnCalendar=Mon..Fri *-*-* 16:20:00
Persistent=true
[Install]
WantedBy=timers.target
[olivares@fedora ~]$
and I test it and it did not work. (tested shutdown at 8:20 AM, have changed it to
16:20:00 which is 4:20 pm) What do I need to add?
I had /usr/sbin/poweroff in a crontab, and it too failed. I get the following messages
for attempting to debug.
</snip>
1) systemctl requires a command such as "start"
2) the poweroff.service is calling itself in the ExecStart line.
3) I think sudo shouldn't be necessary since poweroff.service is defined
as a system service which already runs as root.
4) there is already a poweroff.target; I don't know if that presents a
problem/conflict.
5) you might try "/sbin/poweroff -p" as the ExecStart argument
Looks like you're on the right path. Good luck!