On Mon, 02 Apr 2007 20:35:33 +0100, Andy J. wrote:

> Bit Twister wrote:
>> On Mon, 02 Apr 2007 18:05:05 +0100, Andy J. wrote:
>>
>>> I'm going to try and figure out now why you don't need the
>>> preceding ./ to run the script here as oppose to on the command line.
>>
>> The cron entry requires the location of the script to be executed.
>>
>> When you enter something at the command line, the shell tries to
>> figure out what you want executed.
>>
>> You can execute the script by providing the full path as you did for cron,
>> or put the current directory in your PATH environment variable,
>> or use the period indicating you want to use current directory.
>>
>> To run your script the following will execute your script
>> 1. /home/andrew/goldenpod-0.6/goldenpod
>> 2. $HOME/goldenpod-0.6/goldenpod
>> 3. ~/goldenpod-0.6/goldenpod
>>
>> 4. cd ~/goldenpod-0.6
>> ./goldenpod
>>
>> 5. export PATH=$PATH:.
>> cd ~/goldenpod-0.6
>> goldenpod
>>
>> 6. export PATH=$PATH:$HOME/goldenpod-0.6
>> goldenpod
>>
>> Only 4 and 5 require you to be in the ~/goldenpod-0.6 directory for
>> goldenpod execution from your shell command line.
>
> Oh yeah, I knew that......... :-)
>
> OK, seriously, thanks again BT. I was going to try and figure that out
> but you give a pretty concise answer, all I need to do is go away and
> try and to remember it for the future.

In short the . in ./whatever means starting from here, the directory the
command is isused from.

It is logical.