Date: Wed, 24 Jan 2007 11:20:18 +0000 (GMT) From: Iain Hibbert <plunky@rya-online.net> To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: rfcomm_sppd Message-ID: <1169637618.976327.1758.nullmailer@galant.ukfsn.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1169637618.976327.1758.nullmailer>