Re: cron on 10.5.2 server

In article <ru2n141sc4cosquiqrhgin3o83uiqc4otq@[EMAIL PROTECTED]
>,
 Howard Brazee <howard@[EMAIL PROTECTED]
> wrote:

> On Fri, 02 May 2008 14:24:50 -0500, Jolly Roger <jollyroger@[EMAIL PROTECTED]
>
> wrote:
> 
> >Personally, I'd just skip TextEdit completely and use a plain text 
> >editor that is designed for editing such files, like TextWrangler,
which 
> >is free anyway, optionally installs an 'edit' command-line tool that 
> >allows TextWrangler to function as a replacement to various
command-line 
> >editors.
> >
> >.bashrc and .bash_profile both belong in your home directory 
> >(/Users/you). So open TextWrangler, and choose File > Open Hidden from 
> >the menu bar to look and see if you already have a ~/.bashrc or 
> >~/.bash_profile.
> 
> On my computer (not the computer of the guy who wanted my help) I
> opened TextWrangler and found a .bash_history and a bash_profile file
> (in HBrazee).   The latter I created myself and it consists of one
> line saying:
> ls
> 
> I was hoping that when I started Terminal, I would see ls run, but
> nothing happens.   So I try running it (obviously incorrectly): 
> 
> Last login: Thu May  1 19:48:45 on console
> bHoward-Brazees-Computer:~ HBrazee$ bash_profile
> -bash: bash_profile: command not found
> Howard-Brazees-Computer:~ HBrazee$ 

You need to learn more about the commind-line environment. ; )

1. The BASH profile file should be named .bash_profile - note the period 
character at the beginning. If the file is not named correctly, and does 
not exist in your home folder, BASH will not read it.

2. Why are you trying to run a script? My instructions showed you how to 
set up .bash_profile and .bashrc - those are not your average, ordinary 
shell scripts - in the sense that the BASH environment looks 
specifically for these files during initialization of your shell 
session. In other words, there are certain things that are appropriate 
to put in these files, and 'ls' isn't one of them. If you want to write 
a script, you really shouldn't use a name like .bash_profile, because 
that name is reserved for BASH in this context. Instead, call it 
something like "my_script.sh". The ".sh" filename extension denotes 
shell scripts.

3. If you create a script file from scratch, chances are it won't be 
executable by you or any other user or group until you make it so. To 
make a script file executable, you would need to issue the 'chmod +x 
/path/to/script' command.

4. To run any executable file (including a shell script) that is not in 
one of the paths listed in your PATH environment variable, you'll need 
to (a) use 'cd' to change to the directory containing the executable 
file, then (b) issue the './scriptname.sh' command to run it from within 
the current directory. Remember, on the command line, . means "the 
current directory, just as .. means "the parent of the current 
directory".

-- 
Please send all responses to the relevant news group. E-mail sent to
this address may be devoured by my very hungry SPAM filter. I do not
read posts from Google Groups. Use a real news reader if you want me to
see your posts.

JR