/usr/share/doc/sadms/html/share.html is in sadms 2.0.15.repack-0ubuntu2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>SADMS</title>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta http-equiv="Content-Language" content="en-us">
<link rel="stylesheet" href="sadms.css" type="text/css">
</head>
<body>
<table width="100%" border="0">
<tr>
<td><div align="left"><img src="images/sadms.gif" alt="sadms.gif" width="120" height="50"></div></td>
<td><div class="section-title" align="right">share</div></td>
</tr>
</table>
<p>You will find below some reference data to help you fine-tune the settings and tailor the shared spaces to your needs. Proper permissions are obtained by tuning both the share level <strong>and</strong> the file system level and it can be very tricky. File system permissions are available for changes in the last tab.</p>
<p><img src="images/eye.gif" width="27" height="19"><br>
<a href="tut-share.html">share tutorial
</a><br>
<br>
<b>REFERENCE<BR>
from Samba 3 official documentation</b></p>
<TABLE width=100% BORDER=1 CELLPADDING=2 CELLSPACING=0>
<TR>
<TD class="table-header"><B>invalid users</B></TD>
<TD>(<A HREF="#S">S</A>)</TD>
<TD>Specifies a list of users that can connect to a share and that should not be allowed to login to this service. A name starting with a '@' is interpreted as an NIS netgroup first (if your system supports NIS), and then as a UNIX group if the name was not found in the NIS netgroup database. A name starting with '+' is interpreted only by looking in the UNIX group database. A name starting with '&' is interpreted only by looking in the NIS netgroup database (this requires NIS to be working on your system). The characters '+' and '&' may be used at the start of the name in either order so the value +&group means check the UNIX group database, followed by the NIS netgroup database, and the value &+group means check the NIS netgroup database, followed by the UNIX group database (the same as the '@' prefix).<BR>
Default: NULL, no invalid users</TD>
</TR>
<TR>
<TD class="table-header"><B>valid users</B></TD>
<TD>(<A HREF="#S">S</A>)</TD>
<TD>Specifies a list of users that can connect to a share and should be allowed to login to this service. A name starting with a '@' is interpreted as an NIS netgroup first (if your system supports NIS), and then as a UNIX group if the name was not found in the NIS netgroup database. A name starting with '+' is interpreted only by looking in the UNIX group database. A name starting with '&' is interpreted only by looking in the NIS netgroup database (this requires NIS to be working on your system). The characters '+' and '&' may be used at the start of the name in either order so the value +&group means check the UNIX group database, followed by the NIS netgroup database, and the value &+group means check the NIS netgroup database, followed by the UNIX group database (the same as the '@' prefix). If this is empty (the default) then any user can login. If a username is in both this list and the invalid users list then access is denied for that user.<BR>
Default: NULL, no valid users list (allows everyone, anyone can login)</TD>
</TR>
<TR>
<TD class="table-header"><B>guest ok</B></TD>
<TD> </TD>
<TD>If this parameter is set for a service, then no password is required to connect to the service. Privileges will be those of the guest account. </TD>
</TR>
<TR>
<TD class="table-header"> </TD>
<TD> </TD>
<TD> </TD>
</TR>
<TR>
<TD class="table-header"><B>admin users</B></TD>
<TD>(<A HREF="#S">S</A>)</TD>
<TD>Specifies a list of users who will be granted administrative privileges on the share. They will do all file operations as the super-user (root). You should use this option very carefully, as any user in this list will be able to do anything they like on the share, irrespective of file permissions. Default: NULL, no admin users.</TD>
</TR>
<TR>
<TD class="table-header"><B>force group</B></TD>
<TD>(<A HREF="#S">S</A>)</TD>
<TD>Specifies a UNIX group name that will be assigned as the default primary group for all users connecting to this service. This option, sometimes called group, assigns a static group ID that will be used on all connections to a share after the client has successfully authenticated. This is useful for sharing files by ensuring that all access to files on service will use the named group for their permissions checking. Thus, by assigning permissions for this group to the files and directories within this service the Samba administrator can restrict or allow sharing of these files. This assigns a specific group to each new file or directory created from an SMB client. Allowable values: a Unix group name. Sets the effective group name assigned to all users accessing a share. Used to override a user's normal group memberships. In Samba 2.0.5 and above this parameter has extended functionality in the following way. If the group name listed here has a '+' character prepended to it then the current user accessing the share only has the primary group default assigned to this group if they are already assigned as a member of that group. This allows an administrator to decide that only users who are already in a particular group will create files with group ownership set to that group. This gives a finer granularity of ownership assignment. For example, the setting force group = +sys means that only users who are already in group sys will have their default primary group assigned to sys when accessing this Samba share. All other users will retain their ordinary primary group. If the parameter is also set the group specified in force group will override the primary group set in force user.<BR>
Default: NULL, no forced group</TD>
</TR>
<TR>
<TD class="table-header"><B>force user</B></TD>
<TD>(<A HREF="#S">S</A>)</TD>
<TD>Specifies a UNIX user name that will be assigned as the default user for all users connecting to this service. This is useful for sharing files. You should also use it carefully as using it incorrectly can cause security problems. The force user option assigns a static user ID that will be used on all connections to a share after the client has successfully authenticated. This user name only gets used once a connection is established. Thus clients still need to connect as a valid user and supply a valid password. Once connected, all file operations will be performed as the "forced user", no matter what username the client connected as. This assigns a specific user to each new file or directory created from an SMB client. In Samba 2.0.5 and above this parameter also causes the primary group of the forced user to be used as the primary group for all file activity. Prior to 2.0.5 the primary group was left as the primary group of the connecting user (this was a bug).<BR>
Default: NULL, no forced user</TD>
</TR>
<TR>
<TD class="table-header"> </TD>
<TD> </TD>
<TD> </TD>
</TR>
<TR>
<TD class="table-header"><B>read list</B></TD>
<TD>(<A HREF="#S">S</A>)</TD>
<TD>List of users that are given read-only access to a service. If the connecting user is in this list then they will not be given write access, no matter what the option is set to. The list can include group names using the syntax described in the parameter. Default: read list = <empty string></TD>
</TR>
<TR>
<TD class="table-header"><B>write list</B></TD>
<TD>(<A HREF="#S">S</A>)</TD>
<TD>List of users that are given read-write access to a service. If the connecting user is in this list then they will be given write access, no matter what the option is set to. The list can include group names using the @group syntax. Note that if a user is in both the read list and the write list then they will be given write access. Default: write list = <empty string></TD>
</TR>
</TABLE>
<P><a name="S"></a>(S) The current servicename is substituted for %S</P>
</body>
</html>
|