Displaying 5 results from an estimated 5 matches for "eai_famili".
Did you mean:
eai_family
2019 Dec 04
4
Dovecot 2.3.9 fails on FreeBSD
On Wed, Dec 04, 2019 at 12:19:35 -0500, Josef 'Jeff' Sipek via dovecot wrote:
> On Wed, Dec 04, 2019 at 18:06:58 +0100, Pascal Christen via dovecot wrote:
> > Hi
> >
> > I've just tried to build the latest Dovecot 2.3.9 on FreeBSD 11.3.
> > Without success...It fails on the following commit which was introduced
> > in 2.3.9:
> >
2015 Aug 31
4
Libvirt resume guest startup issues centos 7
Here is the relevant log snippet:
journal: libvirt version: 1.2.8, package: 16.el7_1.3 (CentOS BuildSystem
<http://bugs.centos.org>, 2015-05-12-20:12:58, worker1.bsys.centos.org)
journal: failed to connect to monitor socket: No such process
journal: internal error: process exited while connecting to monitor:
((null):1937): Spice-Warning **: reds.c:3036:reds_init_socket:
2015 Sep 01
0
Libvirt resume guest startup issues centos 7
On 08/31/2015 03:51 AM, Jason Pyeron wrote:
> journal: internal error: process exited while connecting to monitor:
> ((null):1937): Spice-Warning **: reds.c:3036:reds_init_socket:
> getaddrinfo(127.0.0.1,5900): Address family for hostname not supported
> I feel like this is an issue of libvirt starting before networking
I've looked at this a bit... But, bear in mind that I
2019 Dec 04
0
Dovecot 2.3.9 fails on FreeBSD
I'm working on the port as we type. I've already done this patch (will add
the comments).
On Wed, Dec 4, 2019 at 11:29 AM Josef 'Jeff' Sipek via dovecot <
dovecot at dovecot.org> wrote:
> On Wed, Dec 04, 2019 at 12:19:35 -0500, Josef 'Jeff' Sipek via dovecot
> wrote:
> > On Wed, Dec 04, 2019 at 18:06:58 +0100, Pascal Christen via dovecot
> wrote:
2019 Dec 04
4
Dovecot 2.3.9 fails on FreeBSD
Hi
I've just tried to build the latest Dovecot 2.3.9 on FreeBSD 11.3.
Without success...It fails on the following commit which was introduced
in 2.3.9:
https://github.com/dovecot/core/commit/c85f1bc3ce612c736c9d2c468cc08306db1b5851
Following output is the build log: https://pastebin.com/3nvSeDn8
So I guess it has to do with some changes FreeBSD made:
https://reviews.freebsd.org/D18630