On Sep 28, 2009, at 4:20 PM, Ethan Mallove wrote:
I was commenting on both r1304 and r1319.
These INI params:
on_start
on_stop
are very similar to these INI params:
after_each_exec
before_any_exec
after_all_exec
My thought was that it would make sense for them to use a similar
nam
On Fri, Sep/25/2009 04:59:11PM, Jeff Squyres wrote:
> I'm not sure what you mean -- I thought they added a funclect, not a
> field...?
I was commenting on both r1304 and r1319.
These INI params:
on_start
on_stop
are very similar to these INI params:
after_each_exec
before_any_exec
On Fri, Sep 25, 2009 at 10:08 PM, Jeff Squyres wrote:
> On Sep 24, 2009, at 12:46 PM, Mike Dubman wrote:
>
> Im not familiar with :\n semantics, how does it force Bourne shell and
>> what it actually does :)? (seems like leftovers from 1960)
>>
>
> Yes, it might be left over from 1960. :-)
I'm not sure what you mean -- I thought they added a funclect, not a
field...?
On Sep 24, 2009, at 3:09 PM, Ethan Mallove wrote:
I think on_stop should conform more to these params:
after_each_exec
before_any_exec
after_all_exec
E.g.,
before_mtt_start_exec
after_mtt_start_exec
T
On Sep 24, 2009, at 12:46 PM, Mike Dubman wrote:
Im not familiar with :\n semantics, how does it force Bourne shell
and what it actually does :)? (seems like leftovers from 1960)
Yes, it might be left over from 1960. :-) But the nice thing is that
you then don't have to identify /bin/
I think on_stop should conform more to these params:
after_each_exec
before_any_exec
after_all_exec
E.g.,
before_mtt_start_exec
after_mtt_start_exec
Then have &_process_get_value_option() call DoCommand. Note, DoCommand
is aware of hashbangs (see &_contains_shell_script_characters()),
Hey Jeff,
On Thu, Sep 24, 2009 at 4:02 PM, Jeff Squyres wrote:
> The DoCommand.pm sub added ":\n" to the beginning to force the Bourne shell
> interpreter. This is necessary for some cases where an interpreter is not
> otherwise specified.
>
Im not familiar with :\n semantics, how does it forc
I'm not sure this is right.
The DoCommand.pm sub added ":\n" to the beginning to force the Bourne
shell interpreter. This is necessary for some cases where an
interpreter is not otherwise specified.
I see why you did it -- you want the ability to add your own
interpreter in &shell_script
