[jira] [Commented] (TS-4059) Default value for proxy.config.bin_path does not use value from config.layout
[
https://issues.apache.org/jira/browse/TS-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15047021#comment-15047021
]
Craig Forbes commented on TS-4059:
--
Yes this is the problem, TS_BUILD_BINDIR should be used in
mgmt/RecordsConfig.cc instead of "bin"
We use a custom layout where bindir (in config.layout) is ${prefix}/usr/bin so
the default value does not match the install paths.
> Default value for proxy.config.bin_path does not use value from config.layout
> -
>
> Key: TS-4059
> URL: https://issues.apache.org/jira/browse/TS-4059
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration
>Reporter: Craig Forbes
>Assignee: James Peach
>
> The default value for proxy.config.bin_path defined in RecordsConfig.cc is
> hard coded to "bin".
> The value should be TS_BUILD_BINDIR so the value specified at configure time
> is used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (TS-4059) Default value for proxy.config.bin_path does not use value from config.layout
[
https://issues.apache.org/jira/browse/TS-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15047021#comment-15047021
]
Craig Forbes edited comment on TS-4059 at 12/8/15 4:15 PM:
---
Yes this is the problem, TS_BUILD_BINDIR should be used in
mgmt/RecordsConfig.cc instead of "bin"
We use a custom layout where bindir (in config.layout) is $\{prefix}/usr/bin so
the default value does not match the install paths.
was (Author: cpforbes):
Yes this is the problem, TS_BUILD_BINDIR should be used in
mgmt/RecordsConfig.cc instead of "bin"
We use a custom layout where bindir (in config.layout) is ${prefix}/usr/bin so
the default value does not match the install paths.
> Default value for proxy.config.bin_path does not use value from config.layout
> -
>
> Key: TS-4059
> URL: https://issues.apache.org/jira/browse/TS-4059
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration
>Reporter: Craig Forbes
>Assignee: James Peach
>
> The default value for proxy.config.bin_path defined in RecordsConfig.cc is
> hard coded to "bin".
> The value should be TS_BUILD_BINDIR so the value specified at configure time
> is used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TS-4059) Default value for proxy.config.bin_path does not use value from config.layout
Craig Forbes created TS-4059: Summary: Default value for proxy.config.bin_path does not use value from config.layout Key: TS-4059 URL: https://issues.apache.org/jira/browse/TS-4059 Project: Traffic Server Issue Type: Bug Components: Configuration Reporter: Craig Forbes The default value for proxy.config.bin_path defined in RecordsConfig.cc is hard coded to "bin". The value should be TS_BUILD_BINDIR so the value specified at configure time is used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TS-2937) conf_remap plugin returns an error if the file is empty
Craig Forbes created TS-2937: Summary: conf_remap plugin returns an error if the file is empty Key: TS-2937 URL: https://issues.apache.org/jira/browse/TS-2937 Project: Traffic Server Issue Type: Bug Components: Configuration, Plugins Reporter: Craig Forbes If the conf_remap plugin config file does not have at least one CONFIG line an error occurs and traffic_server exits with an error. For example if the config file is empty or has only comments. Also related, if the file does have at least one CONFIG line all other errors are reported but ignored and does not trigger an error and exit. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TS-2308) includedir in config.layout is not used
Craig Forbes created TS-2308: Summary: includedir in config.layout is not used Key: TS-2308 URL: https://issues.apache.org/jira/browse/TS-2308 Project: Traffic Server Issue Type: Bug Components: Build Reporter: Craig Forbes The includedir is hard coded as $(prefix)/include/ts in: mgmt/api/include/Makefile.am proxy/api/ts/Makefile.am so the value set in config.layout is ignored. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (TS-1564) Logs created via the API in plugins are not rolled
Craig Forbes created TS-1564: Summary: Logs created via the API in plugins are not rolled Key: TS-1564 URL: https://issues.apache.org/jira/browse/TS-1564 Project: Traffic Server Issue Type: Bug Components: Logging Affects Versions: 3.2.0 Reporter: Craig Forbes Priority: Minor Logs created in a plugin via TSTextLogObjectCreate and then have log rolling enabled via TSTextLogObjectRollingEnabledSet are not rolled. To reproduce, in a plugin create a log and then call TSTextLogObjectRollingEnabledSet(log_object, 3) The log is not rolled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1564) Logs created via the API in plugins are not rolled
[ https://issues.apache.org/jira/browse/TS-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Forbes updated TS-1564: - Attachment: trafficserver-roll_files.patch Logs created via the API in plugins are not rolled -- Key: TS-1564 URL: https://issues.apache.org/jira/browse/TS-1564 Project: Traffic Server Issue Type: Bug Components: Logging Affects Versions: 3.2.0 Reporter: Craig Forbes Priority: Minor Attachments: trafficserver-roll_files.patch Logs created in a plugin via TSTextLogObjectCreate and then have log rolling enabled via TSTextLogObjectRollingEnabledSet are not rolled. To reproduce, in a plugin create a log and then call TSTextLogObjectRollingEnabledSet(log_object, 3) The log is not rolled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
