Changeset 740 for vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml
- Timestamp:
- Nov 14, 2012, 12:59:34 PM (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml
r414 r740 94 94 <indexterm><primary>idmap gid</primary></indexterm> 95 95 <indexterm><primary>idmap backend</primary></indexterm> 96 <indexterm><primary>LDAP</primary></indexterm>97 96 Winbind maintains a database called winbind_idmap.tdb in which it stores 98 97 mappings between UNIX UIDs, GIDs, and NT SIDs. This mapping is used only … … 211 210 names as they would <quote>native</quote> UNIX names. They can chown files 212 211 so they are owned by NT domain users or even login to the 213 UNIX machine and run a UNIX X -Window session as a domain user.</para>212 UNIX machine and run a UNIX X Window session as a domain user.</para> 214 213 215 214 <para> … … 572 571 <indexterm><primary>PAM</primary></indexterm> 573 572 <indexterm><primary>back up</primary></indexterm> 574 <indexterm><primary>boot disk `</primary></indexterm>573 <indexterm><primary>boot disk</primary></indexterm> 575 574 If you have a Samba configuration file that you are currently using, <emphasis>BACK IT UP!</emphasis> 576 575 If your system already uses PAM, <emphasis>back up the <filename>/etc/pam.d</filename> directory … … 603 602 To allow domain users the ability to access Samba shares and files, as well as potentially other services 604 603 provided by your Samba machine, PAM must be set up properly on your 605 machine. In order to compile the Winbind modules, you should have at least the PAM development librariesinstalled606 on your system. Please refer to the PAM Web site <ulink url="http://www.kernel.org/pub/linux/libs/pam/"/>.604 machine. In order to compile the Winbind modules, the PAM development libraries should be installed 605 on your system. Please refer to the <ulink url="http://www.kernel.org/pub/linux/libs/pam/">PAM Web Site</ulink>. 607 606 </para> 608 607 </sect2> … … 977 976 <indexterm><primary>/etc/init.d/samba</primary></indexterm> 978 977 <indexterm><primary>/usr/local/samba/bin</primary></indexterm> 979 <indexterm><primary></primary></indexterm>980 <indexterm><primary></primary></indexterm>981 <indexterm><primary></primary></indexterm>982 978 The &winbindd; daemon needs to start up after the &smbd; and &nmbd; daemons are running. To accomplish this 983 979 task, you need to modify the startup scripts of your system. They are located at … … 1120 1116 1121 1117 <para> 1122 Again, if you would like to run Sambain dual daemon mode, replace:1118 Again, if you would like to run winbindd in dual daemon mode, replace: 1123 1119 <programlisting> 1124 1120 /usr/local/samba/sbin/winbindd … … 1235 1231 <indexterm><primary>ftp access</primary></indexterm> 1236 1232 The <filename>/etc/pam.d/ftp</filename> file can be changed to allow Winbind ftp access in a manner similar to 1237 the samba file. My <filename>/etc/pam.d/ftp</filename> file was changed to look like this:1233 the <filename>/etc/pam.d/samba</filename>Samba file. My <filename>/etc/pam.d/ftp</filename> file was changed to look like this: 1238 1234 <programlisting> 1239 1235 auth required /lib/security/pam_listfile.so item=user sense=deny \
Note:
See TracChangeset
for help on using the changeset viewer.