/[gentoo]/xml/htdocs/doc/en/quick-samba-howto.xml
Gentoo

Diff of /xml/htdocs/doc/en/quick-samba-howto.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.9 Revision 1.30
1<?xml version='1.0' encoding='UTF-8'?> 1<?xml version='1.0' encoding='UTF-8'?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.9 2004/08/01 11:40:20 swift Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.30 2007/07/08 02:22:04 nightmorph Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4<guide link="quick-samba-howto.xml"> 4<guide link="/doc/en/quick-samba-howto.xml">
5<title>Gentoo Samba3/CUPS/Clam AV HOWTO</title> 5<title>Gentoo Samba3/CUPS/ClamAV HOWTO</title>
6<author title="Author"> 6<author title="Author">
7 <mail link="daff at dword dot org">Andreas "daff" Ntaflos</mail> 7 <mail link="daff at dword dot org">Andreas "daff" Ntaflos</mail>
8</author> 8</author>
9<author title="Author"> 9<author title="Author">
10 <mail link="joshua@sungentoo.homeunix.com">Joshua Preston</mail> 10 <mail link="joshua@sungentoo.homeunix.com">Joshua Preston</mail>
11</author> 11</author>
12<author title="Editor">
13 <mail link="nightmorph@gentoo.org">Joshua Saddler</mail>
14</author>
12 15
13<abstract> 16<abstract>
14Setup, install and configure a Samba Server under Gentoo that shares 17Setup, install and configure a Samba Server under Gentoo that shares files,
15files, printers without the need to install drivers and provides 18printers without the need to install drivers and provides automatic virus
16automatic virus scanning. 19scanning.
17</abstract> 20</abstract>
18 21
19<!-- The content of this document is licensed under the CC-BY-SA license --> 22<!-- The content of this document is licensed under the CC-BY-SA license -->
20<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 23<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
21<license/> 24<license/>
22 25
23<version>1.6</version> 26<version>1.18</version>
24<date>August 01, 2004</date> 27<date>2007-07-07</date>
25 28
26<chapter> 29<chapter>
27<title>Introduction to this HOWTO</title> 30<title>Introduction to this HOWTO</title>
28<section> 31<section>
29<title>Purpose</title> 32<title>Purpose</title>
30<body> 33<body>
31 34
32<p> 35<p>
33This HOWTO is designed to help you move a network from many different 36This HOWTO is designed to help you move a network from many different clients
34clients speaking different languages, to many different machines that 37speaking different languages, to many different machines that speak a common
35speak a common language. The ultimate goal is to help differing 38language. The ultimate goal is to help differing architectures and technologies,
36architectures and technologies, come together in a productive, 39come together in a productive, happily coexisting environment.
37happily coexisting environment.
38</p>
39
40<p> 40</p>
41
42<p>
41Following the directions outlined in this HOWTO should give you an 43Following the directions outlined in this HOWTO should give you an excellent
42excellent step towards a peaceful cohabitation between Windows, and 44step towards a peaceful cohabitation between Windows, and virtually all known
43virtually all known variations of *nix. 45variations of *nix.
44</p>
45
46<p> 46</p>
47
48<p>
47This HOWTO originally started not as a HOWTO, but as a FAQ. It was 49This HOWTO originally started not as a HOWTO, but as a FAQ. It was intended to
48intended to explore the functionality and power of the Gentoo system, 50explore the functionality and power of the Gentoo system, portage and the
49portage and the flexibility of USE flags. Like so many other projects, 51flexibility of USE flags. Like so many other projects, it was quickly discovered
50it was quickly discovered what was missing in the Gentoo realm: there 52what was missing in the Gentoo realm: there weren't any Samba HOWTO's catered
51weren't any Samba HOWTO's catered for Gentoo users. These users are 53for Gentoo users. These users are more demanding than most; they require
52more demanding than most; they require performance, flexibility and 54performance, flexibility and customization. This does not however imply that
53customization. This does not however imply that this HOWTO was not
54intended for other distributions; rather that it was designed to work 55this HOWTO was not intended for other distributions; rather that it was designed
55with a highly customized version of Samba. 56to work with a highly customized version of Samba.
56</p>
57
58<p> 57</p>
58
59<p>
59This HOWTO will describe how to share files and printers between Windows 60This HOWTO will describe how to share files and printers between Windows PCs and
60PCs and *nix PCs. It will also demonstrate the use of the VFS (Virtual 61*nix PCs. It will also demonstrate the use of the VFS (Virtual File System)
61File System) feature of Samba to incorporate automatic virus protection. 62feature of Samba to incorporate automatic virus protection. As a finale, it will
62As a finale, it will show you how to mount and manipulate shares. 63show you how to mount and manipulate shares.
63</p>
64
65<p> 64</p>
65
66<p>
66There are a few topics that will be mentioned, but are out of the 67There are a few topics that will be mentioned, but are out of the scope of this
67scope of this HOWTO. These will be noted as they are presented. 68HOWTO. These will be noted as they are presented.
68</p>
69
70<p> 69</p>
70
71<p>
71This HOWTO is based on a compilation and merge of an excellent HOWTO 72This HOWTO is based on a compilation and merge of an excellent HOWTO provided in
72provided in the <uri link="http://forums.gentoo.org">Gentoo forums</uri> 73the <uri link="http://forums.gentoo.org">Gentoo forums</uri> by Andreas "daff"
73by Andreas "daff" Ntaflos and the collected knowledge of Joshua Preston. 74Ntaflos and the collected knowledge of Joshua Preston. The link to this
74The link to this discussion is provided below for your reference: 75discussion is provided below for your reference:
75</p> 76</p>
76 77
77<ul> 78<ul>
78 <li> 79 <li>
79 <uri link="http://forums.gentoo.org/viewtopic.php?t=110931">HOWTO 80 <uri link="http://forums.gentoo.org/viewtopic.php?t=110931">HOWTO
87<title>Before you use this guide</title> 88<title>Before you use this guide</title>
88<body> 89<body>
89 90
90<p> 91<p>
91There are a several other guides for setting up CUPS and/or Samba, please read 92There are a several other guides for setting up CUPS and/or Samba, please read
92them as well, as they may tell you things left out of this HOWTO (intentional 93them as well, as they may tell you things left out of this HOWTO (intentional or
93or otherwise). One such document is the very useful and well written <uri 94otherwise). One such document is the very useful and well written <uri
94link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration 95link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration
95issues and specific printer setup is not discussed here. 96issues and specific printer setup is not discussed here.
96</p> 97</p>
97 98
98</body> 99</body>
100<section> 101<section>
101<title>Brief Overview</title> 102<title>Brief Overview</title>
102<body> 103<body>
103 104
104<p> 105<p>
105After presenting the various USE flags, the following list will outline 106After presenting the various USE flags, the following list will outline all of
106all of the topics covered as they are presented: 107the topics covered as they are presented:
107</p> 108</p>
108 109
109<ul> 110<ul>
110 <li>On the Samba server: 111 <li>On the Samba server:
111 <ul> 112 <ul>
112 <li>Install and configure CLAM-AV</li> 113 <li>Install and configure ClamAV</li>
113 <li>Install and configure Samba</li> 114 <li>Install and configure Samba</li>
114 <li>Install and configure CUPS</li> 115 <li>Install and configure CUPS</li>
115 <li>Adding the printer to CUPS</li> 116 <li>Adding the printer to CUPS</li>
116 <li>Adding the PS drivers for the Windows clients</li> 117 <li>Adding the PS drivers for the Windows clients</li>
117 </ul> 118 </ul>
144<ul> 145<ul>
145 <li>net-fs/samba</li> 146 <li>net-fs/samba</li>
146 <li>app-antivirus/clamav</li> 147 <li>app-antivirus/clamav</li>
147 <li>net-print/cups</li> 148 <li>net-print/cups</li>
148 <li>net-print/foomatic</li> 149 <li>net-print/foomatic</li>
149 <li>net-print/hpijs (if you have an HP printer)</li> 150 <li>net-print/hplip (if you have an HP printer)</li>
150 <li>A kernel of sorts (preferably 2.4.24+ or 2.6.x)</li> 151 <li>A kernel of sorts (2.6)</li>
151 <li>A printer (PS or non-PS, maybe not TOO new or fancy)</li> 152 <li>A printer (PS or non-PS, maybe not TOO new or fancy)</li>
152 <li> 153 <li>
153 A working network (home/office/etc) consisting of more than one machine) 154 A working network (home/office/etc) consisting of more than one machine)
154 </li> 155 </li>
155</ul> 156</ul>
156 157
157<p> 158<p>
158The main package we use here is net-fs/samba, however, you will need 159The main package we use here is net-fs/samba, however, you will need a kernel
159a kernel with smbfs support enabled in order to mount a samba or windows 160with smbfs support enabled in order to mount a samba or windows share from
160share from another computer. CUPS will be emerged if it is not already. 161another computer. CUPS will be emerged if it is not already.
161app-antivirus/clamav will be used also, but others should be easily adapted 162app-antivirus/clamav will be used also, but others should be easily adapted to
162to work with Samba. 163work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning
164technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ...
163</p> 165</p>
164 166
165</body> 167</body>
166</section> 168</section>
167</chapter> 169</chapter>
171<section> 173<section>
172<title>The USE Flags</title> 174<title>The USE Flags</title>
173<body> 175<body>
174 176
175<p> 177<p>
176Before emerging anything, take a look at the various USE flags 178Before emerging anything, take a look at some of the various USE flags available
177available to Samba. 179to Samba.
178</p> 180</p>
179 181
180<pre caption="Samba uses the following USE Variables:"> 182<pre caption="Samba uses the following USE Variables:">
181kerberos mysql xml acl cups ldap pam readline python oav 183kerberos acl cups ldap pam readline python oav
182</pre> 184</pre>
183 185
184<p> 186<p>
185Depending on the network topology and the specific requirements of 187Depending on the network topology and the specific requirements of the server,
186the server, the USE flags outlined below will define what to include or 188the USE flags outlined below will define what to include or exclude from the
187exclude from the emerging of Samba. 189emerging of Samba.
188</p> 190</p>
189 191
190<table> 192<table>
191<tr> 193<tr>
192 <th><b>USE flag</b></th> 194 <th><b>USE flag</b></th>
199 intended to join an existing domain or Active Directory. See the note 201 intended to join an existing domain or Active Directory. See the note
200 below for more information. 202 below for more information.
201 </ti> 203 </ti>
202</tr> 204</tr>
203<tr> 205<tr>
204 <th><b>mysql</b></th>
205 <ti>
206 This will allow Samba to use MySQL in order to do password authentication.
207 It will store ACLs, usernames, passwords, etc in a database versus a
208 flat file. If Samba is needed to do password authentication, such as
209 acting as a password validation server or a Primary Domain Controller
210 (PDC).
211 </ti>
212</tr>
213<tr>
214 <th><b>xml</b></th>
215 <ti>
216 The xml USE option for Samba provides a password database backend allowing
217 Samba to store account details in XML files, for the same reasons listed in
218 the mysql USE flag description.
219 </ti>
220</tr>
221<tr>
222 <th><b>acl</b></th> 206 <th><b>acl</b></th>
223 <ti> 207 <ti>
224 Enables Access Control Lists. The ACL support in Samba uses a patched 208 Enables Access Control Lists. The ACL support in Samba uses a patched
225 ext2/ext3, or SGI's XFS in order to function properly as it extends more 209 ext2/ext3, or SGI's XFS in order to function properly as it extends more
226 detailed access to files or directories; much more so than typical *nix 210 detailed access to files or directories; much more so than typical *nix
228 </ti> 212 </ti>
229</tr> 213</tr>
230<tr> 214<tr>
231 <th><b>cups</b></th> 215 <th><b>cups</b></th>
232 <ti> 216 <ti>
233 This enables support for the Common Unix Printing System. This 217 This enables support for the Common Unix Printing System. This provides an
234 provides an interface allowing local CUPS printers to be shared to 218 interface allowing local CUPS printers to be shared to other systems in the
235 other systems in the network. 219 network.
236 </ti> 220 </ti>
237</tr> 221</tr>
238<tr> 222<tr>
239 <th><b>ldap</b></th> 223 <th><b>ldap</b></th>
240 <ti> 224 <ti>
241 Enables the Lightweight Directory Access Protocol (LDAP). If Samba is 225 Enables the Lightweight Directory Access Protocol (LDAP). If Samba is
242 expected to use Active Directory, this option must be used. This would 226 expected to use Active Directory, this option must be used. This would be
243 be used in the event Samba needs to login to or provide login to 227 used in the event Samba needs to login to or provide login to a
244 a Domain/Active Directory Server. The kerberos USE flag is needed for 228 Domain/Active Directory Server. The kerberos USE flag is needed for proper
245 proper functioning of this option. 229 functioning of this option.
246 </ti> 230 </ti>
247</tr> 231</tr>
248<tr> 232<tr>
249 <th><b>pam</b></th> 233 <th><b>pam</b></th>
250 <ti> 234 <ti>
251 Include support for pluggable authentication modules (PAM). This 235 Include support for pluggable authentication modules (PAM). This provides
252 provides the ability to authenticate users on the Samba Server, which is 236 the ability to authenticate users on the Samba Server, which is required if
253 required if users have to login to your server. The kerberos USE flag 237 users have to login to your server. The kerberos USE flag is recommended
254 is recommended along with this option. 238 along with this option.
255 </ti> 239 </ti>
256</tr> 240</tr>
257<tr> 241<tr>
258 <th><b>readline</b></th> 242 <th><b>readline</b></th>
259 <ti> 243 <ti>
260 Link Samba again libreadline. This is highly recommended and should 244 Link Samba against libreadline. This is highly recommended and should
261 probably not be disabled 245 probably not be disabled.
262 </ti> 246 </ti>
263</tr> 247</tr>
264<tr> 248<tr>
265 <th><b>python</b></th> 249 <th><b>python</b></th>
266 <ti> 250 <ti>
267 Python bindings API. Provides an API that will allow Python to 251 Python bindings API. Provides an API that will allow Python to interface
268 interface with Samba. 252 with Samba.
269 </ti> 253 </ti>
270</tr> 254</tr>
271<tr> 255<tr>
272 <th><b>oav</b></th> 256 <th><b>oav</b></th>
273 <ti> 257 <ti>
274 Provides on-access scanning of Samba shares with FRISK F-Prot 258 Provides on-access scanning of Samba shares with FRISK F-Prot Daemon,
275 Daemon, Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep 259 Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep (SAVI),
276 (SAVI), Symantec CarrierScan, and Trend Micro (VSAPI). 260 Symantec CarrierScan, and Trend Micro (VSAPI).
277 </ti> 261 </ti>
278</tr> 262</tr>
279</table> 263</table>
280 264
281<p> 265<p>
292 <li> 276 <li>
293 While Active Directory, ACL, and PDC functions are out of the intended 277 While Active Directory, ACL, and PDC functions are out of the intended
294 scope of this HOWTO, you may find these links as helpful to your cause: 278 scope of this HOWTO, you may find these links as helpful to your cause:
295 <ul> 279 <ul>
296 <li><uri>http://www.bluelightning.org/linux/samba_acl_howto/</uri></li> 280 <li><uri>http://www.bluelightning.org/linux/samba_acl_howto/</uri></li>
297 <li><uri>http://open-projects.linuxcare.com/research-papers/winbind-08162000.html</uri></li>
298 <li><uri>http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory</uri></li> 281 <li><uri>http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory</uri></li>
299 </ul> 282 </ul>
300 </li> 283 </li>
301</ul> 284</ul>
302 285
309<section> 292<section>
310<title>Emerging Samba</title> 293<title>Emerging Samba</title>
311<body> 294<body>
312 295
313<p> 296<p>
314First of all: be sure that all your hostnames resolve correctly. 297First of all: be sure that all your hostnames resolve correctly. Either have a
315Either have a working domain name system running on your network 298working domain name system running on your network or appropriate entries in
316or appropriate entries in your <path>/etc/hosts</path> file. 299your <path>/etc/hosts</path> file. <c>cupsaddsmb</c> often borks if hostnames
317<c>cupsaddsmb</c> often borks if hostnames don't point to the correct 300don't point to the correct machines.
318machines.
319</p>
320
321<p> 301</p>
302
303<p>
322Hopefully now you can make an assessment of what you'll actually need in 304Hopefully now you can make an assessment of what you'll actually need in order
323order to use Samba with your particular setup. The setup used for this 305to use Samba with your particular setup. The setup used for this HOWTO is:
324HOWTO is:
325</p> 306</p>
326 307
327<ul> 308<ul>
328 <li>oav</li> 309 <li>oav</li>
329 <li>cups</li> 310 <li>cups</li>
330 <li>readline</li> 311 <li>readline</li>
331 <li>pam</li> 312 <li>pam</li>
332</ul> 313</ul>
333 314
334<p> 315<p>
335To optimize performance, size and the time of the build, the 316To optimize performance, size and the time of the build, the USE flags are
336USE flags are specifically included or excluded. 317specifically included or excluded.
337</p> 318</p>
338 319
339<pre caption="Emerge Samba"> 320<pre caption="Emerge Samba">
340<comment>(Note the USE flags!)</comment> 321# <i>echo "net-fs/samba oav readline cups pam" &gt;&gt; /etc/portage/package.use</i>
341# <i>USE=&quot;oav readline cups pam -python -ldap -kerberos -xml -acl -mysql&quot; emerge net-fs/samba</i> 322# <i>emerge net-fs/samba</i>
342</pre> 323</pre>
343 324
344<note> 325<note>
345The following archs will need to add <e>~</e> to their <e>KEYWORDS</e>: x86, 326The following arches will need to add <e>~</e> to their <e>KEYWORDS</e>: x86,
346ppc, sparc, hppa, ia64 and alpha 327ppc, sparc, hppa, ia64 and alpha
347</note> 328</note>
348 329
349<p> 330<p>
350This will emerge Samba and CUPS (if CUPS is not already emerged). 331This will emerge Samba and CUPS (if CUPS is not already emerged).
351</p> 332</p>
352 333
353</body> 334</body>
354</section> 335</section>
355<section> 336<section>
356<title>Emerging Clam AV</title> 337<title>Emerging ClamAV</title>
357<body> 338<body>
358 339
359<p> 340<p>
360Because the <e>oav</e> USE flag only provides an interface to allow on access 341Because the <e>oav</e> USE flag only provides an interface to allow on access
361virus scanning, the actual virus scanner must be emerged. The scanner 342virus scanning, the actual virus scanner must be emerged. The scanner used in
362used in this HOWTO is Clam AV. 343this HOWTO is ClamAV.
363</p> 344</p>
364 345
365<pre caption="Emerge clam-av"> 346<pre caption="Emerge Clamav">
366# <i>emerge app-antivirus/clamav</i> 347# <i>emerge app-antivirus/clamav</i>
367</pre> 348</pre>
368 349
369</body> 350</body>
370</section> 351</section>
377</pre> 358</pre>
378 359
379</body> 360</body>
380</section> 361</section>
381<section> 362<section>
382<title>Emerging net-print/hpijs</title> 363<title>Emerging net-print/hplip</title>
383<body> 364<body>
384 365
385<p> 366<p>
386You only need to emerge this if you use an HP printer. 367You only need to emerge this if you use an HP printer.
387</p> 368</p>
388 369
389<pre caption="Emerge hpijs"> 370<pre caption="Emerge hplip">
390# <i>emerge net-print/hpijs</i> 371# <i>emerge net-print/hplip</i>
391</pre> 372</pre>
392 373
393</body> 374</body>
394</section> 375</section>
395</chapter> 376</chapter>
399<section> 380<section>
400<title>Configuring Samba</title> 381<title>Configuring Samba</title>
401<body> 382<body>
402 383
403<p> 384<p>
404The main Samba configuration file is <path>/etc/samba/smb.conf</path>. 385The main Samba configuration file is <path>/etc/samba/smb.conf</path>. It is
405It is divided in sections indicated by [sectionname]. Comments are either 386divided in sections indicated by [sectionname]. Comments are either
406# or ;. A sample <path>smb.conf</path> is included below with comments and 387# or ;. A sample <path>smb.conf</path> is included below with comments and
407suggestions for modifications. If more details are required, see the 388suggestions for modifications. If more details are required, see the man page
408man page for <path>smb.conf</path>, the installed 389for <path>smb.conf</path>, the installed <path>smb.conf.example</path>, the
409<path>smb.conf.example</path>, the Samba Web site or any of the 390Samba Web site or any of the numerous Samba books available.
410numerous Samba books available.
411</p> 391</p>
412 392
413<pre caption="A Sample /etc/samba/smb.conf"> 393<pre caption="A Sample /etc/samba/smb.conf">
414[global] 394[global]
415<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment> 395<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment>
416workgroup = <comment>MYWORKGROUPNAME</comment> 396workgroup = <comment>MYWORKGROUPNAME</comment>
417<comment># Of course this has no REAL purpose other than letting 397<comment># Of course this has no REAL purpose other than letting
418# everyone know its not Windows! 398# everyone knows it's not Windows!
419# %v prints the version of Samba we are using.</comment> 399# %v prints the version of Samba we are using.</comment>
420server string = Samba Server %v 400server string = Samba Server %v
421<comment># We are going to use cups, so we are going to put it in here ;-)</comment> 401<comment># We are going to use cups, so we are going to put it in here ;-)</comment>
422printcap name = cups 402printcap name = cups
423printing = cups 403printing = cups
446<comment># We now will implement the on access virus scanner. 426<comment># We now will implement the on access virus scanner.
447# NOTE: By putting this in our [Global] section, we enable 427# NOTE: By putting this in our [Global] section, we enable
448# scanning of ALL shares, you could optionally move 428# scanning of ALL shares, you could optionally move
449# these to a specific share and only scan it.</comment> 429# these to a specific share and only scan it.</comment>
450 430
451<comment># For Samba 3.x</comment> 431<comment># For Samba 3.x. This enables ClamAV on access scanning.</comment>
452vfs object = vscan-clamav 432vfs object = vscan-clamav
453vscan-clamav: config-file = /etc/samba/vscan-clamav.conf 433vscan-clamav: config-file = /etc/samba/vscan-clamav.conf
454
455<comment># For Samba 2.2.x</comment>
456vfs object = /usr/lib/samba/vfs/vscan-clamav.so
457vfs options = config-file = /etc/samba/vscan-clamav.conf
458 434
459<comment># Now we setup our print drivers information!</comment> 435<comment># Now we setup our print drivers information!</comment>
460[print$] 436[print$]
461comment = Printer Drivers 437comment = Printer Drivers
462path = /etc/samba/printer <comment># this path holds the driver structure</comment> 438path = /etc/samba/printer <comment># this path holds the driver structure</comment>
463guest ok = no 439guest ok = yes
464browseable = yes 440browseable = yes
465read only = yes 441read only = yes
466<comment># Modify this to "username,root" if you don't want root to 442<comment># Modify this to "username,root" if you don't want root to
467# be the only printer admin)</comment> 443# be the only printer admin)</comment>
468write list = <i>root</i> 444write list = <i>root</i>
481 457
482<comment># Now we setup our printers share. This should be 458<comment># Now we setup our printers share. This should be
483# browseable, printable, public.</comment> 459# browseable, printable, public.</comment>
484[printers] 460[printers]
485comment = All Printers 461comment = All Printers
486browseable = yes 462browseable = no
487printable = yes 463printable = yes
464writable = no
488public = yes 465public = yes
489guest ok = yes 466guest ok = yes
490path = /var/spool/samba 467path = /var/spool/samba
491<comment># Modify this to "username,root" if you don't want root to 468<comment># Modify this to "username,root" if you don't want root to
492# be the only printer admin)</comment> 469# be the only printer admin)</comment>
503guest ok = yes 480guest ok = yes
504path = /home/samba/public 481path = /home/samba/public
505</pre> 482</pre>
506 483
507<warn> 484<warn>
508If you like to use Samba's guest account to do anything concerning 485If you like to use Samba's guest account to do anything concerning printing from
509printing from Windows clients: don't set <c>guest only = yes</c> in 486Windows clients: don't set <c>guest only = yes</c> in the <c>[global]</c>
510the <c>[global]</c> section. The guest account seems to cause 487section. The guest account seems to cause problems when running
511problems when running <c>cupsaddsmb</c> sometimes when trying to 488<c>cupsaddsmb</c> sometimes when trying to connect from Windows machines. See
512connect from Windows machines. See below, too, when we talk about 489below, too, when we talk about <c>cupsaddsmb</c> and the problems that can
513<c>cupsaddsmb</c> and the problems that can arise. Use a dedicated
514printer user, like <c>printeruser</c> or <c>printer</c> or 490arise. Use a dedicated printer user, like <c>printeruser</c> or <c>printer</c>
515<c>printme</c> or whatever. It doesn't hurt and it will certainly 491or <c>printme</c> or whatever. It doesn't hurt and it will certainly protect you
516protect you from a lot of problems. 492from a lot of problems.
517</warn> 493</warn>
518 494
495<warn>
496Turning on ClamAV on access scanning in the <c>[global]</c> section will slow
497down the performance of your Samba server dramatically.
498</warn>
499
519<p> 500<p>
520Now create the directories required for the minimum configuration of 501Now create the directories required for the minimum configuration of Samba to
521Samba to share the installed printer throughout the network. 502share the installed printer throughout the network.
522</p> 503</p>
523 504
524<pre caption="Create the directories"> 505<pre caption="Create the directories">
525# <i>mkdir /etc/samba/printer</i> 506# <i>mkdir /etc/samba/printer</i>
526# <i>mkdir /var/spool/samba</i> 507# <i>mkdir /var/spool/samba</i>
527# <i>mkdir /home/samba/public</i> 508# <i>mkdir /home/samba/public</i>
528</pre> 509</pre>
529 510
530<p> 511<p>
531At least one Samba user is required in order to install the printer 512At least one Samba user is required in order to install the printer drivers and
532drivers and to allow users to connect to the printer. Users must 513to allow users to connect to the printer. Users must exist in the system's
533exist in the system's <path>/etc/passwd</path> file. 514<path>/etc/passwd</path> file.
534</p> 515</p>
535 516
536<pre caption="Creating the users"> 517<pre caption="Creating the users">
537# <i>smbpasswd -a root</i> 518# <i>smbpasswd -a root</i>
538 519
557</pre> 538</pre>
558 539
559</body> 540</body>
560</section> 541</section>
561<section> 542<section>
562<title>Configuring Clam AV</title> 543<title>Configuring ClamAV</title>
563<body> 544<body>
564 545
565<p> 546<p>
566The configuration file specified to be used in <path>smb.conf</path> is 547The configuration file specified to be used in <path>smb.conf</path> is
567<path>/etc/samba/vscan-clamav.conf</path>. While these options are set 548<path>/etc/samba/vscan-clamav.conf</path>. While these options are set to the
568to the defaults, the infected file action may need to be changed. 549defaults, the infected file action may need to be changed.
569</p> 550</p>
570 551
571<pre caption="/etc/samba/vscan-clamav.conf"> 552<pre caption="/etc/samba/vscan-clamav.conf">
572[samba-vscan] 553[samba-vscan]
573<comment>; run-time configuration for vscan-samba using 554<comment>; run-time configuration for vscan-samba using
623<comment>; an entry is invalidated after lru file entry lifetime (in seconds). 604<comment>; an entry is invalidated after lru file entry lifetime (in seconds).
624; (Default: 5)</comment> 605; (Default: 5)</comment>
625lru file entry lifetime = 5 606lru file entry lifetime = 5
626 607
627<comment>; socket name of clamd (default: /var/run/clamd)</comment> 608<comment>; socket name of clamd (default: /var/run/clamd)</comment>
628clamd socket name = /var/run/clamd 609clamd socket name = /tmp/clamd
629</pre>
630 610
611<comment>; port number the ScannerDaemon listens on</comment>
612oav port = 8127
613</pre>
614
631<p> 615<p>
632It is generally a good idea to start the virus scanner immediately. Add 616It is generally a good idea to start the virus scanner immediately. Add it to
633it to the <e>default</e> runlevel and then start the <c>clamd</c> service immediately. 617the <e>default</e> runlevel and then start the <c>clamd</c> service immediately.
618The service has two processes: freshclam keeps the virus definition database up
619to date while clamd is the actual anti-virus daemon. First you may want to set
620the paths of the logfiles so that it fits your needs.
621</p>
622
623<pre caption="Checking the location of the logfiles">
624# <i>vim /etc/clamd.conf</i>
625<comment>(Check the line "LogFile /var/log/clamd.log")</comment>
626# <i>vim /etc/freshclam.conf</i>
627<comment>(Check the line "UpdateLogFile /var/log/freshclam.log")</comment>
628# <i>vim /etc/conf.d/clamd</i>
629<comment>(Set "START_CLAMD=yes" and "START_FRESHCLAM=yes")</comment>
630</pre>
631
632<p>
633Now fire up the virus scanner.
634</p> 634</p>
635 635
636<pre caption="Add clamd to bootup and start it"> 636<pre caption="Add clamd to bootup and start it">
637# <i>rc-update add clamd default</i> 637# <i>rc-update add clamd default</i>
638# <i>/etc/init.d/clamd start</i> 638# <i>/etc/init.d/clamd start</i>
643<section> 643<section>
644<title>Configuring CUPS</title> 644<title>Configuring CUPS</title>
645<body> 645<body>
646 646
647<p> 647<p>
648This is a little more complicated. CUPS' main config file is 648This is a little more complicated. CUPS' main config file is
649<path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's 649<path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's
650<path>httpd.conf</path> file, so many you may find it familiar. Outlined 650<path>httpd.conf</path> file, so many you may find it familiar. Outlined in the
651in the example are the directives that need to be changed: 651example are the directives that need to be changed:
652</p> 652</p>
653 653
654<pre caption="/etc/cups/cupsd.conf"> 654<pre caption="/etc/cups/cupsd.conf">
655ServerName <i>PrintServer</i> <comment># your printserver name</comment> 655ServerName <i>PrintServer</i> <comment># your printserver name</comment>
656ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, eg you</comment> 656ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, e.g. you</comment>
657 657
658AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment> 658AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment>
659ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment> 659ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment>
660 660
661LogLevel debug <comment># only while isntalling and testing, should later be 661LogLevel debug <comment># only while isntalling and testing, should later be
662 # changed to 'info'</comment> 662 # changed to 'info'</comment>
663 663
664MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back, 664MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back,
665 # there seemed to be a bug in CUPS' controlling of the web interface, 665 # there seemed to be a bug in CUPS' controlling of the web interface,
666 # making CUPS think a denial of service attack was in progress when 666 # making CUPS think a denial of service attack was in progress when
667 # I tried to configure a printer with the web interface. weird.</comment> 667 # I tried to configure a printer with the web interface. weird.</comment>
670 670
671&lt;Location /&gt; 671&lt;Location /&gt;
672Order Deny,Allow 672Order Deny,Allow
673Deny From All 673Deny From All
674Allow From <i>192.168.1.*</i> <comment># the addresses of your internel network 674Allow From <i>192.168.1.*</i> <comment># the addresses of your internel network
675 # eg 192.168.1.* will allow connections from any host on 675 # e.g. 192.168.1.* will allow connections from any host on
676 # the 192.168.1.0 network. change to whatever suits you</comment> 676 # the 192.168.1.0 network. change to whatever suits you</comment>
677&lt;/Location&gt; 677&lt;/Location&gt;
678 678
679&lt;Location /admin&gt; 679&lt;Location /admin&gt;
680AuthType Basic 680AuthType Basic
697<comment>(The following line is found near the end of the file. Uncomment it)</comment> 697<comment>(The following line is found near the end of the file. Uncomment it)</comment>
698application/octet-stream application/vnd.cups-raw 0 698application/octet-stream application/vnd.cups-raw 0
699</pre> 699</pre>
700 700
701<p> 701<p>
702Edit <path>/etc/cups/mime.convs</path> to uncomment some lines. 702Edit <path>/etc/cups/mime.types</path> to uncomment some lines.
703</p> 703</p>
704 704
705<pre caption="/etc/cups/mime.types"> 705<pre caption="/etc/cups/mime.types">
706<comment>(The following line is found near the end of the file. Uncomment it)</comment> 706<comment>(The following line is found near the end of the file. Uncomment it)</comment>
707application/octet-stream 707application/octet-stream
712</p> 712</p>
713 713
714<pre caption="Setting up the CUPS service" > 714<pre caption="Setting up the CUPS service" >
715<comment>(To start CUPS on boot)</comment> 715<comment>(To start CUPS on boot)</comment>
716# <i>rc-update add cupsd default</i> 716# <i>rc-update add cupsd default</i>
717<comment>(To start CUPS if it isn't started)</comment> 717<comment>(To start or restart CUPS now)</comment>
718# <i>/etc/init.d/cupsd start</i>
719<comment>(If CUPS is already started we'll need to restart it!)</comment>
720# <i>/etc/init.d/cupsd restart</i> 718# <i>/etc/init.d/cupsd restart</i>
721</pre> 719</pre>
722 720
723</body> 721</body>
724</section> 722</section>
728 726
729<p> 727<p>
730First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to 728First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to
731find and download the correct PPD file for your printer and CUPS. To do so, 729find and download the correct PPD file for your printer and CUPS. To do so,
732click the link Printer Listings to the left. Select your printers manufacturer 730click the link Printer Listings to the left. Select your printers manufacturer
733and the model in the pulldown menu, eg HP and DeskJet 930C. Click "Show". On 731and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click "Show". On
734the page coming up click the "recommended driver" link after reading the 732the page coming up click the "recommended driver" link after reading the various
735various notes and information. Then fetch the PPD file from the next page, 733notes and information. Then fetch the PPD file from the next page, again after
736again after reading the notes and introductions there. You may have to select 734reading the notes and introductions there. You may have to select your printers
737your printers manufacturer and model again. Reading the <uri 735manufacturer and model again. Reading the <uri
738link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri> 736link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri> is
739is also very helpful when working with CUPS. 737also very helpful when working with CUPS.
740</p>
741
742<p> 738</p>
739
740<p>
743Now you have a PPD file for your printer to work with CUPS. Place it in 741Now you have a PPD file for your printer to work with CUPS. Place it in
744<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was 742<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was named
745named <path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer. 743<path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer.
746This can be done via the CUPS web interface or via command line. The web 744This can be done via the CUPS web interface or via command line. The web
747interface is found at <path>http://PrintServer:631</path> once CUPS is running. 745interface is found at <path>http://PrintServer:631</path> once CUPS is running.
748</p> 746</p>
749 747
750<pre caption="Install the printer via command line"> 748<pre caption="Install the printer via command line">
751# <i>lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd</i> 749# <i>lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd</i>
750# <i>/etc/init.d/cupsd restart</i>
752</pre> 751</pre>
753 752
754<p> 753<p>
755Remember to adjust to what you have. Be sure to have the name 754Remember to adjust to what you have. Be sure to have the name (<c>-p</c>
756(<c>-p</c> argument) right (the name you set above during the Samba 755argument) right (the name you set above during the Samba configuration!) and to
757configuration!) and to put in the correct <c>usb:/dev/usb/blah</c>, 756put in the correct <c>usb:/dev/usb/blah</c>, <c>parallel:/dev/blah</c> or
758<c>parallel:/dev/blah</c> or whatever device you are using for your 757whatever device you are using for your printer.
759printer.
760</p>
761
762<p> 758</p>
759
760<p>
763You should now be able to access the printer from the web interface 761You should now be able to access the printer from the web interface and be able
764and be able to print a test page. 762to print a test page.
765</p> 763</p>
766 764
767</body> 765</body>
768</section> 766</section>
769<section> 767<section>
770<title>Installing the Windows printer drivers</title> 768<title>Installing the Windows printer drivers</title>
771<body> 769<body>
772 770
773<p> 771<p>
774Now that the printer should be working it is time to install the drivers 772Now that the printer should be working it is time to install the drivers for the
775for the Windows clients to work. Samba 2.2 introduced this functionality. 773Windows clients to work. Samba 2.2 introduced this functionality. Browsing to
776Browsing to the print server in the Network Neighbourhood, right-clicking 774the print server in the Network Neighbourhood, right-clicking on the
777on the printershare and selecting "connect" downloads the appropriate 775printershare and selecting "connect" downloads the appropriate drivers
778drivers automagically to the connecting client, avoiding the hassle of 776automagically to the connecting client, avoiding the hassle of manually
779manually installing printer drivers locally. 777installing printer drivers locally.
780</p>
781
782<p> 778</p>
779
780<p>
783There are two sets of printer drivers for this. First, the Adobe PS 781There are two sets of printer drivers for this. First, the Adobe PS drivers
784drivers which can be obtained from <uri 782which can be obtained from <uri
785link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> 783link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript
786(PostScript printer drivers). Second, there are the CUPS PS drivers, 784printer drivers). Second, there are the CUPS PS drivers, to be obtained by
787to be obtained from <uri link="http://www.cups.org/software.php">the 785emerging <c>net-print/cups-windows</c>. Note that it may still be marked ~arch,
788CUPS homepage</uri> and selecting "CUPS Driver for Windows" from the 786so you may need to add it to <path>/etc/portage/package.keywords</path>. There
789pull down menu. There doesn't seem to be a difference between the 787doesn't seem to be a difference between the functionality of the two, but the
790functionality of the two, but the Adobe PS drivers need to be extracted 788Adobe PS drivers need to be extracted on a Windows System since it's a Windows
791on a Windows System since it's a Windows binary. Also the whole procedure 789binary. Also the whole procedure of finding and copying the correct files is a
792of finding and copying the correct files is a bit more hassle. The CUPS
793drivers seem to support some options the Adobe drivers don't. 790bit more hassle. The CUPS drivers seem to support some options the Adobe drivers
794</p> 791don't.
795
796<p> 792</p>
797This HOWTO uses the CUPS drivers for Windows. The downloaded file is 793
798called <path>cups-samba-5.0rc2.tar.gz</path>. Extract the files
799contained into a directory.
800</p> 794<p>
801 795This HOWTO uses the CUPS drivers for Windows. Install them as shown:
802<pre caption="Extract the drivers and run the install">
803# <i>tar -xzf cups-samba-5.0rc2.tar.gz</i>
804# <i>cd cups-samba-5.0rc2</i>
805<comment>(Only use this script if CUPS resides in /usr/share/cups)</comment>
806# <i>./cups-samba.install</i>
807</pre>
808
809<p> 796</p>
810<path>cups-samba.ss</path> is a TAR archive containing three files: 797
811<path>cups5.hlp</path>, <path>cupsdrvr5.dll</path> and 798<pre caption="Install the drivers and restart CUPS">
812<path>cupsui5.dll</path>. These are the actual driver files. 799# <i>emerge -av cups-windows</i>
800# <i>/etc/init.d/cupsd restart</i>
801</pre>
802
813</p> 803<p>
814
815<warn>
816The script <c>cups-samba.install</c> may not work for all *nixes (ie FreeBSD)
817because almost everything which is not part of the base system is
818installed somewhere under the prefix <path>/usr/local/</path>. This
819seems not to be the case for most things you install under GNU/Linux.
820However, if your CUPS installation is somewhere other than
821<path>/usr/share/cups/</path> see the example below.
822</warn>
823
824<p>
825Suppose your CUPS installation resides under
826<path>/usr/local/share/cups/</path>, and you want to install the drivers there.
827Do the following:
828</p>
829
830<pre caption="Manually installing the drivers">
831# <i>cd /path/you/extracted/the/CUPS-driver/tarball/into</i>
832# <i>tar -xf cups-samba.ss</i>
833<comment>(This extracts the files to usr/share/cups/drivers under the CURRENT WORKING DIRECTORY)</comment>
834# <i>cd usr/share/cups/drivers</i>
835<comment>(no leading / !)</comment>
836# <i>cp cups* /usr/local/share/cups/drivers</i>
837</pre>
838
839<p>
840Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS 804Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS distribution.
841distribution. It's man page is an interesting read. 805Its man page is an interesting read.
842</p> 806</p>
843 807
844<pre caption="Run cupsaddsmb"> 808<pre caption="Run cupsaddsmb">
845# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C</i> 809# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C</i>
846<comment>(Instead of HPDeskJet930C you could also specify "-a", which will 810<comment>(Instead of HPDeskJet930C you could also specify "-a", which will
847"export all known printers".)</comment> 811"export all known printers".)</comment>
848# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -a</i> 812# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -a</i>
849</pre> 813</pre>
850 814
851<warn> 815<warn>
852The execution of this command often causes the most trouble. 816The execution of this command often causes the most trouble. Read through the
853Reading through the <uri
854link="http://forums.gentoo.org/viewtopic.php?t=110931">posts in this 817<uri link="http://forums.gentoo.org/viewtopic.php?t=110931">posts in this
855thread</uri>. 818thread</uri> for some troubleshooting tips.
856</warn> 819</warn>
857 820
858<p> 821<p>
859Here are common errors that may happen: 822Here are common errors that may happen:
860</p> 823</p>
861 824
862<ul> 825<ul>
863 <li> 826 <li>
864 The hostname given as a parameter for <c>-h</c> and <c>-H</c> 827 The hostname given as a parameter for <c>-h</c> and <c>-H</c>
865 (<c>PrintServer</c>) often does not resolve correctly and doesn't 828 (<c>PrintServer</c>) often does not resolve correctly and doesn't identify
866 identify the print server for CUPS/Samba interaction. If an error 829 the print server for CUPS/Samba interaction. If an error like: <b>Warning:
867 like: <b>Warning: No PPD file for printer "CUPS_PRINTER_NAME" - 830 No PPD file for printer "CUPS_PRINTER_NAME" - skipping!</b> occurs, the
868 skipping!</b> occurs, the first thing you should do is substitute 831 first thing you should do is substitute <c>PrintServer</c> with
869 <c>PrintServer</c> with <c>localhost</c> and try it again. 832 <c>localhost</c> and try it again.
870 </li> 833 </li>
871 <li> 834 <li>
872 The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message 835 The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message
873 is quite common, but can be triggered by many problems. It's unfortunately 836 is quite common, but can be triggered by many problems. It's unfortunately
874 not very helpful. One thing to try is to temporarily set <c>security = 837 not very helpful. One thing to try is to temporarily set <c>security =
875 user</c> in your <path>smb.conf</path>. After/if the installation completes 838 user</c> in your <path>smb.conf</path>. After/if the installation completes
876 successfully, you should set it back to share, or whatever it was set to 839 successfully, you should set it back to share, or whatever it was set to
877 before. 840 before.
878 </li> 841 </li>
879</ul> 842</ul>
880 843
881<p> 844<p>
882This should install the correct driver directory structure under 845This should install the correct driver directory structure under
883<path>/etc/samba/printer</path>. That would be 846<path>/etc/samba/printer</path>. That would be
884<path>/etc/samba/printer/W32X86/2/</path>. The files contained should 847<path>/etc/samba/printer/W32X86/2/</path>. The files contained should be the 3
885be the 3 driver files and the PPD file, renamed to YourPrinterName.ppd 848driver files and the PPD file, renamed to <path>YourPrinterName.ppd</path> (the
886(the name which you gave the printer when installing it (see above). 849name which you gave the printer when installing it (see above).
887</p>
888
889<p> 850</p>
851
852<p>
890Pending no errors or other complications, your drivers are now 853Pending no errors or other complications, your drivers are now installed.
891installed.
892</p> 854</p>
893 855
894</body> 856</body>
895</section> 857</section>
896<section> 858<section>
914<title>Testing our Samba configuration</title> 876<title>Testing our Samba configuration</title>
915<body> 877<body>
916 878
917<p> 879<p>
918We will want to test our configuration file to ensure that it is formatted 880We will want to test our configuration file to ensure that it is formatted
919properly and all of our options have at least the correct syntax. To do 881properly and all of our options have at least the correct syntax. To do this we
920this we run <c>testparm</c>. 882run <c>testparm</c>.
921</p> 883</p>
922 884
923<pre caption="Running the testparm"> 885<pre caption="Running the testparm">
924<comment>(By default, testparm checks /etc/samba/smb.conf)</comment> 886<comment>(By default, testparm checks /etc/samba/smb.conf)</comment>
925# <i>/usr/bin/testparm</i> 887# <i>/usr/bin/testparm</i>
955<section> 917<section>
956<title>Checking our services</title> 918<title>Checking our services</title>
957<body> 919<body>
958 920
959<p> 921<p>
960It would probably be prudent to check our logs at this time also. 922It would probably be prudent to check our logs at this time also. We will also
961We will also want to take a peak at our Samba shares using 923want to take a peak at our Samba shares using <c>smbclient</c>.
962<c>smbclient</c>.
963</p> 924</p>
964 925
965<pre caption="Checking the shares with smbclient"> 926<pre caption="Checking the shares with smbclient">
966# <i>smbclient -L localhost</i> 927# <i>smbclient -L localhost</i>
967Password: 928Password:
977<section> 938<section>
978<title>Printer configuration of *nix based clients</title> 939<title>Printer configuration of *nix based clients</title>
979<body> 940<body>
980 941
981<p> 942<p>
982Despite the variation or distribution, the only thing needed is CUPS. 943Despite the variation or distribution, the only thing needed is CUPS. Do the
983Do the equivalent on any other UNIX/Linux/BSD client. 944equivalent on any other UNIX/Linux/BSD client.
984</p> 945</p>
985 946
986<pre caption="Configuring a Gentoo system"> 947<pre caption="Configuring a Gentoo system">
987# <i>emerge cups</i> 948# <i>emerge cups</i>
988# <i>/etc/init.d/cupsd start</i> 949# <i>nano -w /etc/cups/client.conf</i>
989# <i>rc-update add cupsd default</i> 950ServerName <i>PrintServer</i> <comment># your printserver name</comment>
990</pre> 951</pre>
991 952
992<p>
993That should be it. Nothing else will be needed. Just point your web
994browser to <c>http://localhost:631</c> on the client and you'll see that
995PrintServer broadcasts all available printers to all CUPS clients.
996</p> 953<p>
997 954That should be it. Nothing else will be needed.
998<p> 955</p>
999To print, use for example 956
1000</p> 957<p>
958If you use only one printer, it will be your default printer. If your print
959server manages several printers, your administrator will have defined a default
960printer on the server. If you want to define a different default printer for
961yourself, use the <c>lpoptions</c> command.
962</p>
963
964<pre caption="Setting your default printer">
965<comment>(List available printers)</comment>
966# <i>lpstat -a</i>
967<comment>(Sample output, yours will differ)</comment>
968HPDeskJet930C accepting requests since Jan 01 00:00
969laser accepting requests since Jan 01 00:00
970<comment>(Define HPDeskJet930C as your default printer)</comment>
971# <i>lpoptions -d HPDeskJet930C</i>
972</pre>
1001 973
1002<pre caption="Printing in *nix"> 974<pre caption="Printing in *nix">
975<comment>(Specify the printer to be used)</comment>
1003# <i>lpr -pHPDeskJet930C anything.txt</i> 976# <i>lp -d HPDeskJet930C anything.txt</i>
1004# <i>lpr -PHPDeskJet930C foobar.whatever.ps</i> 977<comment>(Use your default printer)</comment>
1005</pre>
1006
1007<p>
1008In order to setup a default printer, you have to edit
1009<path>/etc/cups/client.conf</path> and set the directive
1010<c>ServerName</c> to your printserver. In the case of this guide that
1011would be the following example.
1012</p>
1013
1014<pre caption="/etc/cups/client.conf">
1015ServerName PrintServer
1016</pre>
1017
1018<p>
1019The following will print <path>foorbar.whatever.ps</path> directly to the print
1020server.
1021</p>
1022
1023<pre caption="Printing to the default printer">
1024$ <i>lpr foobar.whatever.ps</i> 978# <i>lp foobar.whatever.ps</i>
1025</pre> 979</pre>
1026 980
1027<p>
1028Some common observations when setting a default printer in this manner
1029include the following:
1030</p> 981<p>
1031 982Just point your web browser to <c>http://printserver:631</c> on the client if
1032<ul> 983you want to manage your printers and their jobs with a nice web interface.
1033 <li> 984Replace <c>printserver</c> with the name of the <e>machine</e> that acts as your
1034 Setting the <c>ServerName</c> in <path>client.conf</path> seems to 985print server, not the name you gave to the cups print server if you used
1035 work well for only one printer, there may be yet another way to 986different names.
1036 set a client's default remote printer. 987</p>
1037 </li>
1038 <li>
1039 Also, when accessing <c>http://localhost:631</c> on the client
1040 now, no printers seem to be "found" by the client-CUPS. This is to
1041 be expected when setting <c>ServerName</c> in
1042 <path>client.conf</path>.
1043 </li>
1044</ul>
1045 988
1046</body> 989</body>
1047</section> 990</section>
1048<section> 991<section>
1049<title>Mounting a Windows or Samba share in GNU/Linux</title> 992<title>Mounting a Windows or Samba share in GNU/Linux</title>
1050<body> 993<body>
1051 994
1052<p> 995<p>
1053Now is time to configure our kernel to support smbfs. Since I'm assumming we've 996Now is time to configure our kernel to support smbfs. Since I'm assumming we've
1054all compiled at least one kernel, we'll need to make sure we have all the right 997all compiled at least one kernel, we'll need to make sure we have all the right
1055options selected in our kernel. For simplicity sake, make it a module for ease 998options selected in our kernel. For simplicity's sake, make it a module for ease
1056of use. It is the author's opinion that kernel modules are a good thing and 999of use. It is the author's opinion that kernel modules are a good thing and
1057should be used whenever possible. 1000should be used whenever possible.
1058</p> 1001</p>
1059 1002
1060<pre caption="Relevant kernel options" > 1003<pre caption="Relevant kernel options" >
1061CONFIG_SMB_FS=m 1004CONFIG_SMB_FS=m
1069<pre caption="Loading the kernel module"> 1012<pre caption="Loading the kernel module">
1070# <i>modprobe smbfs</i> 1013# <i>modprobe smbfs</i>
1071</pre> 1014</pre>
1072 1015
1073<p> 1016<p>
1074Once the modules is loaded, mounting a Windows or Samba share is 1017Once the module is loaded, mounting a Windows or Samba share is possible. Use
1075possible. Use <c>mount</c> to accomplish this, as detailed below: 1018<c>mount</c> to accomplish this, as detailed below:
1076</p> 1019</p>
1077 1020
1078<pre caption="Mounting a Windows/Samba share"> 1021<pre caption="Mounting a Windows/Samba share">
1079<comment>(The syntax for mounting a Windows/Samba share is: 1022<comment>(The syntax for mounting a Windows/Samba share is:
1080 mount -t smbfs [-o username=xxx,password=xxx] //server/share /mnt/point 1023 mount -t smbfs [-o username=xxx,password=xxx] //server/share /mnt/point
1085<comment>(If a password is needed)</comment> 1028<comment>(If a password is needed)</comment>
1086# <i>mount -t smbfs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i> 1029# <i>mount -t smbfs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i>
1087</pre> 1030</pre>
1088 1031
1089<p> 1032<p>
1090After you mount the share, you would access it as if it were a local 1033After you mount the share, you would access it as if it were a local drive.
1091drive.
1092</p> 1034</p>
1093 1035
1094</body> 1036</body>
1095</section> 1037</section>
1096<section> 1038<section>
1097<title>Printer Configuration for Windows NT/2000/XP clients</title> 1039<title>Printer Configuration for Windows NT/2000/XP clients</title>
1098<body> 1040<body>
1099 1041
1100<p> 1042<p>
1101That's just a bit of point-and-click. Browse to 1043That's just a bit of point-and-click. Browse to <path>\\PrintServer</path> and
1102<path>\\PrintServer</path> and right click on the printer 1044right click on the printer (HPDeskJet930C) and click connect. This will download
1103(HPDeskJet930C) and click connect. This will download the drivers to
1104the Windows client and now every application (such as Word or Acrobat) 1045the drivers to the Windows client and now every application (such as Word or
1105will offer HPDeskJet930C as an available printer to print to. :-) 1046Acrobat) will offer HPDeskJet930C as an available printer to print to. :-)
1106</p> 1047</p>
1107 1048
1108</body> 1049</body>
1109</section> 1050</section>
1110</chapter> 1051</chapter>
1114<section> 1055<section>
1115<title>A Fond Farewell</title> 1056<title>A Fond Farewell</title>
1116<body> 1057<body>
1117 1058
1118<p> 1059<p>
1119Well that should be it. You should now have a successful printing enviroment 1060That should be it. You should now have a successful printing enviroment that is
1120that is friendly to both Windows and *nix as well as a fully virus-free working 1061friendly to both Windows and *nix as well as a fully virus-free working share!
1121share!
1122</p> 1062</p>
1123 1063
1124</body> 1064</body>
1125</section> 1065</section>
1126</chapter> 1066</chapter>
1136troubleshooting your installation: 1076troubleshooting your installation:
1137</p> 1077</p>
1138 1078
1139<ul> 1079<ul>
1140 <li><uri link="http://www.cups.org/">CUPS Homepage</uri></li> 1080 <li><uri link="http://www.cups.org/">CUPS Homepage</uri></li>
1081 <li>
1141 <li><uri link="http://www.samba.org/">Samba Homepage</uri></li> 1082 <uri link="http://www.samba.org/">Samba Homepage</uri>, especially the <uri
1083 link="http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/CUPS-printing.html">chapter
1084 on Samba/CUPS configuration</uri>
1085 </li>
1142 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li> 1086 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li>
1143 <li> 1087 <li>
1144 <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt 1088 <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt
1145 Pfeifle's Samba Print HOWTO</uri> ( 1089 Pfeifle's Samba Print HOWTO</uri> ( This HOWTO really covers <e>ANYTHING</e>
1146 This HOWTO really covers <e>ANYTHING</e> and <e>EVERYTHING</e>
1147 I've written here, plus a LOT more concerning CUPS and Samba, and 1090 and <e>EVERYTHING</e> I've written here, plus a LOT more concerning CUPS and
1148 generally printing support on networks. A really interesting read, 1091 Samba, and generally printing support on networks. A really interesting
1149 with lots and lots of details) 1092 read, with lots and lots of details.)
1150 </li> 1093 </li>
1151 <li><uri link="http://www.freebsddiary.org/cups.php">FreeBSD Diary's CUPS Topic</uri></li> 1094 <li><uri link="http://www.freebsddiary.org/cups.php">FreeBSD Diary's CUPS Topic</uri></li>
1152</ul> 1095</ul>
1153 1096
1154</body> 1097</body>
1156<section> 1099<section>
1157<title>Troubleshooting</title> 1100<title>Troubleshooting</title>
1158<body> 1101<body>
1159 1102
1160<p> 1103<p>
1104See <uri
1161See <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37">this 1105link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37">this
1162page</uri> from Kurt Pfeifle's "Printing Support in Samba 3.0" 1106page</uri> from Kurt Pfeifle's "Printing Support in Samba 3.0" manual. Lots of
1163manual. Lots of useful tips there! Be sure to look this one up 1107useful tips there! Be sure to look this one up first, before posting questions
1164first, before posting questions and problems! Maybe the solution 1108and problems! Maybe the solution you're looking for is right there.
1165you're looking for is right there.
1166</p> 1109</p>
1167 1110
1168</body> 1111</body>
1169</section> 1112</section>
1170</chapter> 1113</chapter>

Legend:
Removed from v.1.9  
changed lines
  Added in v.1.30

  ViewVC Help
Powered by ViewVC 1.1.20