Changeset 478 for vendor/current/docs-xml
- Timestamp:
- Aug 2, 2010, 6:40:21 PM (15 years ago)
- Location:
- vendor/current/docs-xml
- Files:
-
- 5 edited
Legend:
- Unmodified
- Added
- Removed
-
vendor/current/docs-xml/manpages-3/idmap_ad.8.xml
r414 r478 59 59 <para> 60 60 The following example shows how to retrieve idmappings from our principal and 61 andtrusted AD domains. If trusted domains are present id conflicts must be61 trusted AD domains. If trusted domains are present id conflicts must be 62 62 resolved beforehand, there is no 63 63 guarantee on the order conflicting mappings would be resolved at this point. -
vendor/current/docs-xml/manpages-3/net.8.xml
r427 r478 1791 1791 1792 1792 <refsect2> 1793 <title>G_LOCK</title> 1794 1795 <para>Manage global locks.</para> 1796 1797 <refsect3> 1798 <title>G_LOCK DO <replaceable>lockname</replaceable> <replaceable>timeout</replaceable> <replaceable>command</replaceable></title> 1799 1800 <para> 1801 Execute a shell command under a global lock. This might be useful to define the 1802 order in which several shell commands will be executed. The locking information 1803 is stored in a file called <filename>g_lock.tdb</filename>. In setups with CTDB 1804 running, the locking information will be available on all cluster nodes. 1805 </para> 1806 1807 <itemizedlist> 1808 <listitem><para><replaceable>LOCKNAME</replaceable> defines the name of the global lock.</para></listitem> 1809 <listitem><para><replaceable>TIMEOUT</replaceable> defines the timeout.</para></listitem> 1810 <listitem><para><replaceable>COMMAND</replaceable> defines the shell command to execute.</para></listitem> 1811 </itemizedlist> 1812 </refsect3> 1813 1814 <refsect3> 1815 <title>G_LOCK LOCKS</title> 1816 1817 <para> 1818 Print a list of all currently existing locknames. 1819 </para> 1820 </refsect3> 1821 1822 <refsect3> 1823 <title>G_LOCK DUMP <replaceable>lockname</replaceable></title> 1824 1825 <para> 1826 Dump the locking table of a certain global lock. 1827 </para> 1828 </refsect3> 1829 1830 </refsect2> 1831 1832 <refsect2> 1793 1833 <title>HELP [COMMAND]</title> 1794 1834 -
vendor/current/docs-xml/manpages-3/ntlm_auth.1.xml
r414 r478 172 172 173 173 <varlistentry> 174 <term> Username</term>174 <term>NT-Domain</term> 175 175 <listitem><para>The user's domain, expected to be in 176 176 Samba's <smbconfoption name="unix charset"/>. 177 177 </para> 178 178 179 <para><example> Domain: WORKGROUP</example></para>180 <para><example> Domain:: V09SS0dST1VQ</example></para>179 <para><example>NT-Domain: WORKGROUP</example></para> 180 <para><example>NT-Domain:: V09SS0dST1VQ</example></para> 181 181 </listitem></varlistentry> 182 182 -
vendor/current/docs-xml/manpages-3/winbindd.8.xml
r414 r478 81 81 <variablelist> 82 82 <varlistentry> 83 <term>-D</term>84 <listitem><para>If specified, this parameter causes85 the server to operate as a daemon. That is, it detaches86 itself and runs in the background on the appropriate port.87 This switch is assumed if <command>winbindd</command> is88 executed on the command line of a shell.89 </para></listitem>90 </varlistentry>91 92 <varlistentry>93 83 <term>hosts</term> 94 84 <listitem><para>This feature is only available on IRIX. … … 147 137 148 138 <variablelist> 139 <varlistentry> 140 <term>-D</term> 141 <listitem><para>If specified, this parameter causes 142 the server to operate as a daemon. That is, it detaches 143 itself and runs in the background on the appropriate port. 144 This switch is assumed if <command>winbindd</command> is 145 executed on the command line of a shell. 146 </para></listitem> 147 </varlistentry> 148 149 149 <varlistentry> 150 150 <term>-F</term> -
vendor/current/docs-xml/smbdotconf/winbind/winbindnssinfo.xml
r414 r478 7 7 8 8 <para>This parameter is designed to control how Winbind retrieves Name 9 Service Information to construct a user's home directory and login shell. 10 Currently the following settings are available: 9 Service Information to construct a user's home directory and login shell. 10 Currently the following settings are available: 11 11 12 12 <itemizedlist> 13 13 <listitem> 14 <para><parameter moreinfo="none">template</parameter> 15 - The default, using the parameters of <parameter moreinfo="none">template 14 <para><parameter moreinfo="none">template</parameter> 15 - The default, using the parameters of <parameter moreinfo="none">template 16 16 shell</parameter> and <parameter moreinfo="none">template homedir</parameter>) 17 17 </para> 18 18 </listitem> 19 19 20 20 <listitem> 21 21 <para><parameter moreinfo="none"><sfu | rfc2307 ></parameter> … … 24 24 LDAP schema, winbind can retrieve the login shell and the home 25 25 directory attributes directly from your Directory Server. Note that 26 retrieving UID and GID from your ADS-Server requires to 27 use <parameter moreinfo="non">idmap backend</parameter> = ad 28 or <parameter moreinfo="non">idmap config DOMAIN:backend</parameter> = ad 26 retrieving UID and GID from your ADS-Server requires to 27 use <parameter moreinfo="none">idmap config DOMAIN:backend</parameter> = ad 29 28 as well. 30 29 </para> 31 30 </listitem> 32 33 31 </itemizedlist> 34 32 … … 37 35 38 36 <value type="default">template</value> 39 <value type="example"> templatesfu</value>37 <value type="example">sfu</value> 40 38 </samba:parameter>
Note:
See TracChangeset
for help on using the changeset viewer.