diff --git a/docs/Samba-HOWTO-Collection.pdf b/docs/Samba-HOWTO-Collection.pdf index 0813448f2cb..2d9a2009ac3 100644 Binary files a/docs/Samba-HOWTO-Collection.pdf and b/docs/Samba-HOWTO-Collection.pdf differ diff --git a/docs/docbook/manpages/smb.conf.5.sgml b/docs/docbook/manpages/smb.conf.5.sgml index a49ee7cd35d..1567087d9e1 100644 --- a/docs/docbook/manpages/smb.conf.5.sgml +++ b/docs/docbook/manpages/smb.conf.5.sgml @@ -702,6 +702,7 @@ printcap printcap name printer driver file + private dir protocol read bmpx read raw @@ -5116,6 +5117,7 @@ + Default: passdb backend = smbpasswd Example: passdb backend = tdbsam:/etc/samba/private/passdb.tdb @@ -5908,10 +5910,24 @@ [printers] section. + + + + + private dir (G) + This parameters defines the directory + smbd will use for storing such files as smbpasswd + and secrets.tdb. + + Default :private dir = ${prefix}/private + + + + protocol (G) Synonym for diff --git a/docs/docbook/projdoc/Samba-BDC-HOWTO.sgml b/docs/docbook/projdoc/Samba-BDC-HOWTO.sgml index 0dae399654a..53a0959c39a 100644 --- a/docs/docbook/projdoc/Samba-BDC-HOWTO.sgml +++ b/docs/docbook/projdoc/Samba-BDC-HOWTO.sgml @@ -13,7 +13,7 @@ -How to a Purely Samba Controlled Domain +How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain @@ -230,4 +230,4 @@ password. - \ No newline at end of file + diff --git a/docs/docbook/projdoc/printer_driver2.sgml b/docs/docbook/projdoc/printer_driver2.sgml index 4377303ffb2..84a24bcdefc 100644 --- a/docs/docbook/projdoc/printer_driver2.sgml +++ b/docs/docbook/projdoc/printer_driver2.sgml @@ -230,8 +230,10 @@ that all file shares are set to 'read only' by default. Once you have created the required [print$] service and associated subdirectories, simply log onto the Samba server using a root (or printer admin) account -from a Windows NT 4.0 client. Navigate to the "Printers" folder -on the Samba server. You should see an initial listing of printers +from a Windows NT 4.0/2k client. Open "Network Neighbourhood" or +"My Network Places" and browse for the Samba host. Once you have located +the server, navigate to the "Printers..." folder. +You should see an initial listing of printers that matches the printer shares defined on your Samba host. diff --git a/docs/docbook/projdoc/samba-doc.sgml b/docs/docbook/projdoc/samba-doc.sgml index e2fc5a1eb19..28baa7f6094 100644 --- a/docs/docbook/projdoc/samba-doc.sgml +++ b/docs/docbook/projdoc/samba-doc.sgml @@ -31,7 +31,7 @@ Abstract -Last Update : Tue Jul 31 15:58:03 CDT 2001 +Last Update : Mon Apr 1 08:47:26 CST 2002 @@ -43,6 +43,13 @@ on the "Documentation" page. Please send updates to jerry@samba.org. + +This documentation is distributed under the GNU General Public License (GPL) +version 2. A copy of the license is included with the Samba source +distribution. A copy can be found on-line at http://www.fsf.org/licenses/gpl.txt + + Cheers, jerry diff --git a/docs/htmldocs/Samba-BDC-HOWTO.html b/docs/htmldocs/Samba-BDC-HOWTO.html index 0847335fe66..fd83c4e09a3 100644 --- a/docs/htmldocs/Samba-BDC-HOWTO.html +++ b/docs/htmldocs/Samba-BDC-HOWTO.html @@ -1,7 +1,7 @@ How to a Purely Samba Controlled DomainHow to Act as a Backup Domain Controller in a Purely Samba Controlled DomainHow to a Purely Samba Controlled DomainHow to Act as a Backup Domain Controller in a Purely Samba Controlled Domain

Last Update : Tue Jul 31 15:58:03 CDT 2001

