I have a script that creates a series of at jobs for the day.

If I run the script from the command line the at jobs are created. The at jobs run at the specified time and they do what they are supposed to do.

If I run the script the as a cron job the at are created. The at jobs appear to run at the specified time but they do not do anything.

The command that is run from at is

The number at the end is a variable in minutes that says how long to run the script. The number varies for each job and is set by the initial script.

Whether I run the script from the command line or as a cronjob:

When I run atq the all the jobs show up and if I run at -c jobnumber the command shows as above with both full path and the variable.

Everything is run as user.

The initial script can be found here

https://github.com/frrobert2/AWK-scr...ssdailycronjob

So I am confused by what appears to be identical at jobs the ones that are created via cron do not run correctly.

Any ideas?

Thanks

Looking at your code, I'd do at least 2 , maybe 3 things:

1 insert
as a new line 2 ie immediately after #!/bin/bash


2 Set the cronjob to log stdout & stderr eg

3 Ensure ALL cmds & files have the fullpath specified; eg you haven't done that for 'mktemp' or 'date'.
Generally cron has a minimal env, inc cmd paths, so just assume it has none and code accordingly

HTH

1 members found this post helpful.

The default cron path does include /usr/bin which is where mktemp, date and at are located so the OP should be ok but I agree that using the full path is always better.

I simulated your script as much as possible but I don't know anything about issbeacon and created a dummy script that writes data to a file. I modified the time when the at jobs ran so I did not have to wait but I could successfully run the script from cron, the at jobs were created and the test data file showed the correct information.

1 members found this post helpful.

I have made the suggested changes. The cron job ran fine as always and created the at job. The at job runs at roughly 23:00 tonight. I will let you know if the at job runs correctly.

Thank you for the suggestions