[ https://issues.apache.org/jira/browse/TS-3245?focusedWorklogId=26707&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26707 ]
ASF GitHub Bot logged work on TS-3245: -------------------------------------- Author: ASF GitHub Bot Created on: 20/Aug/16 02:57 Start Date: 20/Aug/16 02:57 Worklog Time Spent: 10m Work Description: Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/845 Linux build *successful*! See https://ci.trafficserver.apache.org/job/Github-Linux/463/ for details. Issue Time Tracking ------------------- Worklog Id: (was: 26707) Time Spent: 40m (was: 0.5h) > 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: Peter Chou > Priority: Minor > Labels: newbie > Fix For: 7.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > When multiple plugins that use getopt are chained, it doesn't work correctly > for the subsequent plugins after the first plugin. [~jpe...@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)