Hello bruce, it works, but I noticed that the crontabs are not updated when changed in the /etc/gl_crontabs.d/ folder.
It seems a copy of the files is created in /tmp/gl_crontabs/crontabs.d/ when the Flint boots.
root@GL-MT6000:/etc/gl_crontabs/crontabs.d# ps w | grep [c]rond
6398 root 1348 S /usr/sbin/crond -f -c /etc/crontabs -l 10
6791 root 1348 S /usr/sbin/crond -f -c /tmp/gl_crontabs -l 10
Works fine after reboot.
By the way, is it intentional that there are two crond running at the same time?
Yeah, it is; gl_crontabs is for, unsurprising, the GL GUI side of things. It's better to use one or the other but not both.
They make some seemingly counter-intuitive development decisions compared to just hooking directly into OWRT. IDK why they seem so intent to reinvent the wheel.
That's also what I initially thought, but then I saw that the other crond also has GL-iNet specific rules?
root@GL-MT6000:~# crontab -l
0 0/10 * * * /usr/bin/lua /usr/share/gl-update-cable-mac.lua time
Oh, probably. I haven't dug into too deeply. Anything I have running GL firmware I tend to treat as an 'appliance' vs getting real work done on pure OWRT.
I'm just not sure how much longer the GL firmware is going to be attractive to you. I think this sentiment also applies here:
... but this really going off topic. I'll back off now. TTYL, I'm sure.
I mean I bought the device because I identified as a SOHO / travel user, but then I started getting curious. Lol.