Re: Newbie Shell Script Problems

2001-01-29 Thread Colin Watson
David B. Harris <[EMAIL PROTECTED]> wrote: >You should also have "#!/bin/bash" as the first line in your script. "#! >/bin/bash", with the space, is generally not how it's done. It probably >won't case any problems, but it's best to do things the way they're >expected to be done. I always use '#!

Re: Newbie Shell Script Problems

2001-01-29 Thread ktb
On Mon, Jan 29, 2001 at 06:39:40PM +, [EMAIL PROTECTED] wrote: > > > When you run your script, do you need to preface the command with > > ./ > > > > eg ./myscript > > > > took me ages to find out that one! > > Or else add '.' to your PATH, but I think there are security reasons > for not

Re: Newbie Shell Script Problems

2001-01-29 Thread ocorrain
> When you run your script, do you need to preface the command with > ./ > > eg ./myscript > > took me ages to find out that one! Or else add '.' to your PATH, but I think there are security reasons for not doing this. Cheers T >

Re: Newbie Shell Script Problems

2001-01-29 Thread Hall Stevenson
> On Mon, Jan 29, 2001 at 08:03:01AM -0800, thus > spake Tom Schuetz: > > Could someone please give me a hint re. how to get > > a functional shell script? > > > > I've done the #! /bin/bash, and I've chmod'd to +x, > > and the CHMOD shows up correctly as executable > > in ls -l, but still wil

Re: Newbie Shell Script Problems

2001-01-29 Thread Glyn Millington
On Mon, Jan 29, 2001 at 08:03:01AM -0800, thus spake Tom Schuetz: > Could someone please give me a hint re. how to get a functional shell > script? > > I've done the #! /bin/bash, and I've chmod'd to +x, and the CHMOD shows up > correctly as executable in ls -l, but still will not "go". > > Wha

Re: Newbie Shell Script Problems

2001-01-29 Thread David B . Harris
To quote "Tom Schuetz" <[EMAIL PROTECTED]>, # Could someone please give me a hint re. how to get a functional shell # script? # # I've done the #! /bin/bash, and I've chmod'd to +x, and the CHMOD shows up # correctly as executable in ls -l, but still will not "go". If you run 'echo $PATH' from

Re: Newbie Shell Script Problems

2001-01-29 Thread Robert L. Yelvington
;[EMAIL PROTECTED]> > To: > Sent: Monday, January 29, 2001 8:03 AM > Subject: Newbie Shell Script Problems > > > Could someone please give me a hint re. how to get a functional shell > > script? > > > > I've done the #! /bin/bash, and I've chmod

Re: Newbie Shell Script Problems

2001-01-29 Thread Kent West
Tom Schuetz wrote: Could someone please give me a hint re. how to get a functional shell script? I've done the #! /bin/bash, and I've chmod'd to +x, and the CHMOD shows up correctly as executable in ls -l, but still will not "go". What should I check? Thanks, Tom Schuetz _

Re: Newbie Shell Script Problems

2001-01-29 Thread ktb
On Mon, Jan 29, 2001 at 08:03:01AM -0800, Tom Schuetz wrote: > Could someone please give me a hint re. how to get a functional shell > script? > > I've done the #! /bin/bash, and I've chmod'd to +x, and the CHMOD shows up > correctly as executable in ls -l, but still will not "go". > > What sho

Re: Newbie Shell Script Problems

2001-01-29 Thread Leonard Leblanc
What's the exact error message that you are getting? Leonard Leblanc - Original Message - From: Tom Schuetz <[EMAIL PROTECTED]> To: Sent: Monday, January 29, 2001 8:03 AM Subject: Newbie Shell Script Problems > Could someone please give me a hint re. how to get a fu

Newbie Shell Script Problems

2001-01-29 Thread Tom Schuetz
Could someone please give me a hint re. how to get a functional shell script? I've done the #! /bin/bash, and I've chmod'd to +x, and the CHMOD shows up correctly as executable in ls -l, but still will not "go". What should I check? Thanks, Tom Schuetz __