AT command configuration files

[tom quach_1]

dear all,
is there any configuration files that limit "at" command from recursive in seven days.
the reason:we have some jobs that suppose to run in seven days and resubmitted by itself, but it failed to do so.

Thanks in advance.
Regards,
Tom

[A. Clay Stephenson · Accepted solution]

No, I suspect that you have an error in your at command for the next run.

Your syntax should look something like this inside your at'ed script:

at -f /aaa/bbb/mycmd.sh now + 7 days

[James R. Ferguson]

Hi Tom:

If you have an 'at' job that needs to re-schedule itself, you must issue the 'at' command using the absolute path name of the file to rerun. Using '$0' [as one would prefer to do] will not work. The running job is titled "sh".

Regards!

...JRF...

[A. Clay Stephenson]

I would set up a simple script (e.g. something that does an ls -l /home >> filename) and then schedules itself again via at to run at now + 2 minutes and then use the at -l command to see if the jobs are being scheduled. When you get this toy version working, you should have no problem converting your real script.

There is one possible "gotcha" for at and cron jobs and that is the maximum number of jobs that may be run simultaneously. Man queuedefs to see how to modify this but I'm betting that you have a small error in your at'ed script.

[tom quach_1]

Thank you A.Clay and James for your advices.

the AT command works just fine and i was able to test on it. our vendor modified something in their script and it did not run or resummitted the job after seven days. so this is to confirm that there is no configuration that prevent it from running or resummitting jobs after seven days.

Thank you all for your help!
Regards,
Tom