I'm experiencing a strange problem where occasionally the at command appears to not be running the command I've configured it to run.
For example:
at -t 201510071042 runsomescript <Ctrl-D> runsomescript does not run at 2015/10/07 10:42am, for some reason. Where can I see why at failed to run the command? I'm looking for some kind of log file for the at process.
Also, I am aware at sends mail. Having said that, I'm not getting an email either when at fails to execute the command.
If I run at -lov immediately after submitting the job, I see it in the queue to be ran at the appropriate time.
Additional info as of 2016-02-17
When the at command fails, mail contains the following "Cron Job Failure" message:
Cron: 0481-072 Cannot change to your home directory.
at -l(lower-case ELL) to see if your job made it to the queue. I assume that the contents of at.allow and at.deny are not changing in the interim?at -lovdoes show the job is in the queue, set for the appropriate time. I have no idea what is inat.alloworat.deny; presumably those are global settings? i.e. I'd need root to see them?