Package: at
Version: 3.1.10
We have been using the "batch" command in a production environment for
years. We discovered today that the "batch" command, which is simply a
script that calls the "at" command with arguments, had been changed in a
way that renders it useless.
Here is the present batch script in version 3.1.10:
#! /bin/sh -e
if [ "$#" -gt 0 ]; then
echo batch accepts no parameters
exit 1
fi
prefix=/usr
exec_prefix=${prefix}
exec ${exec_prefix}/bin/at -qb now
Here is the previous batch script in version 3.1.8-11:
#! /bin/sh
prefix=/usr
exec_prefix=${prefix}
exec ${exec_prefix}/bin/at -qb now "$@"
Since the batch script will now accept no arguments, then what can it
possibly do ? Nothing !
The purpose of a batch script is to "submit a job" to a queue for
running in the background. By removing this capability, the batch
command is presently rendered useless.
As a workaround, we have placed the old batch command of v3.1.8-11
into /usr/local/bin/ so that we can still use it above the delivered one
with v3.1.10.
Also, I agree that the reason for the change (bug report #70988) fixes
the man page to match what batch does. However, I think that a more
versatile batch is needed or just remove batch altogether.
--
James D. Freels, Ph.D.
Oak Ridge National Laboratory
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
