crontab for ordinary users
Joe Smith
jms at tardis.Tymnet.COM
Sat Oct 20 03:43:40 AEST 1990
In article <1990Oct15.181918.8325 at cubmol.bio.columbia.edu> ping at cubmol.bio.col
umbia.edu (Shiping Zhang) writes:
>Subject: Output from "cron" command
>Your "cron" job "/wholepath/test" produced the following output:
>TERM: Undefined variable.
One common error is when the unsuspecting user puts something like
tset -e^? -k^U -n -s -m dialup:?vt100 -m network:?vt100 $TERM
in their .cshrc file, instead of their .login file where it belongs.
Check to see of your .cshrc file references $TERM anywhere. If you can't
move that command to .login, you can program around it. For instance:
set path=(.. a bunch of stuff ..)
if ($?USER == 0 || $?prompt == 0) exit
set notify mail=(15 /usr/spool/mail/$USER) history=500 savehist=500
alias tset 'eval `\tset -s !*`' # This redefines TERMCAP
The first line is executed whenever csh is invoked for any reason, the
third and fourth only when a human being is connected to it (such as login,
rlogin, or a Sunview window).
--
Joe Smith (408)922-6220 | SMTP: jms at tardis.tymnet.com or jms at gemini.tymnet.com
BT Tymnet Tech Services | UUCP: ...!{ames,pyramid}!oliveb!tymix!tardis!jms
PO Box 49019, MS-C41 | BIX: smithjoe | 12 PDP-10s still running! "POPJ P,"
San Jose, CA 95161-9019 | humorous dislaimer: "My Amiga 3000 speaks for me."
More information about the Comp.unix.sysv386
mailing list