ASL3 Crontab automation

Archive
1

Migrating over to ASL3 having issues with using the Crontab, is it still used?
tried the following:
00 06 * * * /etc/asterisk/local/ConDis.sh *3(connect to nodenumber)
where ConDis.sh is /usr/bin/asterisk -rx “rpt fun (mynodenumber) $1”
and the node is not connecting
when I run "rpt fun (mynodenumber) *3(connect to nodenumber)
the node connects just fine.
the node also connects and disconnects just fine in Supermon 7.4

does ASL3 us the Crontab or is it in the bottom of the rpt.conf under schedules

2

Cron jobs still work.

root@wa3wco-rpi:~# mkdir -p /etc/asterisk/local
root@wa3wco-rpi:~# cat <<‘EOT’ > /etc/asterisk/local/ConDis.sh
#!/bin/sh
date >> /tmp/ConDis-out.txt
echo $0 $1 >> /tmp/ConDis-out.txt
_EOT_
root@wa3wco-rpi:~# chmod 755 /etc/asterisk/local/ConDis.sh
root@wa3wco-rpi:~# crontab -e (add a line to test the script)
root@wa3wco-rpi:~# crontab -l | grep -v “^#”
* * * * * /etc/asterisk/local/ConDis.sh *312345

wait a few minutes for the cron jobs to exec

root@wa3wco-rpi:~# cat /tmp/ConDis-out.txt
Tue 9 Jul 09:06:01 EDT 2024
/etc/asterisk/local/ConDis.sh *312345
Tue 9 Jul 09:07:01 EDT 2024
/etc/asterisk/local/ConDis.sh *312345

and don’t forget to remove (or update) the crontab line

Remeber to check that the script works on it’s own.

3

check out ham radio crusader on youtube and he shows you how to do it. yes they still work.

5

What is the advantage to using crontab and the condis.sh file method to just using the scheduler in rpt.conf?

6

Easier to get at and change what you need, and you do not have to set 2 different areas for it to work. Straight and simple to the point. For most, it has been a lot easier for controlling it. Why make it harder when you do not need to.

1 Like
7

Clifford, that has been a point of contention for a very long time.
Like well over a decade.
Use what you are comfortable with and works for you.

I tend to use app_rpt system scheduler for stuff related to asterisk that has a live effect.
And cron for anything system or asterisk related that is not / background services.
For me, it's more of a organizational thing.

I have never herd a 'valid' argument otherwise. But I am sure there can be.
A long time ago when cpu and memory were in a pinch if you had much going on, you might have considered how much more you might use shelling to OS and back into asterisk again depending on what you were executing. Really irrelevant now unless you are using a PiZero2 or like device with a lot going on.

1 Like
8

I see using the rpt.conf scheduler stanza requires another change in that it can only trigger macros so you have to create rpt.conf schedule entry and required macros.

Appreciate the replies. Thx guys.

9

It is called working it smarter not harder. That is the main difference