[
https://issues.apache.org/jira/browse/TS-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758509#comment-13758509
]
Leif Hedstrom edited comment on TS-2054 at 9/4/13 11:18 PM:
------------------------------------------------------------
How does it work on OmniOS now? I had assumed it works there, no ? This really
feels like one of those "Doctor, it hurts when I lift my arm high above my
head"… If we can't support running traffic_server directly from command line on
OmniOS, it's not the end of the world. I'm assuming it works when started the
normal, blessed way ?
I.e., don't run traffic_server by itself if you enable http.wait_for_cash and
you don't use linux and/or don't have libpcap...
was (Author: zwoop):
How does it work on OmniOS now? I had assumed it works there, no ? This
really feels like one of those "Doctor, it hurts when I lift my arm high above
my head"… If we can't support running traffic_server directly from command line
on OmniOS, it's not the end of the world. I'm assuming it works when started
the normal, blessed way ?
I.e., do run traffic_server by itself if you enable http.wait_for_cash and you
don't use linux and/or don't have libpcap...
> 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
