that cyrus-master seems to fork the
configured amount of "prefork" daemons twice. One half listening on IPv4 and
the other half on IPv6. Since IPv6 is practically never used from our
frontends they stay forever doing nothing on the backends.
Is there some reasonable way to prevent this
efork" daemons twice. One half listening on IPv4 and
the other half on IPv6. Since IPv6 is practically never used from our
frontends they stay forever doing nothing on the backends.
Is there some reasonable way to prevent this other than setting prefork=0?
I'm only using SERVICE entries lik
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,
On 5. April 2016 um 14:33:46 +1000 ellie timoney <el...@fastmail.com>
> 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
Hi Ellie,
--On 5. April 2016 um 14:33:46 +1000 ellie timoney <el...@fastmail.com>
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.
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):
>
>
Hi Ellie,
--On 29. März 2016 um 12:30:34 +1100 ellie timoney <el...@fastmail.com>
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
> 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 e
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
address ':' port
> * '[' ipv4-address ']'
> * '[' ipv4-address ']' ':' port
> * '[' ipv6-address ']'
> * '[' ipv6-address ']' ':' port
The `ipv6-address ':' port' notation is also accepted. However, it is
not mentioned even in the comment.
Hagedorn> Thank you! Perhaps that should go
quot;listen" parameter as one of the forms:
*
* hostname
* hostname ':' port
* ipv4-address
* ipv4-address ':' port
* '[' ipv4-address ']'
* '[' ipv4-address ']' ':' port
* '[' ipv6-address ']'
* '[' ipv6-address ']' ':' port
info-cyrus> I will now try a host name with bot A and records
Hi,
>>>>> On Wed, 23 Mar 2016 16:03:10 +0100
>>>>> Sebastian Hagedorn via Info-cyrus <info-cyrus@lists.andrew.cmu.edu> said:
info-cyrus> Yes, I do (multi-homed system), and I have just tried it on a test
info-cyrus> system. Using literal IPv6 adress
--On 23. März 2016 um 15:41:25 +0100 lst_hoe02--- via Info-cyrus
<info-cyrus@lists.andrew.cmu.edu> 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
Zitat von Sebastian Hagedorn via Info-cyrus <info-cyrus@lists.andrew.cmu.edu>:
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
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
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
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 will automatically listen to both the
IPv4
17 matches
Mail list logo