: Mon Apr 1 08:47:26 CST 2002

This book is a collection of HOWTOs added to Samba documentation over the years. I try to ensure that all are current, but sometimes the is a larger job @@ -56,6 +56,14 @@ TARGET="_top" >jerry@samba.org.

This documentation is distributed under the GNU General Public License (GPL) +version 2. A copy of the license is included with the Samba source +distribution. A copy can be found on-line at http://www.fsf.org/licenses/gpl.txt

Cheers, jerry

1.1. Step 0: Read the man pages
1.2. Step 1: Building the Binaries
1.3. Step 2: The all important step
1.4. Step 3: Create the smb configuration file.
1.5. Step 4: Test your config file with
1.6. Step 5: Starting the smbd and nmbd
1.6.1. Step 5a: Starting from inetd.conf
1.6.2. Step 5b. Alternative: starting it as a daemon
1.7. Step 6: Try listing the shares available on your server
1.8. Step 7: Try connecting with the unix client
1.9. Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client
1.10. What If Things Don't Work?
1.10.1. Diagnosing Problems
1.10.2. Scope IDs
1.10.3. Choosing the Protocol Level
1.10.4. Printing from UNIX to a Client PC
1.10.5. Locking
1.10.6. Mapping Usernames
1.10.7. Other Character Sets
2.1. Agenda
2.2. Name Resolution in a pure Unix/Linux world
2.2.1. /etc/hosts
2.2.2. /etc/resolv.conf
2.2.3. /etc/host.conf
2.2.4. /etc/nsswitch.conf
2.3. Name resolution as used within MS Windows networking
2.3.1. The NetBIOS Name Cache
2.3.2. The LMHOSTS file
2.3.3. HOSTS file
2.3.4. DNS Lookup
2.3.5. WINS Lookup
2.4. How browsing functions and how to deploy stable and dependable browsing using Samba
2.5. MS Windows security options and how to configure Samba for seemless integration
2.5.1. Use MS Windows NT as an authentication server
2.5.2. Make Samba a member of an MS Windows NT security domain
2.5.3. Configure Samba as an authentication server
2.5.3.1. Users
2.5.3.2. MS Windows NT Machine Accounts
2.6. Conclusions
3.1. Samba and PAM
3.2. Distributed Authentication
3.3. PAM Configuration in smb.conf
4.1. Instructions
4.1.1. Notes
5.1. Viewing and changing UNIX permissions using the NT security dialogs
5.2. How to view file security on a Samba share
5.3. Viewing file ownership
5.4. Viewing file or directory permissions
5.4.1. File Permissions
5.4.2. Directory Permissions
5.5. Modifying file or directory permissions
5.6. Interaction with the standard Samba create mask parameters
5.7. Interaction with the standard Samba file attribute mapping
6.1. Introduction
6.2. Configuration
6.2.1. Creating [print$]
6.2.2. Setting Drivers for Existing Printers
6.2.3. Support a large number of printers
6.2.4. Adding New Printers via the Windows NT APW
6.2.5. Samba and Printer Ports
6.3. The Imprints Toolset
6.3.1. What is Imprints?
6.3.2. Creating Printer Driver Packages
6.3.3. The Imprints server
6.3.4. The Installation Client
6.4.
7.1. Joining an NT Domain with Samba 2.2
7.2. Samba and Windows 2000 Domains
7.3. Why is this better than security = server?
8.1. Prerequisite Reading
8.2. Background
8.3. Configuring the Samba Domain Controller
8.4. Creating Machine Trust Accounts and Joining Clients to the Domain
8.4.1. Manual Creation of Machine Trust Accounts
8.4.2. "On-the-Fly" Creation of Machine Trust Accounts
8.4.3. Joining the Client to the Domain
8.5. Common Problems and Errors
8.6. System Policies and Profiles
8.7. What other help can I get?
8.8. Domain Control for Windows 9x/ME
8.8.1. Configuration Instructions: Network Logons
8.8.2. Configuration Instructions: Setting up Roaming User Profiles
8.8.2.1. Windows NT Configuration
8.8.2.2. Windows 9X Configuration
8.8.2.3. Win9X and WinNT Configuration
8.8.2.4. Windows 9X Profile Setup
8.8.2.5. Windows NT Workstation 4.0
8.8.2.6. Windows NT Server
8.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0
8.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba
9. How to a Purely Samba Controlled DomainHow to Act as a Backup Domain Controller in a Purely Samba Controlled Domain
9.1. Prerequisite Reading
9.2. Background
9.3. What qualifies a Domain Controller on the network?
9.3.1. How does a Workstation find its domain controller?
9.3.2. When is the PDC needed?
9.4. Can Samba be a Backup Domain Controller?
9.5. How do I set up a Samba BDC?
9.5.1. How do I replicate the smbpasswd file?
10.1. Purpose
10.2. Introduction
10.3. Supported LDAP Servers
10.4. Schema and Relationship to the RFC 2307 posixAccount
10.5. Configuring Samba with LDAP
10.5.1. OpenLDAP configuration
10.5.2. Configuring Samba
10.6. Accounts and Groups management
10.7. Security and sambaAccount
10.8. LDAP specials attributes for sambaAccounts
10.9. Example LDIF Entries for a sambaAccount
10.10. Comments
11.1. Abstract
11.2. Introduction
11.3. What Winbind Provides
11.3.1. Target Uses
11.4. How Winbind Works
11.4.1. Microsoft Remote Procedure Calls
11.4.2. Name Service Switch
11.4.3. Pluggable Authentication Modules
11.4.4. User and Group ID Allocation
11.4.5. Result Caching
11.5. Installation and Configuration
11.5.1. Introduction
11.5.2. Requirements
11.5.3. Testing Things Out
11.5.3.1. Configure and compile SAMBA
11.5.3.2. Configure nsswitch.conf
11.5.3.3. Configure smb.conf
11.5.3.4. Join the SAMBA server to the PDC domain
11.5.3.5. Start up the winbindd daemon and test it!
11.5.3.6. Fix the /etc/rc.d/init.d/smb
11.5.3.7. Configure Winbind and PAM
11.6. Limitations
11.7. Conclusion
12.1. FAQs
12.1.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?
12.1.2. How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?
12.1.3. Are there any other issues when OS/2 (any version) is used as a client?
12.1.4. How do I get printer driver download working for OS/2 clients?
13.1. Introduction
13.2. CVS Access to samba.org
13.2.1. Access via CVSweb
13.2.2. Access via cvs
Index

