Hi Managers,
We have upgraded from an Ultrix system to an AlphaServer running
Digital UNIX 3.2d. The "at" program appears to be broken. When I
try to submit a command to run later, I get this message on the
terminal:
at: no protocol file
This occurs whether running as root or an ordinary user account.
The job appears to be queued anyway, and is reported by the "atq"
command. However, if I look in the queue directory /var/spool/cron/atjobs,
I see that the files in there contain nothing but a list of
"export" commands to export environment variable settings. The
actual command that I was trying to run is not listed in the queue
file! This happens no matter which form of the "at" command I try, e.g.,
at commandfile time
at -f commandfile time
echo 'command' | at time
where "commandfile" is a file containing the command to run, and "command"
is simply the name of the command itself.
Any help with getting "at" to work would be appreciated.
Also, can anyone tell me how often the at queue is actually checked?
UNIX. Under Ultrix, you needed to run the "/usr/lib/atrun" program at
regular intervals from crontab; it would then run the queued up at
commands that were due. There is no such "atrun" program on DUNIX
(that I can find) and no mention or implication in the "at" manual page
that such a program needs to be run. The manual page implies that it
is all handled automatically.
Thanks for any ideas.
-Phil Farrell, Computer Systems Manager
Stanford University School of Earth Sciences
farrell_at_pangea.stanford.edu
Received on Fri Jul 26 1996 - 08:14:25 NZST