At 11:06 2003-10-03 -0700, John Bowling wrote:
/home/myuser//scriptfile: line 9: java: command not found
While you're at it, you should resolve that '//' bit.
When logged into myuser I can manually execute the scriptfile with no errors
including execute the java process with no errors.
Because your user shell startup scripts define an extended path, which
isn't handed to the shell when it is invoked by the MTA. No surprise there
'which java'
Then, ensure the path to that is added in your ~/.procmailrc
The scriptfile has been able to execute grep and sed with no problems.
Because they're in more common path locations.
I have pointers to java in the .alias file.
'which java'
Probably reveals a path which doesn't include the word 'java' (excepting of
course the executable name on the tail end, but that's not part of the
DIRECTORY path).
Does procmail need to have pointers to java somewhere?
No 'pointers', just a valid path - you may not
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail