[jira] [Updated] (TS-3245) getopt doesn't work correctly when used in plugin chaining

["Sudheer Vinukonda (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sudheer Vinukonda updated TS-3245:
----------------------------------
             Priority: Minor  (was: Major)
    Affects Version/s: 5.1.1
        Fix Version/s: 5.3.0
             Assignee: Sudheer Vinukonda

> getopt doesn't work correctly when used in plugin chaining
> ----------------------------------------------------------
>
>                 Key: TS-3245
>                 URL: https://issues.apache.org/jira/browse/TS-3245
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Plugins
>    Affects Versions: 5.1.1
>            Reporter: Sudheer Vinukonda
>            Assignee: Sudheer Vinukonda
>            Priority: Minor
>             Fix For: 5.3.0
>
>
> When multiple plugins that use getopt are chained, it doesn't work correctly for the subsequent plugins after the first plugin. [~jpeach@apache.org] and [~zwoop] suggested that the getopt globals need to be reset (example, {{optind = opterr = optopt = 0}}) before using it and would be better to do it in the core during plugin loading to keep it simple/transparent from plugin development. 
> Note that, if a plugin itself uses getopt multiple times on different argv's, it would have to reset the globals between them. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)