On Mar 7, 2016 21:59, "Yehuda Katz" wrote:
>
> On Mon, Mar 7, 2016 at 9:06 PM, William A Rowe Jr
wrote:
>>
>> On Mar 7, 2016 13:54, "Jan Kaluža" wrote:
>> >
>> > On 03/07/2016 04:17 PM, Jim Jagielski wrote:
>> >>
>> >> Intstead of
On Mon, Mar 7, 2016 at 9:06 PM, William A Rowe Jr
wrote:
> On Mar 7, 2016 13:54, "Jan Kaluža" wrote:
> >
> > On 03/07/2016 04:17 PM, Jim Jagielski wrote:
> >>
> >> Intstead of adding YAD (yet another directive ;) ), would it
> >> be possible to somehow
On Mar 7, 2016 13:54, "Jan Kaluža" wrote:
>
> On 03/07/2016 04:17 PM, Jim Jagielski wrote:
>>
>> Intstead of adding YAD (yet another directive ;) ), would it
>> be possible to somehow leverage Listen itself, maybe with some
>> sort of flag?
>
>
> Yes, that would be quite
On 03/07/2016 04:17 PM, Jim Jagielski wrote:
Intstead of adding YAD (yet another directive ;) ), would it
be possible to somehow leverage Listen itself, maybe with some
sort of flag?
Yes, that would be quite possible. I was thinking about that way, but I
have chosen YAD as a first approach.
Intstead of adding YAD (yet another directive ;) ), would it
be possible to somehow leverage Listen itself, maybe with some
sort of flag?
> On Mar 7, 2016, at 6:41 AM, Jan Kaluža wrote:
>
> Hi,
>
> attached patch adds new "FreeListen" directive. The difference between
>
Hi,
attached patch adds new "FreeListen" directive. The difference between
"Listen" and "FreeListen" is that "FreeListen" sets the IP_FREEBIND
socket option on platforms where this is available.
It is therefore possible to start the server even when particular IP
address set in the