On Wed, Nov 12, 2003 at 09:59:55AM -0800, deb wrote:
At 09:49:17, on 11.12.03:
On Wed, 12 Nov 2003, Deb wrote:
This is almost certainly coming from a command in one of your shell's
startup files. Someone, you or a misguided sysadmin, has placed an
interactive command in a file that's read by non-interactive shells.
Well, maybe. BUT, in the 3 years I've been using procmail filters, I've
never seen a single "TERM: Undefined variable" complaint in my logs
prior to putting in the recipe described in my previous email.
So, gosh, I wonder why?
Maybe you've never invoked a subshell before in your procmail filters?
You'll likely see this in any other kind of program that invokes a
subshell also, not just in procmail.
Check your SHELL variable in your procmail recipe file to make sure
it points to /bin/sh. Also make sure that your shell's rc file doesn't
have interactive commands or that if you do, that you have a quick
exit (ala csh "if (! $?prompt) exit" before a non-interactive shell
can get to them.
Scott
--
Scott Wiersdorf
scott(_at_)perlcode(_dot_)org
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail