From fb7096a55bb7873965797feee72ceef2404d689d Mon Sep 17 00:00:00 2001 From: John H Terpstra Date: Thu, 8 Oct 2009 08:27:21 -0500 Subject: Fix typos. Thank-you PC Oota. --- docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) (limited to 'docs-xml') diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml index 33e2697bd3f..2c59aa74201 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml @@ -93,7 +93,6 @@ idmap uid idmap gid idmap backend -LDAP Winbind maintains a database called winbind_idmap.tdb in which it stores mappings between UNIX UIDs, GIDs, and NT SIDs. This mapping is used only for users and groups that do not have a local UID/GID. It stores the UID/GID @@ -210,7 +209,7 @@ Users on the UNIX machine can then use NT user and group names as they would native UNIX names. They can chown files so they are owned by NT domain users or even login to the - UNIX machine and run a UNIX X-Window session as a domain user. + UNIX machine and run a UNIX X Window session as a domain user. domain controller @@ -571,7 +570,7 @@ is for you. PAM back up -boot disk` +boot disk If you have a Samba configuration file that you are currently using, BACK IT UP! If your system already uses PAM, back up the /etc/pam.d directory contents! If you haven't already made a boot disk, MAKE ONE NOW! @@ -602,7 +601,7 @@ instructions on downloading the source code. development libraries To allow domain users the ability to access Samba shares and files, as well as potentially other services provided by your Samba machine, PAM must be set up properly on your -machine. In order to compile the Winbind modules, you should have at least the PAM development libraries installed +machine. In order to compile the Winbind modules, the PAM development libraries should be installed on your system. Please refer to the PAM Web site . @@ -976,9 +975,6 @@ The same thing can be done for groups with the command: /etc/init.d/smb /etc/init.d/samba /usr/local/samba/bin - - - The &winbindd; daemon needs to start up after the &smbd; and &nmbd; daemons are running. To accomplish this task, you need to modify the startup scripts of your system. They are located at /etc/init.d/smb in Red Hat Linux and in /etc/init.d/samba in Debian @@ -1119,7 +1115,7 @@ usually only starts smbd and nmbd but should now start winbindd, too. If you hav -Again, if you would like to run Samba in dual daemon mode, replace: +Again, if you would like to run winbindd in dual daemon mode, replace: /usr/local/samba/sbin/winbindd @@ -1234,7 +1230,7 @@ pre-create the directories of users to make sure users can log in on UNIX with t Winbind ftp access The /etc/pam.d/ftp file can be changed to allow Winbind ftp access in a manner similar to -the samba file. My /etc/pam.d/ftp file was changed to look like this: +the /etc/pam.d/samba file. My /etc/pam.d/ftp file was changed to look like this: auth required /lib/security/pam_listfile.so item=user sense=deny \ file=/etc/ftpusers onerr=succeed -- cgit v1.2.1