1.1. Step 0: Read the man pages


1.2. Step 1: Building the Binaries


1.3. Step 2: The all important step


1.4. Step 3: Create the smb configuration file.


1.5. Step 4: Test your config file with

1.6. Step 5: Starting the smbd and nmbd


1.6.1. Step 5a: Starting from inetd.conf


1.6.2. Step 5b. Alternative: starting it as a daemon


1.7. Step 6: Try listing the shares available on your server


1.8. Step 7: Try connecting with the unix client


1.9. Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client


1.10. What If Things Don't Work?


1.10.1. Diagnosing Problems


1.10.2. Scope IDs


1.10.3. Choosing the Protocol Level


1.10.4. Printing from UNIX to a Client PC


1.10.5. Locking


1.10.6. Mapping Usernames


1.10.7. Other Character Sets

2.1. Agenda


2.2. Name Resolution in a pure Unix/Linux world


2.2.1. /etc/hosts

2.2.2. /etc/resolv.conf

2.2.3. /etc/host.conf

2.2.4. /etc/nsswitch.conf

2.3. Name resolution as used within MS Windows networking


2.3.1. The NetBIOS Name Cache


2.3.2. The LMHOSTS file


2.3.3. HOSTS file


2.3.4. DNS Lookup


2.3.5. WINS Lookup


2.4. How browsing functions and how to deploy stable and dependable browsing using Samba


2.5. MS Windows security options and how to configure Samba for seemless integration


2.5.1. Use MS Windows NT as an authentication server


2.5.2. Make Samba a member of an MS Windows NT security domain


2.5.3. Configure Samba as an authentication server


2.5.3.1. Users


2.5.3.2. MS Windows NT Machine Accounts


2.6. Conclusions

