Thanks, I'm fine with that wording.
--On 6. April 2016 um 12:33:08 +1000 ellie timoney
wrote:
Oh yeah, of course. I've added the following to man/master.8 for future
releases:
Services added or modified to listen on a privileged port may not
be able to bind the port, depending on your sys
Hi Sebastian,
> after thinking about it, I think it's like this: I added a service that
> was
> configured to listen on a privileged port. But master has dropped
> privileges by that point, so it can't add such a listener. I just
> double-checked that I *can* add a listener at run-time if it's
Hi Ellie,
--On 5. April 2016 um 14:33:46 +1000 ellie timoney
wrote:
> Sebastian, is there anything you tried that *didn't* work, and if so,
> what happened?
The only thing I tried that didn't work was to add a IPv6 listener and
to HUP the master process. The manpage for master reads (in my
Hi Sebastian,
> > Sebastian, is there anything you tried that *didn't* work, and if so,
> > what happened?
>
> The only thing I tried that didn't work was to add a IPv6 listener and to
> HUP the master process. The manpage for master reads (in my version):
>
>Cyrus-master rereads its co
Hi Ellie,
--On 29. März 2016 um 12:30:34 +1100 ellie timoney
wrote:
Ellie, can you please fix the listen statement to accept correctly
bracketed ipv6 and backport to at least 2.5 and 2.4, shouldn't be many
changes in that code.
I don't think there's anything to fix here. The code looks fi
> Ellie, can you please fix the listen statement to accept correctly
> bracketed ipv6 and backport to at least 2.5 and 2.4, shouldn't be many
> changes in that code.
I don't think there's anything to fix here. The code looks fine as is,
just docs missing. Unless we want to explicitly *not* accep
Ellie, can you please fix the listen statement to accept correctly bracketed
ipv6 and backport to at least 2.5 and 2.4, shouldn't be many changes in that
code.
Nicola, can you check that we document how it's working now, and of course the
fixed version :)
Bron (on phone in bush somewhere)
On
Hi,
> On Wed, 23 Mar 2016 17:43:30 +0100
> Sebastian Hagedorn said:
> * Parse the "listen" parameter as one of the forms:
> *
> * hostname
> * hostname ':' port
> * ipv4-address
> * ipv4-address ':' port
> * '[' ipv4-address ']'
> * '[' ipv4-address ']' ':' port
> * '[' ipv6-add
--On 24. März 2016 um 01:32:57 +0900 Hajimu UMEMOTO
wrote:
Though it is not mentioned in the manpage, the address:port notation
without bracket is also accepted.
You can find the following comment for parse_inet_listen() in
master/master.c:
* Parse the "listen" parameter as one of the form
Hi,
> On Wed, 23 Mar 2016 16:03:10 +0100
> Sebastian Hagedorn via Info-cyrus said:
info-cyrus> Yes, I do (multi-homed system), and I have just tried it on a test
info-cyrus> system. Using literal IPv6 adresses without brackets works fine,
even
info-cyrus> though it looks strange:
info-
--On 23. März 2016 um 15:41:25 +0100 lst_hoe02--- via Info-cyrus
wrote:
we've been using IPv6 for a few years now, but so far we haven't
used it with Cyrus. Now we want to, and I have a few questions:
Is it correct that if we use host names in the listen statement and
add a record to t
Zitat von Sebastian Hagedorn via Info-cyrus :
Hi,
we've been using IPv6 for a few years now, but so far we haven't
used it with Cyrus. Now we want to, and I have a few questions:
Is it correct that if we use host names in the listen statement and
add a record to the DNS that Cyrus w
Please disregard my previous comment,
misread your original post.
Need coffee.
Eric Luyten.
On Wed, March 23, 2016 3:27 pm, Eric Luyten via Info-cyrus wrote:
<>
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe
On Wed, March 23, 2016 3:13 pm, Sebastian Hagedorn via Info-cyrus wrote:
> Hi,
>
>
> we've been using IPv6 for a few years now, but so far we haven't used it with
> Cyrus. Now we want to, and I have a few questions:
>
>
> Is it correct that if we use host names in the listen statement and add a
> A
14 matches
Mail list logo
