Changeset 988 for vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-Printing.xml
- Timestamp:
- Nov 24, 2016, 1:14:11 PM (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-Printing.xml
r740 r988 283 283 show add printer wizard = Yes 284 284 os2 driver map = 285 printer admin =286 285 min print space = 0 287 286 max print jobs = 1000 … … 405 404 show add printer wizard = Yes 406 405 os2 driver map = 407 printer admin =408 406 min print space = 0 409 407 max print jobs = 1000 … … 481 479 <smbconfoption name="show add printer wizard">yes</smbconfoption> 482 480 <smbconfoption name="printcap name">/etc/printcap</smbconfoption> 483 <smbconfoption name="printer admin">@ntadmin, root</smbconfoption>484 481 <smbconfoption name="max print jobs">100</smbconfoption> 485 482 <smbconfoption name="lpq cache time">20</smbconfoption> … … 499 496 <smbconfoption name="comment">Printer with Restricted Access</smbconfoption> 500 497 <smbconfoption name="path">/var/spool/samba_my_printer</smbconfoption> 501 <smbconfoption name="printer admin">kurt</smbconfoption>502 498 <smbconfoption name="browseable">yes</smbconfoption> 503 499 <smbconfoption name="printable">yes</smbconfoption> … … 569 565 The <smbconfoption name="printing"/> parameter is normally a service-level parameter. Since it is included 570 566 here in the <smbconfsection name="[global]"/> section, it will take effect for all printer shares that are not 571 defined differently. Samba -3no longer supports the SOFTQ printing system.567 defined differently. Samba no longer supports the SOFTQ printing system. 572 568 </para></caution> 573 569 </listitem></varlistentry> … … 625 621 </para></listitem></varlistentry> 626 622 627 <varlistentry><term><smbconfoption name="printer admin">@ntadmin </smbconfoption></term>628 <listitem><para>629 <indexterm><primary>add drivers</primary></indexterm>630 <indexterm><primary>/etc/group</primary></indexterm>631 <indexterm><primary>printer share</primary></indexterm>632 <indexterm><primary>set printer properties</primary></indexterm>633 Members of the ntadmin group should be able to add drivers and set printer properties634 (<constant>ntadmin</constant> is only an example name; it needs to be a valid UNIX group name); root is635 implicitly always a <smbconfoption name="printer admin"/>. The <literal>@</literal> sign precedes group names636 in the <filename>/etc/group</filename>. A printer admin can do anything to printers via the remote637 administration interfaces offered by MS-RPC (see <link linkend="cups-msrpc">Printing Developments Since638 Samba-2.2</link>). In larger installations, the <smbconfoption name="printer admin"/> parameter is normally a639 per-share parameter. This permits different groups to administer each printer share.640 </para></listitem></varlistentry>641 642 623 <varlistentry><term><smbconfoption name="lpq cache time">20 </smbconfoption></term> 643 624 <listitem><para> … … 787 768 Sets the spooling area for this printer to a directory other than the default. It is not 788 769 necessary to set it differently, but the option is available. 789 </para></listitem>790 </varlistentry>791 792 <varlistentry><term><smbconfoption name="printer admin">kurt </smbconfoption></term>793 <listitem><para>794 The printer admin definition is different for this explicitly defined printer share from the general795 <smbconfsection name="[printers]"/> share. It is not a requirement; we did it to show that it is possible.796 770 </para></listitem> 797 771 </varlistentry> … … 1119 1093 <indexterm><primary>ADS</primary></indexterm> 1120 1094 <indexterm><primary>LDAP</primary></indexterm> 1121 A benefit of updating is that Samba -3is able to publish its printers to Active Directory (or LDAP).1095 A benefit of updating is that Samba is able to publish its printers to Active Directory (or LDAP). 1122 1096 </para> 1123 1097 … … 1224 1198 <indexterm><primary>ACLs</primary></indexterm> 1225 1199 These parameters, including the <parameter>printer driver file</parameter> parameter, 1226 are now removed and cannot be used in installations of Samba -3. The share name1200 are now removed and cannot be used in installations of Samba. The share name 1227 1201 <smbconfsection name="[print$]"/> is now used for the location of downloadable printer 1228 1202 drivers. It is taken from the <smbconfsection name="[print$]"/> service created … … 1257 1231 <smbconfblock> 1258 1232 <smbconfsection name="[global]"/> 1259 <smbconfcomment>members of the ntadmin group should be able to add drivers and set</smbconfcomment>1260 <smbconfcomment>printer properties. root is implicitly always a 'printer admin'.</smbconfcomment>1261 <smbconfoption name="printer admin">@ntadmin</smbconfoption>1262 1233 <smbconfcomment>...</smbconfcomment> 1263 1234 … … 1359 1330 update files on the share. Normally, you will want to name only administrative-level user 1360 1331 account in this setting. Check the file system permissions to make sure these accounts 1361 can copy files to the share. If this is a non-root account, then the account should also 1362 be mentioned in the global <smbconfoption name="printer admin"/> 1363 parameter. See the &smb.conf; man page for more information on configuring file shares. 1332 can copy files to the share. 1364 1333 </para></listitem> 1365 1334 </varlistentry> … … 1404 1373 The account used to connect to the Samba host must have a UID of 0 (i.e., a root account). 1405 1374 </para></listitem> 1406 1407 <listitem><para>1408 The account used to connect to the Samba host must be named in the <emphasis>printer admin</emphasis> list.1409 </para></listitem>1410 1375 </itemizedlist> 1411 1376 … … 1496 1461 Once the APW is started, the procedure is exactly the same as the one you are familiar with in Windows (we 1497 1462 assume here that you are familiar with the printer driver installations procedure on Windows NT). Make sure 1498 your connection is, in fact, set up as a user with <smbconfoption name="printer admin"/>1499 privileges(if in doubt, use <command>smbstatus</command> to check for this). If you wish to install1463 your connection is, in fact, set up as a user with printer administrator privileges 1464 (if in doubt, use <command>smbstatus</command> to check for this). If you wish to install 1500 1465 printer drivers for client operating systems other than <application>Windows NT x86</application>, 1501 1466 you will need to use the <guilabel>Sharing</guilabel> tab of the printer properties dialog. … … 1503 1468 1504 1469 <para> 1505 Assuming you have connected with an administrative (or root) account (as named by the 1506 <smbconfoption name="printer admin"/> parameter), you will also be able to modify 1470 Assuming you have connected with an administrative (or root) account, you will also be able to modify 1507 1471 other printer properties such as ACLs and default device settings using this dialog. For the default 1508 1472 device settings, please consider the advice given further in <link linkend="inst-rpc">Installing … … 2105 2069 2106 2070 <para> 2107 Replace root, if needed, by another valid <smbconfoption name="printer admin"/>user as given in2071 Replace root, if needed, by another valid printer administrator user as given in 2108 2072 the definition. Should you already be connected as a different user, you will get an error message. There 2109 2073 is no easy way to get rid of that connection, because Windows does not seem to know a concept of logging … … 2205 2169 2206 2170 <para> 2207 Be aware that a valid device mode can only be initiated by a <smbconfoption name="printer admin"/>or root2171 Be aware that a valid device mode can only be initiated by a printer administrator or root 2208 2172 (the reason should be obvious). Device modes can be correctly set only by executing the printer driver program 2209 2173 itself. Since Samba cannot execute this Win32 platform driver code, it sets this field initially to NULL … … 2316 2280 2317 2281 <sect2> 2318 <title>Always Make First Client Connection as root or <quote>printer admin</quote></title>2282 <title>Always Make First Client Connection as root or printer administrator</title> 2319 2283 2320 2284 <para> 2321 2285 After you installed the driver on the Samba server (in its <smbconfsection name="[print$]"/> share), you 2322 2286 should always make sure that your first client installation completes correctly. Make it a habit for yourself 2323 to build the very first connection from a client as <smbconfoption name="printer admin"/>. This is to make2287 to build the very first connection from a client as a printer administrator"/>. This is to make 2324 2288 sure that: 2325 2289 </para> … … 2355 2319 You will be prompted for <constant>root</constant>'s Samba password; type it, wait a few seconds, click on 2356 2320 <guibutton>Printing Defaults</guibutton>, and proceed to set the job options that should be used as defaults 2357 by all clients. Alternatively, instead of root you can name one other member of the <smbconfoption2358 name="printer admin"/> from the setting.2321 by all clients. Alternatively, instead of root you can give one other member printer adminadministrator 2322 privileges. 2359 2323 </para> 2360 2324 … … 2459 2423 arrived at with steps C.1 through C.6 will permanently save any settings which will then become the defaults 2460 2424 for new users. If you want all clients to have the same defaults, you need to conduct these steps as 2461 administrator (<smbconfoption name="printer admin"/>)before a client downloads the driver (the clients can2425 administrator before a client downloads the driver (the clients can 2462 2426 later set their own per-user defaults by following procedures A or B above). Windows 200x/XP allow per-user 2463 2427 default settings and the ones the administrator gives them before they set up their own. The parents of the … … 2603 2567 <listitem><para> 2604 2568 The connected user is able to successfully execute an <command>OpenPrinterEx(\\server)</command> with 2605 administrative privileges (i.e., root or <smbconfoption name="printer admin"/>).2569 administrative privileges (i.e., root or a printer administrator). 2606 2570 </para> 2607 2571 … … 3194 3158 <listitem><para> 3195 3159 An existing <filename>printers.def</filename> file (the one specified in the now removed parameter 3196 <parameter>printer driver file</parameter>) will no longer work with Samba -3. In 3.0, smbd attempts3160 <parameter>printer driver file</parameter>) will no longer work with Samba. In 3.0, smbd attempts 3197 3161 to locate Windows 9x/Me driver files for the printer in <smbconfsection name="[print$]"/> 3198 3162 and additional settings in the TDB and only there; if it fails, it will <emphasis>not</emphasis>
Note:
See TracChangeset
for help on using the changeset viewer.