[ale] How to pass vars to lots of shell scripts?

[leam hall]

Well, this became a little easier now that I figured out a python(*) way to
insert the newer file information. I can do either command line options per
file or whatever.

Still thinking this through.

Leam

* yeah, awk can do the same thing. As can sed. I wanted to stretch my
python-fu a bit.



On Fri, Oct 18, 2013 at 3:56 PM, Phil Turmel <philip at turmel.org> wrote:

> On 10/18/2013 01:03 PM, leam hall wrote:
> > So far, that's what I'm thinking. The process would be:
> >
> > master script zeros out the param file
> > master script takes options given to it and writes to a param file
> > For example:
> >
> > params.sh
> >   TEST=0  # Test for condition, default true
> >   FAIL=1   #  Has not failed yet
> >   FIX=1     #  Default  to do not fix
> >
> > Called script looks something like:
> >
> > . params.sh
>
> There be dragons.
>
> What happens if the master script crashes/fails to clean up and you run
> one of the subordinate scripts?
>
> What happens if you run multiple instances of the master script
> simultaneously (unintentionally, perhaps)?
>
> Environment variables and/or command line arguments are the safe ways to
> do this.  Files are not.  (Pipes are ok too, but can be hard to use for
> this case.)
>
> Phil
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>



-- 
Mind on a Mission <http://leamhall.blogspot.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20131018/9e9a32b5/attachment.html>