export PATH in script called via Cron.

2009-10-16 Thread Paul Halliday
I have a script that I call via Cron. It wont work unless I include a path: #!/usr/local/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin export $PATH which is fine and works. Out of curiosity though, why is it that if I call it from the cl like ./test.sh I get

Re: export PATH in script called via Cron.

2009-10-16 Thread krad
2009/10/16 Paul Halliday paul.halli...@gmail.com I have a script that I call via Cron. It wont work unless I include a path: #!/usr/local/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin export $PATH which is fine and works. Out of curiosity though, why

export PATH ???

2003-12-09 Thread Xpression
Hi again list, I've posted a question recently about uninstalling packages, in fact, when I installing changin the prefix path (eg.--prefix=/usr/local/package_name) it creates me some subdirs. The trouble is that I can't execute any installed program, until I put, for example: cd

Re: export PATH ???

2003-12-09 Thread Scott W
Xpression wrote: Hi again list, I've posted a question recently about uninstalling packages, in fact, when I installing changin the prefix path (eg.--prefix=/usr/local/package_name) it creates me some subdirs. The trouble is that I can't execute any installed program, until I put, for example: cd

Re: export PATH ???

2003-12-09 Thread staf wagemakers
On Tue, Dec 09, 2003 at 11:06:44AM -0500, Xpression wrote: Hi again list, I've posted a question recently about uninstalling packages, in fact, when I installing changin the prefix path (eg.--prefix=/usr/local/package_name) it creates me some subdirs. The trouble is that I can't execute any