DECsystem 3100 at atrun batch problem

diamond@tkovoa diamond at tkou02.enet.dec.com
Thu Jun 28 12:31:44 AEST 1990


In article <32670 at ut-emx.UUCP> jwe at emx.utexas.edu (John W. Eaton) writes:
>In article <439 at beguine.UUCP> tmorris at athena.sph.unc.edu
>(Thomas P. Morris) writes: 
>: Jobs submitted via the batch command do not appear to be getting
>: released.  Load average on this machine [is small].
>Take a look at the Ultrix version of the man page for at(1) and look
>for the comments about the files /usr/lib/cron/at.{deny,allow}.

That "answer" does not answer the problem.  If the deny (and/or allow)
lists are not suitably established, then an ordinary user is prevented
from even submitting a batch/at job.  This "feature" seems to work on
the systems our group uses.  (I'm still not sure of the purpose though,
since a user could always "nohup" anything that he can't "batch".)

The problem is that jobs in the batch/at queue do not get executed.
Even when we use "at" instead of "batch", they don't get executed.
The "atrun" command is more like an "atnoop".  At least, this is the
problem our group has.  We don't have sources here.  I plan to submit
an SPR eventually.  However, if anyone else knows the solution, I'd be
glad to be corrected.
-- 
Norman Diamond, Nihon DEC     diamond at tkou02.enet.dec.com
This is me speaking.  If you want to hear the company speak, you need DECtalk.



More information about the Comp.unix.ultrix mailing list