[
https://issues.apache.org/jira/browse/TS-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758518#comment-13758518
]
Alan M. Carroll commented on TS-2054:
-------------------------------------
It works if you start it the normal way, or you don't enable "wait_for_cache".
The latter is new with 4.0.1 and so hasn't been an issue previously. What I
don't want is for people to file this bug again and again when it doesn't work
mysteriously. If you think it's a livable issue (until someone does the libcap
equivalent on other operating systems), then we should do option (1) and
generate a clear "you fail, because ..." message.
> traffic_server will not bind to a reserved port (<=1024)
> --------------------------------------------------------
>
> Key: TS-2054
> URL: https://issues.apache.org/jira/browse/TS-2054
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Phil Sorber
> Assignee: Phil Sorber
> Priority: Minor
> Fix For: 5.0.0
>
>
> At some point after ea560ce I stopped being able to bind to port 80. It looks
> like I can bind above port 1024 though. Perhaps we are dropping privs before
> binding the port now?
> I used --enable-debug when configuring.
--
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
