From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marcel Holtmann To: BlueZ development In-Reply-To: References: Date: Tue, 26 Sep 2006 23:11:16 +0200 Message-Id: <1159305076.800.43.camel@localhost> Mime-Version: 1.0 Subject: Re: [Bluez-devel] Bug in RFCOMM (or BT general) socket layer Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net Hi Peter, > if you use a non blocking RFCOMM socket (have not tested other types) > connect(..) returns EAGAIN. According to the socket documentation > it shall return EINPROGRESS. > > However, beside of this connect(..) works as expected. starting with 2.6.18-mh3 this should be fixed now. Regards Marcel ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel