From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jan 24 12:11:52 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0868E16A403 for ; Wed, 24 Jan 2007 12:11:52 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from post.rya-online.net (post.rya-online.net [195.26.225.220]) by mx1.freebsd.org (Postfix) with ESMTP id C7EF613C47E for ; Wed, 24 Jan 2007 12:11:51 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from rya-online.net (unknown [217.154.254.216]) by post.rya-online.net (Postfix) with SMTP id 9778A1D4358; Wed, 24 Jan 2007 11:49:37 +0000 (GMT) Received: (nullmailer pid 1567 invoked by uid 1000); Wed, 24 Jan 2007 11:20:18 -0000 Date: Wed, 24 Jan 2007 11:20:18 +0000 (GMT) To: Maksim Yevmenkin In-Reply-To: <1169575182.661050.3030.nullmailer@galant.ukfsn.org> References: <20070112082200.GA67105@old.com.ua> <45A7C992.4040805@savvis.net> <1169575182.661050.3030.nullmailer@galant.ukfsn.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1169637618.976327.1758.nullmailer@galant.ukfsn.org> From: Iain Hibbert Cc: freebsd-bluetooth@freebsd.org Subject: Re: rfcomm_sppd X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 12:11:52 -0000 On Tue, 23 Jan 2007, Iain Hibbert wrote: > Do you recall why you chose to put the slave tty into raw mode? I claim no > expertise over pty(4) but I can't really think why rfcomm_sppd should care > about the slave tty settings? also, regarding the slave tty - I notice that if I do the following % rfcomm_sppd -a phone -c dun -t ttyp9 % cu -l ttyp9 then it works fine, but if I exit cu and try again % cu -l ttyp9 I get a "Device Busy" error. I tracked this down to the fact that cu sets TIOCEXCL but never unsets it. While arguably cu should clean up after itself, I wonder if you really do need to hold open the slave tty? If I don't do that then it works as advertised and I can access the slave as many times as I want with no problems.. regards, iain