:: ipBLOCKer :: Category blocking using iptables and ipsets

[kvic]

Have you tried as suggested in the Guide

Check the name of super user on your system. If it's other then root, please fix it at /opt/etc/crontab.
As an example, asuswrt(-merlin) uses admin:

sed -i 's/root/admin/g' /opt/etc/crontab

NOTE:
Since entware has the vixie's version and as
@ rhyzhov_al pointed out $USER needs to be part of the job description
i.e.,
0 * * * * $USER scriptcall

The elegant approach would be to as you say having cron.allow

That will fix the system-wide crontab as in /opt/etc/crontab. Thinking back..in fact we don't need per-user crontab in a "single user" environment. So if Entware cron is detected, a job can simply be scheduled by appending to /opt/etc/crontab. It'll be picked up by cron shortly after without bouncing any process.

In case someone insist on per-user cron, here is how-to:

echo admin > /opt/etc/cron.allow
ln -s /opt/etc/cron.allow /opt/var/cron/cron.allow

With the above one-time change, 'crontab -e' and its other command line options shall work in Entware.

 

[spalife]

In case someone insist on per-user cron, here is how-to:

echo admin > /opt/etc/cron.allow
ln -s /opt/etc/cron.allow /opt/var/cron/cron.allow

With the above one-time change, 'crontab -e' and its other command line options shall work in Entware.

Adding a $USER to cron.allow and the soft link are elegant.

@Odkrys  Try this approach.
Do a test after configuration with @kvic's suggested steps to see if crontab is working for $USER.

I have included a quick fix for you, uptake the file and in the .ipBLOCKer.config file add the below
CRON_USER=$USER

Do the above ONLY if vixie's cron needs $USER in the crontab schedule.

You would have to rename the extension of the file from .txt to .sh