Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 Jun 2005 20:36:46 +0800
From:      Oleg Gritsak <admin@sib-ecometall.ru>
To:        freebsd-hackers@freebsd.org
Subject:   mio_connect specificity
Message-ID:  <20050611123646.GA92781@go.local.sib-ecometall.ru>

next in thread | raw e-mail | index | archive | help

Greetings! Would you, please, help to understand, what's specific
FreeBSD has in a syscall mio_connect? The problem, I've ran into
is - the shutting jabber server. 

In linux this code:

out->fd = mio_connect(s2s->mio, pkt->port, pkt->ip, _out_mio_callback, (void *) out);

doesn't lead to problems, but on my servers (FreeBSD 4.11/5.4) the daemon dies instantly.
It doesn't even write to log, that it is exiting.

The author of Jabber (2.0.8, from latest ports) is probably a linux-user and therefor 
doesn't believe the problem (on FreeBSD) exists. 8-(

p.s. Of course, this problem occures only when peer is unreachable 
(return code 1, Operation not permitted).
 
p.p.s. "Operation not permitted" because of isakmpd.

-- 
системный администратор
ООО "Сиб-ЭкоМеталл"
т. (3912) 60-99-42 (144)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050611123646.GA92781>