On Wed, 18 Apr 2012 19:23:19 +0200 Wendy Lin wrote:
> On 30 March 2012 08:42, Glenn Fowler <[email protected]> wrote:
> > ast-cmdtst.2012-03-30.tgz md5 e84b44ba46bef61cf68c4d22dddf3b6b
> > source just posted to www.research.att.com/sw/download/beta/
> > it requires nmake to build so
> > you will need either the ast-base or ast-open package installed
> >
> > download ast-cmdtst.2012-03-30.tgz lib/package/tgz
> > bin/package read
> > bin/package use # new ksh with viewpath env ready to build
> > cd cmdtst
> > nmake install
> > nmake test
> >
> > then this line in a ksh script to test
> > builtin -f cmdtst grep egrep fgrep xargs
> >
> > all of the standalone grep and xargs tests pass
> > but the builtin environment could introduce new bug vectors
> Thank you all for your work, input, suggestions, help and testing.
> Are you planning an integration into the ast-ksh package soon? The
> current external module gave use serious headaches when we tried to
> test it because we require superuser privileges to alter production
> software, including scripts, or set an alternative PATH (the scripts
> all override PATH for security).
its still alpha so I wouldn't recommend it for production use
one of the challenges/dangers of builtins/plugins is that they run in
the address space of the main app (ksh here)
the grep builtin was recoded from the standalone grep
standalone apps are (rightfuly so) lax on closing/releasing resources
because _exit(2) does all of that for free
builtins must be meticulous about every resource
its definitely a different mindset
I have some fixes in place that should be ready to post by the end of the week
but there are still (known) issues with { stdin stdout stderr } that
are shared by the builtin and the parent shell
all of these issues will be laid out in a ksh builtin/plugin document
that is being developed as part of the { grep xargs } learning process
now, to answer your question
given that the code as it stands needs a *lot* more testing
it will not become part of -lcmd or ksh proper for a while
if you want to test for production maybe you can set up a (possibly smaller)
shadow copy
of the production environment and run it in parallel and compare results
_______________________________________________
ast-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-users
