You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/09/16 16:25:21 UTC
[jira] [Work logged] (TS-3245) getopt doesn't work correctly when
used in plugin chaining
[ https://issues.apache.org/jira/browse/TS-3245?focusedWorklogId=29243&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-29243 ]
ASF GitHub Bot logged work on TS-3245:
--------------------------------------
Author: ASF GitHub Bot
Created on: 16/Sep/16 16:25
Start Date: 16/Sep/16 16:25
Worklog Time Spent: 10m
Work Description: Github user jpeach commented on the issue:
https://github.com/apache/trafficserver/pull/845
@pbchou Please add the version to the ``Backport`` field in the corresponding JIRA.
Issue Time Tracking
-------------------
Worklog Id: (was: 29243)
Time Spent: 1h (was: 50m)
> 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: 1h
> Remaining Estimate: 0h
>
> 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)