3.1. Samba and PAM


3.2. Distributed Authentication


3.3. PAM Configuration in smb.conf

4.1. Instructions


4.1.1. Notes

5.1. Viewing and changing UNIX permissions using the NT security dialogs


5.2. How to view file security on a Samba share


5.3. Viewing file ownership


5.4. Viewing file or directory permissions


5.4.1. File Permissions


5.4.2. Directory Permissions


5.5. Modifying file or directory permissions


5.6. Interaction with the standard Samba create mask parameters


5.7. Interaction with the standard Samba file attribute mapping

6.1. Introduction


6.2. Configuration


6.2.1. Creating [print$]

printer admin) account -from a Windows NT 4.0 client. Navigate to the "Printers" folder -on the Samba server. You should see an initial listing of printers +from a Windows NT 4.0/2k client. Open "Network Neighbourhood" or +"My Network Places" and browse for the Samba host. Once you have located +the server, navigate to the "Printers..." folder. +You should see an initial listing of printers that matches the printer shares defined on your Samba host.


6.2.2. Setting Drivers for Existing Printers


6.2.3. Support a large number of printers


6.2.4. Adding New Printers via the Windows NT APW


6.2.5. Samba and Printer Ports


6.3. The Imprints Toolset


6.3.1. What is Imprints?


6.3.2. Creating Printer Driver Packages


6.3.3. The Imprints server


6.3.4. The Installation Client


6.4.

7.1. Joining an NT Domain with Samba 2.2


7.2. Samba and Windows 2000 Domains


7.3. Why is this better than security = server?

8.1. Prerequisite Reading


8.2. Background


8.3. Configuring the Samba Domain Controller


8.4. Creating Machine Trust Accounts and Joining Clients to the Domain


8.4.1. Manual Creation of Machine Trust Accounts


8.4.2. "On-the-Fly" Creation of Machine Trust Accounts


8.4.3. Joining the Client to the Domain


8.5. Common Problems and Errors


8.6. System Policies and Profiles


8.7. What other help can I get?


8.8. Domain Control for Windows 9x/ME


8.8.1. Configuration Instructions: Network Logons


8.8.2. Configuration Instructions: Setting up Roaming User Profiles


8.8.2.1. Windows NT Configuration


8.8.2.2. Windows 9X Configuration


8.8.2.3. Win9X and WinNT Configuration


8.8.2.4. Windows 9X Profile Setup


8.8.2.5. Windows NT Workstation 4.0


8.8.2.6. Windows NT Server


8.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0


8.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba


Chapter 9. How to a Purely Samba Controlled DomainChapter 9. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain

9.1. Prerequisite Reading


9.2. Background


9.3. What qualifies a Domain Controller on the network?


9.3.1. How does a Workstation find its domain controller?


9.3.2. When is the PDC needed?


9.4. Can Samba be a Backup Domain Controller?


9.5. How do I set up a Samba BDC?


9.5.1. How do I replicate the smbpasswd file?

10.1. Purpose


10.2. Introduction


10.3. Supported LDAP Servers


10.4. Schema and Relationship to the RFC 2307 posixAccount


10.5. Configuring Samba with LDAP

10.5.1. OpenLDAP configuration


10.5.2. Configuring Samba


10.6. Accounts and Groups management


10.7. Security and sambaAccount


10.8. LDAP specials attributes for sambaAccounts


10.9. Example LDIF Entries for a sambaAccount


10.10. Comments

11.1. Abstract


11.2. Introduction


11.3. What Winbind Provides


11.3.1. Target Uses


11.4. How Winbind Works


11.4.1. Microsoft Remote Procedure Calls


11.4.2. Name Service Switch


11.4.3. Pluggable Authentication Modules


11.4.4. User and Group ID Allocation


11.4.5. Result Caching


11.5. Installation and Configuration


11.5.1. Introduction


11.5.2. Requirements


11.5.3. Testing Things Out


11.5.3.1. Configure and compile SAMBA


11.5.3.2. Configure nsswitch.conf

11.5.3.3. Configure smb.conf


11.5.3.4. Join the SAMBA server to the PDC domain


11.5.3.5. Start up the winbindd daemon and test it!


