[rabbitmq-discuss] Fwd: Port Number

[Dan Simpson]

I didn't reply to the list either.  Thanks for the help all.

On Wed, Aug 26, 2009 at 10:43 PM, Dan Simpson <dan.simpson at gmail.com> wrote:

> Paul.
>
> I was running it from the command line.  I now see: su rabbitmq -s /bin/sh
> -c "/usr/lib/rabbitmq/bin/${SCRIPT} ${CMDLINE}" in the rabbitmq-server
> script.
>
> Thanks for the quick response,
> Dan
>
> On Wed, Aug 26, 2009 at 10:38 PM, Paul Jones <pauljones23 at gmail.com>wrote:
>
>> Hi Dan,
>>
>> How are you running Rabbit? Most systems implement a restriction where
>> only processes run by root can take ports <1024. The  default start scripts
>> for rabbit will actually start Rabbit as a "rabbitmq" user, so in order to
>> take a well-known port, you'd need to alter these scripts.
>>
>> Be warned however that Rabbit doesn't support the features normally
>> required by daemons that use well-known ports, such as the ability to open
>> the port then drop to the context of a less privileged user. This means that
>> a Rabbit running as root will stay running as root.
>>
>> Paul.
>>
>> On Thu, Aug 27, 2009 at 5:37 AM, Dan Simpson <dan.simpson at gmail.com>wrote:
>>
>>> Hello,
>>>
>>> I am having trouble getting rabbitmq to listen on a "well-known" port.  I
>>> am guessing there is some implemented restriction for listening on any port
>>> less than 1024.
>>>
>>> How can I get around this?
>>>
>>> --Dan
>>>
>>> _______________________________________________
>>> rabbitmq-discuss mailing list
>>> rabbitmq-discuss at lists.rabbitmq.com
>>> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>>
>>>
>>
>

On Thu, Aug 27, 2009 at 1:33 AM, Paul Jones <pauljones23 at gmail.com> wrote:

> Oops...
>
> I did reply to Dan, but forgot to CC the list.
>
>
> ---------- Forwarded message ----------
> From: Paul Jones <pauljones23 at gmail.com>
> Date: Thu, Aug 27, 2009 at 6:38 AM
> Subject: Re: [rabbitmq-discuss] Port Number
> To: Dan Simpson <dan.simpson at gmail.com>
>
>
> Hi Dan,
>
> How are you running Rabbit? Most systems implement a restriction where only
> processes run by root can take ports <1024. The  default start scripts for
> rabbit will actually start Rabbit as a "rabbitmq" user, so in order to take
> a well-known port, you'd need to alter these scripts.
>
> Be warned however that Rabbit doesn't support the features normally
> required by daemons that use well-known ports, such as the ability to open
> the port then drop to the context of a less privileged user. This means that
> a Rabbit running as root will stay running as root.
>
> Paul.
>
> On Thu, Aug 27, 2009 at 5:37 AM, Dan Simpson <dan.simpson at gmail.com>wrote:
>
>> Hello,
>>
>> I am having trouble getting rabbitmq to listen on a "well-known" port.  I
>> am guessing there is some implemented restriction for listening on any port
>> less than 1024.
>>
>> How can I get around this?
>>
>> --Dan
>>
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090827/65ad4679/attachment.htm