It's almost always environment variables. Vern was suggesting putting in absolute paths because the search path (just another environment variable) will usually be different. In my case, Oracle's Instant Client has to have some variables set to tell it where to find certain info.
As an experiment, log in to your machine and just do a "set > interactiveloginvars", then add an entry to your crontab to do a "set > noninteractiveloginvars". Diff the 2 files - I think you'll see a major difference, and I'm guessing that one of those differences is what's causing the problem. Since search paths are very often the problem, have you tried clearing your search path completely and running it in an interactive shell to make sure it still works? I agree that I'm a little baffled that there's nothing going into the log file, though. Can you put some simple echo statements in the script to see where it's dying (or if it's running at all?) Jeremy On Tue, Oct 28, 2008 at 9:49 AM, Simón Ruiz <[EMAIL PROTECTED]> wrote: > Makes sense. > > I've gone though /etc/profile, /etc/bash.bashrc, ~/.bashrc, though, > and nothing jumps out at me as obviously problematic. > > What sorts of things in /etc/profile have owned you on these occasions? > > Simón > > On Fri, Oct 24, 2008 at 11:52 PM, Jeremy Nelson <[EMAIL PROTECTED]> wrote: >> >> Simón, >> >> Maybe the behavior difference is caused an environment variable that's >> set by the login shell when sourcing /etc/profile when you do an >> interactive login. I've gotten owned by that on too many occasions to >> count. >> >> Jeremy > > _______________________________________________ > Fwlug mailing list > [email protected] > http://fortwaynelug.org/mailman/listinfo/fwlug_fortwaynelug.org > -- Jeremy _______________________________________________ Fwlug mailing list [email protected] http://fortwaynelug.org/mailman/listinfo/fwlug_fortwaynelug.org
