[erlang-questions] missing LD_LIBRARY_PATH
Wed Oct 15 17:06:39 CEST 2014
We tend to use iptables to get access to privileged ports; saves messing with process permissions which always causes problems like this
Sent from my iPhone
> On 15 Oct 2014, at 16:43, David Welton <davidnwelton@REDACTED> wrote:
> Good guess! I was just writing to say I'd figured out that it's the
> "setcap" we use on Linux to let Erlang listen on port 80.
> That was a nasty one to figure out.
> Now we get to decide what to do... find another way to port 80,
> another place for the libs, or something else.
> Thank you!
>> On Wed, Oct 15, 2014 at 4:25 PM, Jon Schneider <jon@REDACTED> wrote:
>> setuid is one way I can think of for this environment variable to be
>> clobbered though would have thought this would be reflected in the /proc
>> view but maybe it's done in a more hackey way.
>>>> out of interest, does os:getenv() give you LD_LIBRARY_PATH in the list?
>>> No, it doesn't.
>>>> and as a long shot :-() does os:getpid() give you 31960?
>>> David N. Welton
>>> erlang-questions mailing list
> David N. Welton
> erlang-questions mailing list
More information about the erlang-questions