From f58ac61fb10a96f2a3241e6b87b1e51b58687630 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Sat, 3 Dec 2005 02:25:59 +0000 Subject: [PATCH] Updating documentation of tdb files some more. (This used to be commit 9d530b84d791feaeb1a77bca37e91557adf86f14) --- docs/Samba3-HOWTO/TOSHARG-CUPS-printing.xml | 2 +- docs/Samba3-HOWTO/TOSHARG-Install.xml | 187 +++++++++++++++++++++++++ docs/Samba3-HOWTO/TOSHARG-PDC.xml | 2 +- docs/Samba3-HOWTO/TOSHARG-Printing.xml | 2 +- docs/Samba3-HOWTO/TOSHARG-TheNetCommand.xml | 8 +- docs/Samba3-HOWTO/TOSHARG-upgrading-to-3.0.xml | 100 +++++++++---- 6 files changed, 269 insertions(+), 32 deletions(-) diff --git a/docs/Samba3-HOWTO/TOSHARG-CUPS-printing.xml b/docs/Samba3-HOWTO/TOSHARG-CUPS-printing.xml index 081fd597ba7..e76aeeae7d8 100644 --- a/docs/Samba3-HOWTO/TOSHARG-CUPS-printing.xml +++ b/docs/Samba3-HOWTO/TOSHARG-CUPS-printing.xml @@ -2366,7 +2366,7 @@ Windows. The CUPS driver is derived from the Microsoft one. In an attempt to work around problems, site administrators have resorted to restricting the allowed drivers installed on their WTS to one generic PCL and one PostScript driver. This, however, restricts -the the number of printer options available for clients to use. Often they can't get out more than simplex +the number of printer options available for clients to use. Often they can't get out more than simplex prints from one standard paper tray, while their devices could do much better if driven by a different driver! diff --git a/docs/Samba3-HOWTO/TOSHARG-Install.xml b/docs/Samba3-HOWTO/TOSHARG-Install.xml index c8655c91fb9..769e0b10cf7 100644 --- a/docs/Samba3-HOWTO/TOSHARG-Install.xml +++ b/docs/Samba3-HOWTO/TOSHARG-Install.xml @@ -119,6 +119,193 @@ + + TDB Database File Information + + + This section contains brief descriptions of the databases that are used by Samba-3. + + + +tdb file locations + The directory in which Samba stores the tdb files is determined by compile-time directives. Samba-3 stores + tdb files in two locations. The best way to determine these locations is to execute the following + command: + +&rootprompt; smbd -b | grep PRIVATE_DIR + PRIVATE_DIR: /etc/samba/private + + This means that the confidential tdb files are stored in the /etc/samba/private + directory. Samba-3 also uses a number of tdb files that contain more mundane data. The location of + these files can be found by executing: + +&rootprompt; smbd -b | grep LOCKDIR + LOCKDIR: /var/lib/samba + + Therefore the remaining control files will, in the example shown, be stored in the + /var/lib/samba directory. + + + +tdb file descriptions + The persistent tdb files are described in the Persistent TDB File + Descriptions table. All persistent tdb files should be regularly backed up. Use the + tdbbackup utility to backup the tdb files. All persistent tdb files must be + preserved during machine migrations, updates and upgrades. + + + + The temporary tdb files do not need to be backed up, nor do they need to be preseved across machine + migrations, updates or upgrades. The temporary tdb files are described in + the Temporary TDB File Descriptions. + + + Persistent TDB File Descriptions + + + + + + + Name + Description + + + + + account_policy + User policy settings. + + + group_mapping + Mapping table from Windows groups/SID to UNIX groups. + + + ntdrivers + Stores per-printer driver information. + + + ntforms + Stores per-printer forms information. + + + ntprinters + Stores the per-printer devmode configuration settings. + + + passdb + + Exists only when the tdbsam passwd backend is used. This file stores the + SambaSAMAccount information. Note: This file requires that user POSIX account information is + availble from either the /etc/passwd file, or from an alternative system source. + + + + registry + + Read-only Samba registry skeleton that provides support for exporting various database tables + via the winreg RPCs. + + + + secrets + + This file stores the Workgroup/Domain/Machine SID, the LDAP directory update password, and + a further collection of critical environmental data that is necessary for Samba to operate + correctly. This file contains very sensitive information that must be protected. It is stored + in the PRIVARE_DIR directory. + + + + share_info + Stores per-share ACL information. + + + winbindd_idmap + New ID map table from SIDS to UNIX UIDs/GIDs. + + + +
+ + Temporary TDB File Descriptions + + + + + + + Name + Description + Backup + + + + + brlock + Byte-range locking information. + No + + + connections + A temporary cache for current connection information. + no + + + gencache + Generic caching database for dead WINS servers and trusted domain data. + no + + + login_cache + A temporary cache for login information. + no + + + messages + Temporary storage of messages being processed by smbd. + no + + + netsamlogon_cache + Packets received for which no process is listening. + no + + + printing/*.tdb + Cached output from lpq command created on a per-print-service basis. + no + + + schannel_store + + A confidential file, stored in the PRIVATE_DIR, containing crytographic connection + information so that clients that have temporarily disconnected can reconnect without + needing to renegotiate the connection setup process. + + no + + + sessionid + Temporary cache for miscellaneous session information. + no + + + unexpected + Stores packets received for which no process is actively listening. + no + + + winbindd_cache + Cache of Identity information received from an NT4 domain or from ADS. + yes + + + +
+ + + Starting Samba diff --git a/docs/Samba3-HOWTO/TOSHARG-PDC.xml b/docs/Samba3-HOWTO/TOSHARG-PDC.xml index 715c92710cb..31a828b83ed 100644 --- a/docs/Samba3-HOWTO/TOSHARG-PDC.xml +++ b/docs/Samba3-HOWTO/TOSHARG-PDC.xml @@ -550,7 +550,7 @@ time choices offered are: promote Algin Technology LLC provide a commercial tool that makes it possible to promote a Windows NT4 standalone -server to a PDC or a BDC, and also permits this process to be reversed. Refer the the Algin web site for further information. diff --git a/docs/Samba3-HOWTO/TOSHARG-Printing.xml b/docs/Samba3-HOWTO/TOSHARG-Printing.xml index 2ccb953d56b..1cf35fb7c4f 100644 --- a/docs/Samba3-HOWTO/TOSHARG-Printing.xml +++ b/docs/Samba3-HOWTO/TOSHARG-Printing.xml @@ -2978,7 +2978,7 @@ not be disabled. The Installation Client -More information regarding the Imprints installation client is available from the the documentation file +More information regarding the Imprints installation client is available from the documentation file Imprints-Client-HOWTO.ps that is included with the Imprints source package. The Imprints installation client comes in two forms: diff --git a/docs/Samba3-HOWTO/TOSHARG-TheNetCommand.xml b/docs/Samba3-HOWTO/TOSHARG-TheNetCommand.xml index 2ca199c1327..a7cd9d457ee 100644 --- a/docs/Samba3-HOWTO/TOSHARG-TheNetCommand.xml +++ b/docs/Samba3-HOWTO/TOSHARG-TheNetCommand.xml @@ -1617,7 +1617,7 @@ net rpc share MIGRATE ALL <share-name> -S <source> The installation of a new server, as with the migration to a new network environment, often is similar to building a house; progress is very rapid from the laying of foundations up to the stage at which - the the house can be locked up, but the finishing off appears to take longer and longer as building + the house can be locked up, but the finishing off appears to take longer and longer as building approaches completion. @@ -1830,8 +1830,8 @@ net ads printer search <printer_name> -Uadministrator%secret net idmap dump <full_path_and_tdb_filename> > dumpfile.txt - Where the Samba run-time tdb files are stored in the /var/lib/samba directory - the the following commands to create the dump file will suffice: + Where a particular build of Samba the run-time tdb files are stored in the + /var/lib/samba directory the following commands to create the dump file will suffice: net idmap dump /var/lib/samba/winbindd_idmap.tdb > idmap_dump.txt @@ -1848,7 +1848,7 @@ net idmap dump /var/lib/samba/winbindd_idmap.tdb > idmap_dump.txt net idmap restore <full_path_and_tdb_filename> < dumpfile.txt Where the Samba run-time tdb files are stored in the /var/lib/samba directory - the the following command can be used to restore the data to the tdb file: + the following command can be used to restore the data to the tdb file: net idmap restore /var/lib/samba/winbindd_idmap.tdb < idmap_dump.txt diff --git a/docs/Samba3-HOWTO/TOSHARG-upgrading-to-3.0.xml b/docs/Samba3-HOWTO/TOSHARG-upgrading-to-3.0.xml index aada0978d83..057e72b10a2 100644 --- a/docs/Samba3-HOWTO/TOSHARG-upgrading-to-3.0.xml +++ b/docs/Samba3-HOWTO/TOSHARG-upgrading-to-3.0.xml @@ -395,23 +395,38 @@ In alphabetical order, these are the parameters eliminated from Samba-2.2.x thro New Functionality + +major changes + The major changes in behavior since that Samba-2.2.x series are documented in this section. + Please refer to the WHATSNEW.txt file that ships with every release of + Samba to obtain detailed information regarding the changes that have been made during the + life of the current Samba release. + + - Databases + TDB Data Files + +tdb data files + + Refer to Installation, Chapter 1, Chapter 1 + for information pertaining to the Samba-3 data files, their location and the information that must be + preserved across server migrations, updates and upgrades. + - This section contains brief descriptions of any new databases - introduced in Samba-3. Please remember to back up your existing - ${lock directory}/*tdb before upgrading to Samba-3. Samba will - upgrade databases as they are opened (if necessary), but downgrading - from 3.0 to 2.2 is an unsupported path. +tdb file backup + Please remember to back up your existing ${lock directory}/*tdb before upgrading to Samba-3. If necessary, Samba will + upgrade databases as they are opened. Downgrading from Samba-3 to 2.2, or reversion to an earlier version + of Samba-3 from a later release, is an unsupported path. - The new tdb files are described in the next table. +tdb file descriptions + The old Samba-2.2.x tdb files are described in the next table. - TDB File Descriptions +
Samba-2.2.x TDB File Descriptions @@ -430,43 +445,78 @@ In alphabetical order, these are the parameters eliminated from Samba-2.2.x thro yes - gencache - Generic caching db + brlock + Byte-range file locking information. no - group_mapping - Mapping table from Windows groups/SID to UNIX groups - yes - - - idmap - New ID map table from SIDS to UNIX UIDs/GIDs - yes + connections + Client connection information + no - namecache - Name resolution cache entries + locking + Temporary file locking data. no - netlogon_unigrp - Cache of universal group membership obtained when operating - as a member of a Windows domain + messages + Temporary storage of messages being processed by smbd. no + + ntdrivers + Stores per-printer driver information. + yes + + + ntforms + Stores per-printer forms information. + yes + + + ntprinters + Stores the per-printer devmode configuration settings. + yes + printing/*.tdb - Cached output from lpq command created on a per-print-service basis + Cached output from lpq command created on a per-print-service basis. no registry Read-only Samba registry skeleton that provides support for - exporting various database tables via the winreg RPCs + exporting various database tables via the winreg RPCs. + no + + + sessionid + Temporary cache for miscellaneous session information. no + + share_info + Share ACL settings. + yes + + + + unexpected + Packets received for which no process was listening. + no + + + winbindd_cache + Cache of identity information received from an NT4 or an ADS domain. + yes + + + winbindd_idmap + New ID map table from SIDS to UNIX UIDs/GIDs. + yes +
-- 2.11.4.GIT