Doing some cursory Googles (I don't use at much myself either, except when upgrading salt minions) it seems like atd doesn't log very much at all, unless you run jobs with the -m option. Another suggestion was to wrap the command being run with at in a wrapper to syslog:

ex: 
#!/bin/bash
logger -i -t mycmd Starting
/bin/somecommand
logger -i -t mycmd Completed
exit 0

It looks like you're out of luck for determining what happened in the past, but going into the future either the -m or wrapper options might work for you.



On Fri, Feb 26, 2016 at 1:59 PM, Trevor Cordes <trevor@tecnopolis.ca> wrote:
Is there a way to tell after the fact what command(s) an "at" command ran?
I got an email about an error in a cron job and it appears to be an at
command that was queued up.  The error is suspicious, and I don't remember
queueing this at command (though I do use at from time to time).

I can find in logs that it was atd running it under my user id, but the at
queue is now empty and I can't find a way to retroactively see what
commands/script tried to run.  I'm doing a full fs search on some of the
error strings but I am not hopeful.

Is there a way to find out more about what at ran?  Are there options that
in the future would give me more log/debug output so I can more easily
answer this type of question?
_______________________________________________
Roundtable mailing list
Roundtable@muug.mb.ca
http://www.muug.mb.ca/mailman/listinfo/roundtable