GitHub user pbchou opened a pull request:

    https://github.com/apache/trafficserver/pull/845

    TS-3245: Allow multiple plugins to safely use getopt(3).

    Request back-port to 6.2.x branch. This was cherry-picked from "master", 
and it was clean except for some spacing issues introduced by clang-format 
setting changes.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/pbchou/trafficserver TS-3245-backport-6.2.x

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/845.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #845
    
----
commit 92b20a567bf8e0df3621f00f8e81f2bfd2e39078
Author: Peter Chou <pbc...@labs.att.com>
Date:   2016-06-06T23:31:43Z

    TS-3245: Allow multiple plugins to safely use getopt(3).
    
    Allow multiple global plugins to co-exist in the plugin.config
    file. Also, made the same changes to allow remap plugins
    to co-exist with each other in the remap.config file.
    
    Specifically, on freebsd and darwin platforms we use 'optreset =
    1' to reset the getopt_long() command line parser.  On Linux/glibc
    we use 'optind = 0' to reset the parser.  The parser must be reset
    between uses such as first loading one plugin and then another.
    
    The setting of these variables is now performed in ATS core before
    the plugin initialization functions are called. The setting of these
    variables inside of the individual plugins has been removed. If a
    plugin needs to call getopt_long() outside of the plugin global or
    remap intializations, it should use the code in proxy/Plugin.cc as
    an example.
    
    Back-ported from "master" [7.0.0] branch.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to