How the command "at" works?

[Karl Auer]

On Sat, 2016-08-06 at 09:34 -0500, Peng Yu wrote:
> I need atd be aware of any bash function defined in the bash shell
> when at is called. I don't think this is possible with the current
> version of at,

No - but the point of my last message was that it is easy to change
at/atd because you have the source code.

I don't understand what you mean by "be aware of any bash function
defined in the bash shell".

Do you mean that there are bash functions defined in your environment,
and you want the at-jobs to be able to call them? I just did a quick
test with sh functions and they do not end up in the atjob. I'd already
discarded my bash mods, so cannot test whether they are passed in the
bash environment - you can test that yourself :-)

If the functions are not passed to atd, there are several ways around
it that do not involve rewriting at/atd, but first tell us if that is
in fact what you want.

And if it is, do you need your atjobs to have ad hoc access to any
functions that happen to be defined by any user that happens to create
them, or do you need your atjobs to have access to a particular set of
functions?

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer at biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: E00D 64ED 9C6A 8605 21E0 0ED0 EE64 2BEE CBCB C38B
Old fingerprint: 3C41 82BE A9E7 99A1 B931 5AE7 7638 0147 2C3C 2AC4