| rfcomm_sppd.1 (121054) | rfcomm_sppd.1 (133178) |
|---|---|
| 1.\" Copyright (c) 2001-2003 Maksim Yevmenkin <m_evmenkin@yahoo.com> 2.\" All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 9 unchanged lines hidden (view full) --- 18.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 19.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 20.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 21.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 22.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 23.\" SUCH DAMAGE. 24.\" 25.\" $Id: rfcomm_sppd.1,v 1.3 2003/09/07 18:15:55 max Exp $ | 1.\" Copyright (c) 2001-2003 Maksim Yevmenkin <m_evmenkin@yahoo.com> 2.\" All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 9 unchanged lines hidden (view full) --- 18.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 19.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 20.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 21.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 22.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 23.\" SUCH DAMAGE. 24.\" 25.\" $Id: rfcomm_sppd.1,v 1.3 2003/09/07 18:15:55 max Exp $ |
| 26.\" $FreeBSD: head/usr.bin/bluetooth/rfcomm_sppd/rfcomm_sppd.1 121054 2003-10-12 22:04:24Z emax $ | 26.\" $FreeBSD: head/usr.bin/bluetooth/rfcomm_sppd/rfcomm_sppd.1 133178 2004-08-05 16:32:41Z emax $ |
| 27.\" 28.Dd April 26, 2003 29.Dt RFCOMM_SPPD 1 30.Os 31.Sh NAME 32.Nm rfcomm_sppd 33.Nd RFCOMM Serial Port Profile daemon 34.Sh SYNOPSIS 35.Nm 36.Op Fl bh | 27.\" 28.Dd April 26, 2003 29.Dt RFCOMM_SPPD 1 30.Os 31.Sh NAME 32.Nm rfcomm_sppd 33.Nd RFCOMM Serial Port Profile daemon 34.Sh SYNOPSIS 35.Nm 36.Op Fl bh |
| 37.Fl a Ar BD_ADDR | 37.Fl a Ar address |
| 38.Fl c Ar channel 39.Fl t Ar tty 40.Sh DESCRIPTION 41The 42.Nm 43utility is a Serial Port Profile daemon. | 38.Fl c Ar channel 39.Fl t Ar tty 40.Sh DESCRIPTION 41The 42.Nm 43utility is a Serial Port Profile daemon. |
| 44It opens RFCOMM connection to the specified server's 45.Ar BD_ADDR 46and | 44It opens RFCOMM connection to the specified 45.Ar address 46server and |
| 47.Ar channel . 48Once connection is established, the 49.Nm 50utility provides access to the server's remote serial port via 51.Xr pty 4 52interface. 53.Pp 54The --- 7 unchanged lines hidden (view full) --- 62The data received from the RFCOMM connection are written 63into master pseudo terminal. 64The application in its turn opens the slave pseudo 65terminal and operates on it just like it would operate over the standard serial 66port. 67.Pp 68The options are as follows: 69.Bl -tag -width indent | 47.Ar channel . 48Once connection is established, the 49.Nm 50utility provides access to the server's remote serial port via 51.Xr pty 4 52interface. 53.Pp 54The --- 7 unchanged lines hidden (view full) --- 62The data received from the RFCOMM connection are written 63into master pseudo terminal. 64The application in its turn opens the slave pseudo 65terminal and operates on it just like it would operate over the standard serial 66port. 67.Pp 68The options are as follows: 69.Bl -tag -width indent |
| 70.It Fl a Ar BD_ADDR 71This required option specifies the remote BD_ADDR of the RFCOMM server. | 70.It Fl a Ar address 71This required option specifies the address of the remote RFCOMM server. 72The address can be specified as BD_ADDR or name. 73If name was specified then the 74.Nm 75utility will attempt to resolve the name via 76.Xr bt_gethostbyname 3 . |
| 72.It Fl b 73Detach from the controlling terminal, i.e., run in background. 74.It Fl c Ar channel 75This option specifies RFCOMM channel to connect to. 76The channel must provide Serial Port service. 77If channel was not specified then 78.Nm 79utility will try to obtain RFCOMM channel via Service Discovery Protocol from --- 22 unchanged lines hidden (view full) --- 102.It Pa /dev/tty[p-sP-S][0-9a-v] 103slave pseudo terminals 104.El 105.Sh DIAGNOSTICS 106.Ex -std 107.Sh BUGS 108Please report if found. 109.Sh SEE ALSO | 77.It Fl b 78Detach from the controlling terminal, i.e., run in background. 79.It Fl c Ar channel 80This option specifies RFCOMM channel to connect to. 81The channel must provide Serial Port service. 82If channel was not specified then 83.Nm 84utility will try to obtain RFCOMM channel via Service Discovery Protocol from --- 22 unchanged lines hidden (view full) --- 107.It Pa /dev/tty[p-sP-S][0-9a-v] 108slave pseudo terminals 109.El 110.Sh DIAGNOSTICS 111.Ex -std 112.Sh BUGS 113Please report if found. 114.Sh SEE ALSO |
| 115.Xr bluetooth 3 , |
|
| 110.Xr ng_btsocket 4 , 111.Xr pty 4 , 112.Xr rfcomm_pppd 8 113.Sh AUTHORS 114.An Maksim Yevmenkin Aq m_evmenkin@yahoo.com | 116.Xr ng_btsocket 4 , 117.Xr pty 4 , 118.Xr rfcomm_pppd 8 119.Sh AUTHORS 120.An Maksim Yevmenkin Aq m_evmenkin@yahoo.com |