11.5.3.6. Fix the /etc/rc.d/init.d/smb

11.5.3.7. Configure Winbind and PAM


11.6. Limitations


11.7. Conclusion

12.1. FAQs


Index

Primary Domain Controller, Background
printer admin) account -from a Windows NT 4.0 client. Navigate to the "Printers" folder -on the Samba server. You should see an initial listing of printers +from a Windows NT 4.0/2k client. Open "Network Neighbourhood" or +"My Network Places" and browse for the Samba host. Once you have located +the server, navigate to the "Printers..." folder. +You should see an initial listing of printers that matches the printer shares defined on your Samba host.

the NetBIOS name of the server. This allows you to change your config based on what the client calls you. Your server can have a "dual personality".

Note that this paramater is not available when Samba listens + on port 445, as clients no longer send this information

%M

NAME MANGLING

NOTE ABOUT USERNAME/PASSWORD VALIDATION

COMPLETE LIST OF GLOBAL PARAMETERS

  • private dir

  • COMPLETE LIST OF SERVICE PARAMETERS

    EXPLANATION OF EACH PARAMETER

    See the discussion in the section NAME MANGLING.

    See the section on NAME MANGLING. Also note the

    Default : large readwrite = nolarge readwrite = yes

    See the section on NAME MANGLING

    See the section on NAME MANGLING for details on how to control the mangling process.

    magic character in name mangling. The default is a '~' but this may interfere with some software. Use this option to set @@ -12647,6 +12662,135 @@ NAME="PASSDBBACKEND" (eg --with-tdbsam) at configure time.

    This paramater is in two parts, the backend's name, and a 'location' + string that has meaning only to that particular backed. These are separated + by a : character.

    Available backends can include: +

    • smbpasswd - The default smbpasswd + backend. Takes a path to the smbpasswd file as an optional argument.

    • smbpasswd_nua - The smbpasswd + backend, but with support for 'not unix accounts'. + Takes a path to the smbpasswd file as an optional argument.

      See also non unix account range

    • tdbsam - The TDB based password storage + backend. Takes a path to the TDB as an optional argument (defaults to passdb.tdb + in the private dir directory.

    • tdbsam_nua - The TDB based password storage + backend, with non unix account support. Takes a path to the TDB as an optional argument (defaults to passdb.tdb + in the private dir directory.

      See also non unix account range

    • ldapsam - The LDAP based passdb + backend. Takes an LDAP URL as an optional argument (defaults to + ldap://localhost)

    • ldapsam_nua - The LDAP based passdb + backend, with non unix account support. Takes an LDAP URL as an optional argument (defaults to + ldap://localhost)

      See also non unix account range

    • plugin - Allows Samba to load an + arbitary passdb backend from the .so specified as a compulsary argument. +

      Any characters after the (optional) second : are passed to the plugin + for its own processing

    +

    Default: passdb backend = smbpasswd

    Example: passdb backend = tdbsampassdb backend = tdbsam:/etc/samba/private/passdb.tdb

    Example: passdb backend = ldapsam_nua:ldaps://ldap.example.com

    Example: passdb backend = plugin:/usr/local/samba/lib/my_passdb.so:my_plugin_args

    See the section on NAME MANGLING for a fuller discussion.

  • private dir (G)

    This parameters defines the directory + smbd will use for storing such files as smbpasswd + and secrets.tdb. +

    Default :private dir = ${prefix}/private

    protocol (G)

    See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.

    parameter for details on doing this.

    See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.

    parameter for details on doing this.

    See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.

    See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.

    See the section on NAME MANGLING.

    See the section NOTE ABOUT USERNAME/PASSWORD VALIDATION for more information on how @@ -18692,7 +18869,7 @@ CLASS="COMMAND" >

    WARNINGS

    VERSION

    SEE ALSO

    AUTHOR

    .\" Please send any bug reports, improvements, comments, patches, .\" etc. to Steve Cheng . -.TH "SMB.CONF" "5" "19 February 2002" "" "" +.TH "SMB.CONF" "5" "01 April 2002" "" "" .SH NAME smb.conf \- The configuration file for the Samba suite .SH "SYNOPSIS" @@ -360,6 +360,9 @@ the NetBIOS name of the client machine the NetBIOS name of the server. This allows you to change your config based on what the client calls you. Your server can have a "dual personality". + +Note that this paramater is not available when Samba listens +on port 445, as clients no longer send this information .TP \fB%M\fR the Internet name of the client machine. @@ -830,6 +833,9 @@ each parameter for details. Note that some are synonyms. \fIprinter driver file\fR .TP 0.2i \(bu +\fIprivate dir\fR +.TP 0.2i +\(bu \fIprotocol\fR .TP 0.2i \(bu @@ -3218,10 +3224,10 @@ supports the new 64k streaming read and write varient SMB requests introduced with Windows 2000. Note that due to Windows 2000 client redirector bugs this requires Samba to be running on a 64-bit capable operating system such as IRIX, Solaris or a Linux 2.4 kernel. Can improve performance by 10% with -Windows 2000 clients. Defaults to off. Not as tested as some other Samba +Windows 2000 clients. Defaults to on. Not as tested as some other Samba code paths. -Default : \fBlarge readwrite = no\fR +Default : \fBlarge readwrite = yes\fR .TP \fBldap admin dn (G)\fR This parameter is only available if Samba has been @@ -4629,9 +4635,64 @@ smbpasswd and tdbsam to be used without a recompile. Only one can be used at a time however, and experimental backends must still be selected (eg --with-tdbsam) at configure time. +This paramater is in two parts, the backend's name, and a 'location' +string that has meaning only to that particular backed. These are separated +by a : character. + +Available backends can include: +.RS +.TP 0.2i +\(bu +\fBsmbpasswd\fR - The default smbpasswd +backend. Takes a path to the smbpasswd file as an optional argument. +.TP 0.2i +\(bu +\fBsmbpasswd_nua\fR - The smbpasswd +backend, but with support for 'not unix accounts'. +Takes a path to the smbpasswd file as an optional argument. + +See also \fInon unix account range\fR +.TP 0.2i +\(bu +\fBtdbsam\fR - The TDB based password storage +backend. Takes a path to the TDB as an optional argument (defaults to passdb.tdb +in the \fIprivate dir\fR directory. +.TP 0.2i +\(bu +\fBtdbsam_nua\fR - The TDB based password storage +backend, with non unix account support. Takes a path to the TDB as an optional argument (defaults to passdb.tdb +in the \fIprivate dir\fR directory. + +See also \fInon unix account range\fR +.TP 0.2i +\(bu +\fBldapsam\fR - The LDAP based passdb +backend. Takes an LDAP URL as an optional argument (defaults to +\fBldap://localhost\fR) +.TP 0.2i +\(bu +\fBldapsam_nua\fR - The LDAP based passdb +backend, with non unix account support. Takes an LDAP URL as an optional argument (defaults to +\fBldap://localhost\fR) + +See also \fInon unix account range\fR +.TP 0.2i +\(bu +\fBplugin\fR - Allows Samba to load an +arbitary passdb backend from the .so specified as a compulsary argument. + +Any characters after the (optional) second : are passed to the plugin +for its own processing +.RE +.PP + Default: \fBpassdb backend = smbpasswd\fR -Example: \fBpassdb backend = tdbsam\fR +Example: \fBpassdb backend = tdbsam:/etc/samba/private/passdb.tdb\fR + +Example: \fBpassdb backend = ldapsam_nua:ldaps://ldap.example.com\fR + +Example: \fBpassdb backend = plugin:/usr/local/samba/lib/my_passdb.so:my_plugin_args\fR .TP \fBpasswd chat (G)\fR This string controls the \fB"chat"\fR @@ -5258,6 +5319,13 @@ This option can be set on a per printer basis See also the discussion in the [printers] section. .TP +\fBprivate dir (G)\fR +This parameters defines the directory +smbd will use for storing such files as \fIsmbpasswd\fR +and \fIsecrets.tdb\fR. + +Default :\fBprivate dir = ${prefix}/private\fR +.TP \fBprotocol (G)\fR Synonym for \fImax protocol\fR. .TP