From 62019631fb0ee333de5a09a8dda4b4511043dfa1 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Sun, 31 Oct 2004 04:16:36 +0000 Subject: Work in progress commit - Adding IDMAP documentation. (This used to be commit e2f52f0feccffe62b289095e82da7b3789d2a79b) --- docs/Samba-HOWTO-Collection/IDMAP.xml | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) (limited to 'docs/Samba-HOWTO-Collection') diff --git a/docs/Samba-HOWTO-Collection/IDMAP.xml b/docs/Samba-HOWTO-Collection/IDMAP.xml index fa485de495..23d02bb0f3 100644 --- a/docs/Samba-HOWTO-Collection/IDMAP.xml +++ b/docs/Samba-HOWTO-Collection/IDMAP.xml @@ -29,11 +29,21 @@ This is followed by an overview of how the IDMAP facility may be implemented. -The IDMAP facility is usually of concern only where more than one Samba server or Samba network client +The IDMAP facility is usually of concern where more than one Samba server or Samba network client is installed in the one Domain. Where there is a single Samba server do not be too concerned regarding the IDMAP infrastructure - the default behavior of Samba is nearly always sufficient. + +The use of IDMAP is important where the Samba server will be accessed by workstations or servers from +more than one domain, in which case it is important to run winbind so it can handle the resolution (ID mapping) +of foreign SIDs to local UNIX UIDs and GIDs. + + + +The use of the IDMAP facility requires that the winbindd be executed on Samba start-up. + + Samba Server Deployment Types -- cgit