From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Description of problem:
Any attempt by a user that uses tcsh as their shell
to set up an at or batch job fails at job run time.
The error message mailed back says:-
TERM: Undefined variable.
An strace on the atd shows that tcsh appears to be
being started to handle the job.
Setting the SHELL environment variable no longer fixes this
(as in the previous incarnation of this bug). There no longer
appear to be switches to select the run time shell.
This is on a current FC2 system (tried on 3 different boxes,
one a clean install, 2 upgrades from FC1). Selinux is disabled.
This is a reversion after fixes for FC1 detailed in Bug #109587
and Bug #117276
The method of failure is slightly different to the referenced
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Use acount with tcsh shell
2. echo ls | batch
3. Examine email
The problem here is that one of your rc files
(see "FILES" section in man tcsh) is referencing
the $TERM variable, which has not been defined,
causing the execution to terminate.
I created a new user with tcsh as the shell,
without having any rc files, and was able to use
'at' fine, with no errors.
grep TERM ~/.tcshrc ~/.cshrc ~/.login
One of these files will be accessing $TERM before
it has been set.