Am 20.08.2010 18:58, schrieb Stefan G. Weichinger: > I would only like to somehow compare the environment variables, just to > narrow down the reasons ... > > Would crontabbing something like "env >> my_result" work?
Tried that. Big difference. examples: result_crontab:SHELL=/bin/sh result_shell:SHELL=/bin/bash result_crontab:PATH=/usr/bin:/bin result_shell:PATH=/usr/sbin:/usr/local/sbin:/opt/gnome/sbin:/root/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:/opt/gnome/bin:/opt/kde3/bin:/usr/lib/jvm/jre/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:/usr/NX/bin btw, my tar-wrapper calls "#!/bin/sh" not bash. And when I look through it everything is called with a full path, nothing should depend on a correct $PATH. hmmm I now wait for the cronjobbed amdump .... Stefan
