diff options
author | ru <ru@FreeBSD.org> | 2004-06-04 19:22:04 +0000 |
---|---|---|
committer | ru <ru@FreeBSD.org> | 2004-06-04 19:22:04 +0000 |
commit | c78a480d1f10914b2c6dfcb1c8bb171749660496 (patch) | |
tree | 953d9e8d85f1db49842c82ab81f425fd609bd7ea /usr.sbin | |
parent | d539cb328c017886fd2b620b5743752dd940aefe (diff) | |
download | FreeBSD-src-c78a480d1f10914b2c6dfcb1c8bb171749660496.zip FreeBSD-src-c78a480d1f10914b2c6dfcb1c8bb171749660496.tar.gz |
Reapply some lost fixes, fix some more.
Diffstat (limited to 'usr.sbin')
-rw-r--r-- | usr.sbin/bluetooth/rfcomm_pppd/rfcomm_pppd.8 | 28 |
1 files changed, 15 insertions, 13 deletions
diff --git a/usr.sbin/bluetooth/rfcomm_pppd/rfcomm_pppd.8 b/usr.sbin/bluetooth/rfcomm_pppd/rfcomm_pppd.8 index 2617212..2369242 100644 --- a/usr.sbin/bluetooth/rfcomm_pppd/rfcomm_pppd.8 +++ b/usr.sbin/bluetooth/rfcomm_pppd/rfcomm_pppd.8 @@ -55,7 +55,7 @@ It can operate in two modes: client and server. .Pp In the client mode, .Nm -opens a RFCOMM connection to the specified server's +opens an RFCOMM connection to the specified server's .Ar BD_ADRR and .Ar channel . @@ -76,7 +76,7 @@ and connect to the Internet. .Pp In the server mode, .Nm -opens a RFCOMM socket and listens for incomming connections from remote clients. +opens an RFCOMM socket and listens for incomming connections from remote clients. Once the new incomming connection is accepted, .Nm forks and executes @@ -93,7 +93,7 @@ the standard serial port thus providing network connectivity to remote clients. The options are as follows: .Bl -tag -width indent .It Fl a Ar BD_ADDR -In the client mode this required option specifies the remote BD_ADDR of the +In the client mode, this required option specifies the remote BD_ADDR of the RFCOMM server. In the server mode, this option can be used to specify the local BD_ADDR to listen on. @@ -101,32 +101,33 @@ By default, server will listen on .Dv ANY address. .It Fl C Ar channel -In both client and server modes this required option specifies RFCOMM channel +In both client and server modes, this required option specifies RFCOMM channel to connect to or listen on. -In the server mode RFCOMM channel should be number between 1 and 30. -In the client mode RFCOMM channel could be either number between 1 and 30 or -service name. Supported service names are: +In the server mode, RFCOMM channel should be a number between 1 and 30. +In the client mode, RFCOMM channel could either be a number between 1 and 30 +or a service name. +Supported service names are: .Cm DUN -for DialUp Networking service and +(for DialUp Networking service) and .Cm LAN -for LAN Access Using PPP service. +(for LAN Access Using PPP service). If service name was specified instead of numeric RFCOMM channel then .Nm utility will try to obtain RFCOMM channel for the service via Service Discovery Protocol. .It Fl c -Act as a RFCOMM client. +Act as an RFCOMM client. This is the default mode. .It Fl d Do not detach from the controlling terminal, i.e., run in foreground. .It Fl h Display usage message and exit. .It Fl l Ar label -In both client and server modes this required option specifies which +In both client and server modes, this required option specifies which .Xr ppp 8 label will be used. .It Fl s -Act as a RFCOMM server. +Act as an RFCOMM server. .It Fl u Ar N This option maps directly onto .Fl unit @@ -288,7 +289,8 @@ label. The .Nm utility in server mode will try to register Bluetooth LAN Access Over PPP -service with local SPD daemon. If local SDP daemon is not running the +service with local SPD daemon. +If local SDP daemon is not running the .Nm utility will exit with error. .Sh SEE ALSO |