<para>
Be careful. If you take away all permissions from the <constant>Everyone</constant> user without removing this user
then effectively no user will be able to access the share. This is a result of what is known as
- ACL precedence. ie: Everyone with <strong>no access</strong> means that MaryK who is part of the group
+ ACL precedence. ie: Everyone with <emphasis>no access</emphasis> means that MaryK who is part of the group
<constant>Everyone</constant> will have no access even if this user is given explicit full control access.
</para>
</warning>
</para>
<note><para>
- The above are only needed <strong>if</strong> your users are <strong>not</strong> members of the group
+ The above are only needed <emphasis>if</emphasis> your users are <emphasis>not</emphasis> members of the group
you have used. ie: Within the OS do not have write permission on the directory.
</para>
</note>
</para>
<note><para>
-You do <strong>not</strong> need a smbpasswd file, and older clients will be authenticated as
+You do <emphasis>not</emphasis> need a smbpasswd file, and older clients will be authenticated as
if <parameter>security = domain</parameter>, although it won't do any harm and
allows you to have local users not in the domain. It is expected that the above
required options will change soon when active directory integration will get
</programlisting></para>
<para>
-Do <strong>not</strong> use the <command>bind interfaces only</command> parameter where you
+Do <emphasis>not</emphasis> use the <command>bind interfaces only</command> parameter where you
may wish to
use the samba password change facility, or where &smbclient; may need to
access a local service for name resolution or for local resource
</para>
<para>
-Note that you should <strong>not</strong> set Samba to be the domain master for a
+Note that you should <emphasis>not</emphasis> set Samba to be the domain master for a
workgroup that has the same name as an NT Domain.
</para>
</para>
<para>
-The next step is rather important. <strong>Please note:</strong> Instead of assigning a group profile
+The next step is rather important. <emphasis>Please note:</emphasis> Instead of assigning a group profile
to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned
the now modified profile.
</para>
SWAT can be configured to run in <emphasis>demo</emphasis> mode. This is NOT recommended
as it runs SWAT without authentication and with full administrative ability. ie: Allows
changes to smb.conf as well as general operation with root privilidges. The option that
-creates this ability is the <option>-a</option> flag to swat. <strong>Do not use this in any
-production environment.</strong>
+creates this ability is the <option>-a</option> flag to swat. <emphasis>Do not use this in any
+production environment.</emphasis>
</para></warning>
</sect2>
for it's workgroup entry. It is not uncommon for the name WORKGROUP to be used for this. With this
mode of configuration there are NO machine trust accounts and any concept of membership as such
is limited to the fact that all machines appear in the network neighbourhood to be logically
-grouped together. Again, just to be clear: <strong>workgroup mode does not involve any security machine
-accounts</strong>.
+grouped together. Again, just to be clear: <emphasis>workgroup mode does not involve any security machine
+accounts</emphasis>.
</para>
<para>
url="http://www.fsf.org/licenses/gpl.txt">http://www.fsf.org/licenses/gpl.txt</ulink>
</para>
-<sect1>
+<formalpara>
<title>Attributions</title>
&attributions;
-</sect1>
+</formalpara>
</legalnotice>
</bookinfo>
git.samba.org / sfrench / samba-autobuild / .git / commitdiff