From 4b10dd945476a93fd9a7d3e047cff7592935ad34 Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Wed, 24 Sep 2003 15:08:05 +0000 Subject: more syncs from 3.0 (This used to be commit bb7d5ce3762afcb14905fc2c1112df8a7475ffe3) --- docs/docbook/smbdotconf/misc/afsshare.xml | 17 +++++++++++++++++ docs/docbook/smbdotconf/misc/afsusernamemap.xml | 20 ++++++++++++++++++++ 2 files changed, 37 insertions(+) create mode 100644 docs/docbook/smbdotconf/misc/afsshare.xml create mode 100644 docs/docbook/smbdotconf/misc/afsusernamemap.xml (limited to 'docs/docbook/smbdotconf/misc') diff --git a/docs/docbook/smbdotconf/misc/afsshare.xml b/docs/docbook/smbdotconf/misc/afsshare.xml new file mode 100644 index 0000000000..1933fa5768 --- /dev/null +++ b/docs/docbook/smbdotconf/misc/afsshare.xml @@ -0,0 +1,17 @@ + + + This parameter controls whether special AFS features are enabled + for this share. If enabled, it assumes that the directory exported via + the path parameter is a local AFS import. The + special AFS features include the attempt to hand-craft an AFS token + if you enabled --with-fake-kaserver in configure. + + + Default: afs share = no + + Example: afs share = yes + + diff --git a/docs/docbook/smbdotconf/misc/afsusernamemap.xml b/docs/docbook/smbdotconf/misc/afsusernamemap.xml new file mode 100644 index 0000000000..a312f4309b --- /dev/null +++ b/docs/docbook/smbdotconf/misc/afsusernamemap.xml @@ -0,0 +1,20 @@ + + + If you are using the fake kaserver AFS feature, you might + want to hand-craft the usernames you are creating tokens for. + For example this is necessary if you have users from several domain + in your AFS Protection Database. One possible scheme to code users + as DOMAIN+User as it is done by winbind with the + as a separator. + + + The mapped user name must contain the cell name to log into, + so without setting this parameter there will be no token. + + Default: none + + Example: afs username map = %u@afs.samba.org + + -- cgit