I can make them both work, but in each case, it takes several, frustrating workarounds.
AT is a strange duck. I can “at -f someScript now + 2 minutes”, as the documentation allows,
and a proper display is returned. BUT, 5 minutes later, if I do an atq, the jobs in the queue are listed,
and invariably the job submitted is still there, and will remain there. To force it out, I submit
“at -f dummyAt now” which causes the previously submitted job to run.
I do this from the command line in Konsole, as a “regular user”.
CRONTAB will give you heartburn. While AT gives you access to all exported variables, Crontab does not.
For example, **$SHLVL **and the other system, exported variables are accessible in a script that is run by Cron.
But, other variables that I set and export in .bashrc, are not accessible; e.g., $binDir which is my personal bin.
No way! You want it, set it in the script, and a complete path, not a relative one.
Any suggestions will be greatly appreciated and duly researched.