On Fri, Oct 5, 2012 at 11:59 AM, Bruce Dubbs <[email protected]> wrote:
> Cory Cline wrote:
>
>>> Well I ran the exact same script file this morning I had been all
>>> along to recap on the errors and start fresh, and it worked. So thank
>>> the gods, is there a way to mark this resolved? Thanks for your help
>>> :)
>>
>> Well it only worked because I forgot to be in a bash -e
>> shell.....might want to look into this further, When I realized that
>> and ran it in the bash -e shell it has the same problem
>
> Try to trim your posts so only relevant info is included.
>
> Are you sure you didn't do 'bash -r'? The r is right next to the e on
> the keyboard and changing directories is not permitted in a restricted
> shell.
>
> Using bash -e works fine. At least no one else has had an issue and the
> construct has been there for quite some time.
>
> -- Bruce
>
>
>
> --
Will do on the trimming. I ran "sh file.sh | grep error" (file.sh is
the name of the for script. I ran this outside of the bash -e (Yes,
Im sure it is -e that I am using) so that I could see where the error
was coming in. It seems that it is erroring on the first commented
line in my proto-7.7.md5 script. Is there any reason that it would
ignore the #?
> http://linuxfromscratch.org/mailman/listinfo/blfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
