/[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.26 Revision 1.29
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.26 2006/12/25 17:30:26 nightmorph Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.29 2007/06/06 23:23:35 nightmorph Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4<guide link="/doc/en/quick-samba-howto.xml"> 4<guide link="/doc/en/quick-samba-howto.xml">
5<title>Gentoo Samba3/CUPS/ClamAV 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>
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 12
13<abstract> 13<abstract>
14Setup, install and configure a Samba Server under Gentoo that shares 14Setup, install and configure a Samba Server under Gentoo that shares files,
15files, printers without the need to install drivers and provides 15printers without the need to install drivers and provides automatic virus
16automatic virus scanning. 16scanning.
17</abstract> 17</abstract>
18 18
19<!-- The content of this document is licensed under the CC-BY-SA license --> 19<!-- The content of this document is licensed under the CC-BY-SA license -->
20<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 20<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
21<license/> 21<license/>
22 22
23<version>1.15</version> 23<version>1.17</version>
24<date>2006-12-25</date> 24<date>2007-06-06</date>
25 25
26<chapter> 26<chapter>
27<title>Introduction to this HOWTO</title> 27<title>Introduction to this HOWTO</title>
28<section> 28<section>
29<title>Purpose</title> 29<title>Purpose</title>
30<body> 30<body>
31 31
32<p> 32<p>
33This HOWTO is designed to help you move a network from many different 33This HOWTO is designed to help you move a network from many different clients
34clients speaking different languages, to many different machines that 34speaking different languages, to many different machines that speak a common
35speak a common language. The ultimate goal is to help differing 35language. The ultimate goal is to help differing architectures and technologies,
36architectures and technologies, come together in a productive, 36come together in a productive, happily coexisting environment.
37happily coexisting environment.
38</p>
39
40<p> 37</p>
38
39<p>
41Following the directions outlined in this HOWTO should give you an 40Following the directions outlined in this HOWTO should give you an excellent
42excellent step towards a peaceful cohabitation between Windows, and 41step towards a peaceful cohabitation between Windows, and virtually all known
43virtually all known variations of *nix. 42variations of *nix.
44</p>
45
46<p> 43</p>
44
45<p>
47This HOWTO originally started not as a HOWTO, but as a FAQ. It was 46This 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, 47explore the functionality and power of the Gentoo system, portage and the
49portage and the flexibility of USE flags. Like so many other projects, 48flexibility of USE flags. Like so many other projects, it was quickly discovered
50it was quickly discovered what was missing in the Gentoo realm: there 49what 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 50for Gentoo users. These users are more demanding than most; they require
52more demanding than most; they require performance, flexibility and 51performance, 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 52this HOWTO was not intended for other distributions; rather that it was designed
55with a highly customized version of Samba. 53to work with a highly customized version of Samba.
56</p>
57
58<p> 54</p>
55
56<p>
59This HOWTO will describe how to share files and printers between Windows 57This 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 58*nix PCs. It will also demonstrate the use of the VFS (Virtual File System)
61File System) feature of Samba to incorporate automatic virus protection. 59feature 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. 60show you how to mount and manipulate shares.
63</p>
64
65<p> 61</p>
62
63<p>
66There are a few topics that will be mentioned, but are out of the 64There 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. 65HOWTO. These will be noted as they are presented.
68</p>
69
70<p> 66</p>
67
68<p>
71This HOWTO is based on a compilation and merge of an excellent HOWTO 69This 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> 70the <uri link="http://forums.gentoo.org">Gentoo forums</uri> by Andreas "daff"
73by Andreas "daff" Ntaflos and the collected knowledge of Joshua Preston. 71Ntaflos and the collected knowledge of Joshua Preston. The link to this
74The link to this discussion is provided below for your reference: 72discussion is provided below for your reference:
75</p> 73</p>
76 74
77<ul> 75<ul>
78 <li> 76 <li>
79 <uri link="http://forums.gentoo.org/viewtopic.php?t=110931">HOWTO 77 <uri link="http://forums.gentoo.org/viewtopic.php?t=110931">HOWTO
87<title>Before you use this guide</title> 85<title>Before you use this guide</title>
88<body> 86<body>
89 87
90<p> 88<p>
91There are a several other guides for setting up CUPS and/or Samba, please read 89There 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 90them 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 91otherwise). One such document is the very useful and well written <uri
94link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration 92link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration
95issues and specific printer setup is not discussed here. 93issues and specific printer setup is not discussed here.
96</p> 94</p>
97 95
98</body> 96</body>
100<section> 98<section>
101<title>Brief Overview</title> 99<title>Brief Overview</title>
102<body> 100<body>
103 101
104<p> 102<p>
105After presenting the various USE flags, the following list will outline 103After presenting the various USE flags, the following list will outline all of
106all of the topics covered as they are presented: 104the topics covered as they are presented:
107</p> 105</p>
108 106
109<ul> 107<ul>
110 <li>On the Samba server: 108 <li>On the Samba server:
111 <ul> 109 <ul>
144<ul> 142<ul>
145 <li>net-fs/samba</li> 143 <li>net-fs/samba</li>
146 <li>app-antivirus/clamav</li> 144 <li>app-antivirus/clamav</li>
147 <li>net-print/cups</li> 145 <li>net-print/cups</li>
148 <li>net-print/foomatic</li> 146 <li>net-print/foomatic</li>
149 <li>net-print/hpijs (if you have an HP printer)</li> 147 <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> 148 <li>A kernel of sorts (2.6)</li>
151 <li>A printer (PS or non-PS, maybe not TOO new or fancy)</li> 149 <li>A printer (PS or non-PS, maybe not TOO new or fancy)</li>
152 <li> 150 <li>
153 A working network (home/office/etc) consisting of more than one machine) 151 A working network (home/office/etc) consisting of more than one machine)
154 </li> 152 </li>
155</ul> 153</ul>
156 154
157<p> 155<p>
158The main package we use here is net-fs/samba, however, you will need 156The 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 157with 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. 158another computer. CUPS will be emerged if it is not already.
161app-antivirus/clamav will be used also, but others should be easily adapted 159app-antivirus/clamav will be used also, but others should be easily adapted to
162to work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning 160work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning
163technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ... 161technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ...
164</p> 162</p>
165 163
166</body> 164</body>
167</section> 165</section>
172<section> 170<section>
173<title>The USE Flags</title> 171<title>The USE Flags</title>
174<body> 172<body>
175 173
176<p> 174<p>
177Before emerging anything, take a look at the various USE flags 175Before emerging anything, take a look at some of the various USE flags available
178available to Samba. 176to Samba.
179</p> 177</p>
180 178
181<pre caption="Samba uses the following USE Variables:"> 179<pre caption="Samba uses the following USE Variables:">
182kerberos mysql xml acl cups ldap pam readline python oav libclamav 180kerberos acl cups ldap pam readline python oav
183</pre> 181</pre>
184 182
185<p> 183<p>
186Depending on the network topology and the specific requirements of 184Depending on the network topology and the specific requirements of the server,
187the server, the USE flags outlined below will define what to include or 185the USE flags outlined below will define what to include or exclude from the
188exclude from the emerging of Samba. 186emerging of Samba.
189</p> 187</p>
190 188
191<table> 189<table>
192<tr> 190<tr>
193 <th><b>USE flag</b></th> 191 <th><b>USE flag</b></th>
200 intended to join an existing domain or Active Directory. See the note 198 intended to join an existing domain or Active Directory. See the note
201 below for more information. 199 below for more information.
202 </ti> 200 </ti>
203</tr> 201</tr>
204<tr> 202<tr>
205 <th><b>mysql</b></th>
206 <ti>
207 This will allow Samba to use MySQL in order to do password authentication.
208 It will store ACLs, usernames, passwords, etc in a database versus a
209 flat file. If Samba is needed to do password authentication, such as
210 acting as a password validation server or a Primary Domain Controller
211 (PDC).
212 </ti>
213</tr>
214<tr>
215 <th><b>xml</b></th>
216 <ti>
217 The xml USE option for Samba provides a password database backend allowing
218 Samba to store account details in XML files, for the same reasons listed in
219 the mysql USE flag description.
220 </ti>
221</tr>
222<tr>
223 <th><b>acl</b></th> 203 <th><b>acl</b></th>
224 <ti> 204 <ti>
225 Enables Access Control Lists. The ACL support in Samba uses a patched 205 Enables Access Control Lists. The ACL support in Samba uses a patched
226 ext2/ext3, or SGI's XFS in order to function properly as it extends more 206 ext2/ext3, or SGI's XFS in order to function properly as it extends more
227 detailed access to files or directories; much more so than typical *nix 207 detailed access to files or directories; much more so than typical *nix
229 </ti> 209 </ti>
230</tr> 210</tr>
231<tr> 211<tr>
232 <th><b>cups</b></th> 212 <th><b>cups</b></th>
233 <ti> 213 <ti>
234 This enables support for the Common Unix Printing System. This 214 This enables support for the Common Unix Printing System. This provides an
235 provides an interface allowing local CUPS printers to be shared to 215 interface allowing local CUPS printers to be shared to other systems in the
236 other systems in the network. 216 network.
237 </ti> 217 </ti>
238</tr> 218</tr>
239<tr> 219<tr>
240 <th><b>ldap</b></th> 220 <th><b>ldap</b></th>
241 <ti> 221 <ti>
242 Enables the Lightweight Directory Access Protocol (LDAP). If Samba is 222 Enables the Lightweight Directory Access Protocol (LDAP). If Samba is
243 expected to use Active Directory, this option must be used. This would 223 expected to use Active Directory, this option must be used. This would be
244 be used in the event Samba needs to login to or provide login to 224 used in the event Samba needs to login to or provide login to a
245 a Domain/Active Directory Server. The kerberos USE flag is needed for 225 Domain/Active Directory Server. The kerberos USE flag is needed for proper
246 proper functioning of this option. 226 functioning of this option.
247 </ti> 227 </ti>
248</tr> 228</tr>
249<tr> 229<tr>
250 <th><b>pam</b></th> 230 <th><b>pam</b></th>
251 <ti> 231 <ti>
252 Include support for pluggable authentication modules (PAM). This 232 Include support for pluggable authentication modules (PAM). This provides
253 provides the ability to authenticate users on the Samba Server, which is 233 the ability to authenticate users on the Samba Server, which is required if
254 required if users have to login to your server. The kerberos USE flag 234 users have to login to your server. The kerberos USE flag is recommended
255 is recommended along with this option. 235 along with this option.
256 </ti> 236 </ti>
257</tr> 237</tr>
258<tr> 238<tr>
259 <th><b>readline</b></th> 239 <th><b>readline</b></th>
260 <ti> 240 <ti>
261 Link Samba against libreadline. This is highly recommended and should 241 Link Samba against libreadline. This is highly recommended and should
262 probably not be disabled 242 probably not be disabled.
263 </ti> 243 </ti>
264</tr> 244</tr>
265<tr> 245<tr>
266 <th><b>python</b></th> 246 <th><b>python</b></th>
267 <ti> 247 <ti>
268 Python bindings API. Provides an API that will allow Python to 248 Python bindings API. Provides an API that will allow Python to interface
269 interface with Samba. 249 with Samba.
270 </ti> 250 </ti>
271</tr> 251</tr>
272<tr> 252<tr>
273 <th><b>oav</b></th> 253 <th><b>oav</b></th>
274 <ti> 254 <ti>
275 Provides on-access scanning of Samba shares with FRISK F-Prot 255 Provides on-access scanning of Samba shares with FRISK F-Prot Daemon,
276 Daemon, Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep 256 Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep (SAVI),
277 (SAVI), Symantec CarrierScan, and Trend Micro (VSAPI). 257 Symantec CarrierScan, and Trend Micro (VSAPI).
278 </ti>
279</tr>
280<tr>
281 <th><b>libclamav</b></th>
282 <ti>
283 Use the ClamAV library instead of the clamd daemon
284 </ti> 258 </ti>
285</tr> 259</tr>
286</table> 260</table>
287 261
288<p> 262<p>
315<section> 289<section>
316<title>Emerging Samba</title> 290<title>Emerging Samba</title>
317<body> 291<body>
318 292
319<p> 293<p>
320First of all: be sure that all your hostnames resolve correctly. 294First of all: be sure that all your hostnames resolve correctly. Either have a
321Either have a working domain name system running on your network 295working domain name system running on your network or appropriate entries in
322or appropriate entries in your <path>/etc/hosts</path> file. 296your <path>/etc/hosts</path> file. <c>cupsaddsmb</c> often borks if hostnames
323<c>cupsaddsmb</c> often borks if hostnames don't point to the correct 297don't point to the correct machines.
324machines.
325</p>
326
327<p> 298</p>
299
300<p>
328Hopefully now you can make an assessment of what you'll actually need in 301Hopefully now you can make an assessment of what you'll actually need in order
329order to use Samba with your particular setup. The setup used for this 302to use Samba with your particular setup. The setup used for this HOWTO is:
330HOWTO is:
331</p> 303</p>
332 304
333<ul> 305<ul>
334 <li>oav</li> 306 <li>oav</li>
335 <li>cups</li> 307 <li>cups</li>
336 <li>readline</li> 308 <li>readline</li>
337 <li>pam</li> 309 <li>pam</li>
338</ul> 310</ul>
339 311
340<p> 312<p>
341To optimize performance, size and the time of the build, the 313To optimize performance, size and the time of the build, the USE flags are
342USE flags are specifically included or excluded. 314specifically included or excluded.
343</p> 315</p>
344 316
345<pre caption="Emerge Samba"> 317<pre caption="Emerge Samba">
346# <i>echo "net-fs/samba oav readline cups pam" &gt;&gt; /etc/portage/package.use</i> 318# <i>echo "net-fs/samba oav readline cups pam" &gt;&gt; /etc/portage/package.use</i>
347# <i>emerge net-fs/samba</i> 319# <i>emerge net-fs/samba</i>
348</pre> 320</pre>
349 321
350<note> 322<note>
351The following archs will need to add <e>~</e> to their <e>KEYWORDS</e>: x86, 323The following arches will need to add <e>~</e> to their <e>KEYWORDS</e>: x86,
352ppc, sparc, hppa, ia64 and alpha 324ppc, sparc, hppa, ia64 and alpha
353</note> 325</note>
354 326
355<p> 327<p>
356This will emerge Samba and CUPS (if CUPS is not already emerged). 328This will emerge Samba and CUPS (if CUPS is not already emerged).
361<section> 333<section>
362<title>Emerging ClamAV</title> 334<title>Emerging ClamAV</title>
363<body> 335<body>
364 336
365<p> 337<p>
366Because the <e>oav</e> USE flag only provides an interface to allow on access 338Because the <e>oav</e> USE flag only provides an interface to allow on access
367virus scanning, the actual virus scanner must be emerged. The scanner 339virus scanning, the actual virus scanner must be emerged. The scanner used in
368used in this HOWTO is ClamAV. 340this HOWTO is ClamAV.
369</p> 341</p>
370 342
371<pre caption="Emerge Clamav"> 343<pre caption="Emerge Clamav">
372# <i>emerge app-antivirus/clamav</i> 344# <i>emerge app-antivirus/clamav</i>
373</pre> 345</pre>
383</pre> 355</pre>
384 356
385</body> 357</body>
386</section> 358</section>
387<section> 359<section>
388<title>Emerging net-print/hpijs</title> 360<title>Emerging net-print/hplip</title>
389<body> 361<body>
390 362
391<p> 363<p>
392You only need to emerge this if you use an HP printer. 364You only need to emerge this if you use an HP printer.
393</p> 365</p>
394 366
395<pre caption="Emerge hpijs"> 367<pre caption="Emerge hplip">
396# <i>emerge net-print/hpijs</i> 368# <i>emerge net-print/hplip</i>
397</pre> 369</pre>
398 370
399</body> 371</body>
400</section> 372</section>
401</chapter> 373</chapter>
405<section> 377<section>
406<title>Configuring Samba</title> 378<title>Configuring Samba</title>
407<body> 379<body>
408 380
409<p> 381<p>
410The main Samba configuration file is <path>/etc/samba/smb.conf</path>. 382The main Samba configuration file is <path>/etc/samba/smb.conf</path>. It is
411It is divided in sections indicated by [sectionname]. Comments are either 383divided in sections indicated by [sectionname]. Comments are either
412# or ;. A sample <path>smb.conf</path> is included below with comments and 384# or ;. A sample <path>smb.conf</path> is included below with comments and
413suggestions for modifications. If more details are required, see the 385suggestions for modifications. If more details are required, see the man page
414man page for <path>smb.conf</path>, the installed 386for <path>smb.conf</path>, the installed <path>smb.conf.example</path>, the
415<path>smb.conf.example</path>, the Samba Web site or any of the 387Samba Web site or any of the numerous Samba books available.
416numerous Samba books available.
417</p> 388</p>
418 389
419<pre caption="A Sample /etc/samba/smb.conf"> 390<pre caption="A Sample /etc/samba/smb.conf">
420[global] 391[global]
421<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment> 392<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment>
506guest ok = yes 477guest ok = yes
507path = /home/samba/public 478path = /home/samba/public
508</pre> 479</pre>
509 480
510<warn> 481<warn>
511If you like to use Samba's guest account to do anything concerning 482If you like to use Samba's guest account to do anything concerning printing from
512printing from Windows clients: don't set <c>guest only = yes</c> in 483Windows clients: don't set <c>guest only = yes</c> in the <c>[global]</c>
513the <c>[global]</c> section. The guest account seems to cause 484section. The guest account seems to cause problems when running
514problems when running <c>cupsaddsmb</c> sometimes when trying to 485<c>cupsaddsmb</c> sometimes when trying to connect from Windows machines. See
515connect from Windows machines. See below, too, when we talk about 486below, too, when we talk about <c>cupsaddsmb</c> and the problems that can
516<c>cupsaddsmb</c> and the problems that can arise. Use a dedicated
517printer user, like <c>printeruser</c> or <c>printer</c> or 487arise. Use a dedicated printer user, like <c>printeruser</c> or <c>printer</c>
518<c>printme</c> or whatever. It doesn't hurt and it will certainly 488or <c>printme</c> or whatever. It doesn't hurt and it will certainly protect you
519protect you from a lot of problems. 489from a lot of problems.
520</warn> 490</warn>
521 491
522<warn> 492<warn>
523Turning on ClamAV on access scanning in the <c>[global]</c> section will slow 493Turning on ClamAV on access scanning in the <c>[global]</c> section will slow
524down the performance of your Samba server dramatically. 494down the performance of your Samba server dramatically.
525</warn> 495</warn>
526 496
527<p> 497<p>
528Now create the directories required for the minimum configuration of 498Now create the directories required for the minimum configuration of Samba to
529Samba to share the installed printer throughout the network. 499share the installed printer throughout the network.
530</p> 500</p>
531 501
532<pre caption="Create the directories"> 502<pre caption="Create the directories">
533# <i>mkdir /etc/samba/printer</i> 503# <i>mkdir /etc/samba/printer</i>
534# <i>mkdir /var/spool/samba</i> 504# <i>mkdir /var/spool/samba</i>
535# <i>mkdir /home/samba/public</i> 505# <i>mkdir /home/samba/public</i>
536</pre> 506</pre>
537 507
538<p> 508<p>
539At least one Samba user is required in order to install the printer 509At least one Samba user is required in order to install the printer drivers and
540drivers and to allow users to connect to the printer. Users must 510to allow users to connect to the printer. Users must exist in the system's
541exist in the system's <path>/etc/passwd</path> file. 511<path>/etc/passwd</path> file.
542</p> 512</p>
543 513
544<pre caption="Creating the users"> 514<pre caption="Creating the users">
545# <i>smbpasswd -a root</i> 515# <i>smbpasswd -a root</i>
546 516
569<section> 539<section>
570<title>Configuring ClamAV</title> 540<title>Configuring ClamAV</title>
571<body> 541<body>
572 542
573<p> 543<p>
574The configuration file specified to be used in <path>smb.conf</path> is 544The configuration file specified to be used in <path>smb.conf</path> is
575<path>/etc/samba/vscan-clamav.conf</path>. While these options are set 545<path>/etc/samba/vscan-clamav.conf</path>. While these options are set to the
576to the defaults, the infected file action may need to be changed. 546defaults, the infected file action may need to be changed.
577</p> 547</p>
578 548
579<pre caption="/etc/samba/vscan-clamav.conf"> 549<pre caption="/etc/samba/vscan-clamav.conf">
580[samba-vscan] 550[samba-vscan]
581<comment>; run-time configuration for vscan-samba using 551<comment>; run-time configuration for vscan-samba using
638<comment>; port number the ScannerDaemon listens on</comment> 608<comment>; port number the ScannerDaemon listens on</comment>
639oav port = 8127 609oav port = 8127
640</pre> 610</pre>
641 611
642<p> 612<p>
643It is generally a good idea to start the virus scanner immediately. Add 613It is generally a good idea to start the virus scanner immediately. Add it to
644it to the <e>default</e> runlevel and then start the <c>clamd</c> service 614the <e>default</e> runlevel and then start the <c>clamd</c> service immediately.
645immediately. The service has two processes: freshclam keeps the virus definition 615The service has two processes: freshclam keeps the virus definition database up
646database up to date while clamd is the actual anti-virus daemon. First you may 616to date while clamd is the actual anti-virus daemon. First you may want to set
647want to set the paths of the logfiles so that it fits your needs. 617the paths of the logfiles so that it fits your needs.
648</p> 618</p>
649 619
650<pre caption="Checking the location of the logfiles"> 620<pre caption="Checking the location of the logfiles">
651# <i>vim /etc/clamd.conf</i> 621# <i>vim /etc/clamd.conf</i>
652<comment>(Check the line "LogFile /var/log/clamd.log")</comment> 622<comment>(Check the line "LogFile /var/log/clamd.log")</comment>
670<section> 640<section>
671<title>Configuring CUPS</title> 641<title>Configuring CUPS</title>
672<body> 642<body>
673 643
674<p> 644<p>
675This is a little more complicated. CUPS' main config file is 645This is a little more complicated. CUPS' main config file is
676<path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's 646<path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's
677<path>httpd.conf</path> file, so many you may find it familiar. Outlined 647<path>httpd.conf</path> file, so many you may find it familiar. Outlined in the
678in the example are the directives that need to be changed: 648example are the directives that need to be changed:
679</p> 649</p>
680 650
681<pre caption="/etc/cups/cupsd.conf"> 651<pre caption="/etc/cups/cupsd.conf">
682ServerName <i>PrintServer</i> <comment># your printserver name</comment> 652ServerName <i>PrintServer</i> <comment># your printserver name</comment>
683ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, e.g. you</comment> 653ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, e.g. you</comment>
754<p> 724<p>
755First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to 725First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to
756find and download the correct PPD file for your printer and CUPS. To do so, 726find and download the correct PPD file for your printer and CUPS. To do so,
757click the link Printer Listings to the left. Select your printers manufacturer 727click the link Printer Listings to the left. Select your printers manufacturer
758and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click "Show". On 728and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click "Show". On
759the page coming up click the "recommended driver" link after reading the 729the page coming up click the "recommended driver" link after reading the various
760various notes and information. Then fetch the PPD file from the next page, 730notes and information. Then fetch the PPD file from the next page, again after
761again after reading the notes and introductions there. You may have to select 731reading the notes and introductions there. You may have to select your printers
762your printers manufacturer and model again. Reading the <uri 732manufacturer and model again. Reading the <uri
763link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri> 733link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri> is
764is also very helpful when working with CUPS. 734also very helpful when working with CUPS.
765</p>
766
767<p> 735</p>
736
737<p>
768Now you have a PPD file for your printer to work with CUPS. Place it in 738Now you have a PPD file for your printer to work with CUPS. Place it in
769<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was 739<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was named
770named <path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer. 740<path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer.
771This can be done via the CUPS web interface or via command line. The web 741This can be done via the CUPS web interface or via command line. The web
772interface is found at <path>http://PrintServer:631</path> once CUPS is running. 742interface is found at <path>http://PrintServer:631</path> once CUPS is running.
773</p> 743</p>
774 744
775<pre caption="Install the printer via command line"> 745<pre caption="Install the printer via command line">
776# <i>lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd</i> 746# <i>lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd</i>
777# <i>/etc/init.d/cupsd restart</i> 747# <i>/etc/init.d/cupsd restart</i>
778</pre> 748</pre>
779 749
780<p> 750<p>
781Remember to adjust to what you have. Be sure to have the name 751Remember to adjust to what you have. Be sure to have the name (<c>-p</c>
782(<c>-p</c> argument) right (the name you set above during the Samba 752argument) right (the name you set above during the Samba configuration!) and to
783configuration!) and to put in the correct <c>usb:/dev/usb/blah</c>, 753put in the correct <c>usb:/dev/usb/blah</c>, <c>parallel:/dev/blah</c> or
784<c>parallel:/dev/blah</c> or whatever device you are using for your 754whatever device you are using for your printer.
785printer.
786</p>
787
788<p> 755</p>
756
757<p>
789You should now be able to access the printer from the web interface 758You should now be able to access the printer from the web interface and be able
790and be able to print a test page. 759to print a test page.
791</p> 760</p>
792 761
793</body> 762</body>
794</section> 763</section>
795<section> 764<section>
796<title>Installing the Windows printer drivers</title> 765<title>Installing the Windows printer drivers</title>
797<body> 766<body>
798 767
799<p> 768<p>
800Now that the printer should be working it is time to install the drivers 769Now that the printer should be working it is time to install the drivers for the
801for the Windows clients to work. Samba 2.2 introduced this functionality. 770Windows clients to work. Samba 2.2 introduced this functionality. Browsing to
802Browsing to the print server in the Network Neighbourhood, right-clicking 771the print server in the Network Neighbourhood, right-clicking on the
803on the printershare and selecting "connect" downloads the appropriate 772printershare and selecting "connect" downloads the appropriate drivers
804drivers automagically to the connecting client, avoiding the hassle of 773automagically to the connecting client, avoiding the hassle of manually
805manually installing printer drivers locally. 774installing printer drivers locally.
806</p> 775</p>
807 776
808<p> 777<p>
809There are two sets of printer drivers for this. First, the Adobe PS drivers 778There are two sets of printer drivers for this. First, the Adobe PS drivers
810which can be obtained from <uri 779which can be obtained from <uri
841<path>cupsui5.dll</path>. These are the actual driver files. 810<path>cupsui5.dll</path>. These are the actual driver files.
842</p> 811</p>
843 812
844<warn> 813<warn>
845The script <c>cups-samba.install</c> may not work for all *nixes (i.e. FreeBSD) 814The script <c>cups-samba.install</c> may not work for all *nixes (i.e. FreeBSD)
846because almost everything which is not part of the base system is 815because almost everything which is not part of the base system is installed
847installed somewhere under the prefix <path>/usr/local/</path>. This 816somewhere under the prefix <path>/usr/local/</path>. This seems not to be the
848seems not to be the case for most things you install under GNU/Linux. 817case for most things you install under GNU/Linux. However, if your CUPS
849However, if your CUPS installation is somewhere other than 818installation is somewhere other than <path>/usr/share/cups/</path> see the
850<path>/usr/share/cups/</path> see the example below. 819example below.
851</warn> 820</warn>
852 821
853<p> 822<p>
854Suppose your CUPS installation resides under 823Suppose your CUPS installation resides under
855<path>/usr/local/share/cups/</path>, and you want to install the drivers there. 824<path>/usr/local/share/cups/</path>, and you want to install the drivers there.
856Do the following: 825Do the following:
857</p> 826</p>
858 827
859<pre caption="Manually installing the drivers"> 828<pre caption="Manually installing the drivers">
860# <i>cd /path/you/extracted/the/CUPS-driver/tarball/into</i> 829# <i>cd /path/you/extracted/the/CUPS-driver/tarball/into</i>
889</p> 858</p>
890 859
891<ul> 860<ul>
892 <li> 861 <li>
893 The hostname given as a parameter for <c>-h</c> and <c>-H</c> 862 The hostname given as a parameter for <c>-h</c> and <c>-H</c>
894 (<c>PrintServer</c>) often does not resolve correctly and doesn't 863 (<c>PrintServer</c>) often does not resolve correctly and doesn't identify
895 identify the print server for CUPS/Samba interaction. If an error 864 the print server for CUPS/Samba interaction. If an error like: <b>Warning:
896 like: <b>Warning: No PPD file for printer "CUPS_PRINTER_NAME" - 865 No PPD file for printer "CUPS_PRINTER_NAME" - skipping!</b> occurs, the
897 skipping!</b> occurs, the first thing you should do is substitute 866 first thing you should do is substitute <c>PrintServer</c> with
898 <c>PrintServer</c> with <c>localhost</c> and try it again. 867 <c>localhost</c> and try it again.
899 </li> 868 </li>
900 <li> 869 <li>
901 The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message 870 The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message
902 is quite common, but can be triggered by many problems. It's unfortunately 871 is quite common, but can be triggered by many problems. It's unfortunately
903 not very helpful. One thing to try is to temporarily set <c>security = 872 not very helpful. One thing to try is to temporarily set <c>security =
904 user</c> in your <path>smb.conf</path>. After/if the installation completes 873 user</c> in your <path>smb.conf</path>. After/if the installation completes
905 successfully, you should set it back to share, or whatever it was set to 874 successfully, you should set it back to share, or whatever it was set to
906 before. 875 before.
907 </li> 876 </li>
908</ul> 877</ul>
909 878
910<p> 879<p>
911This should install the correct driver directory structure under 880This should install the correct driver directory structure under
912<path>/etc/samba/printer</path>. That would be 881<path>/etc/samba/printer</path>. That would be
913<path>/etc/samba/printer/W32X86/2/</path>. The files contained should 882<path>/etc/samba/printer/W32X86/2/</path>. The files contained should be the 3
914be the 3 driver files and the PPD file, renamed to YourPrinterName.ppd 883driver files and the PPD file, renamed to <path>YourPrinterName.ppd</path> (the
915(the name which you gave the printer when installing it (see above). 884name which you gave the printer when installing it (see above).
916</p>
917
918<p> 885</p>
886
887<p>
919Pending no errors or other complications, your drivers are now 888Pending no errors or other complications, your drivers are now installed.
920installed.
921</p> 889</p>
922 890
923</body> 891</body>
924</section> 892</section>
925<section> 893<section>
943<title>Testing our Samba configuration</title> 911<title>Testing our Samba configuration</title>
944<body> 912<body>
945 913
946<p> 914<p>
947We will want to test our configuration file to ensure that it is formatted 915We will want to test our configuration file to ensure that it is formatted
948properly and all of our options have at least the correct syntax. To do 916properly and all of our options have at least the correct syntax. To do this we
949this we run <c>testparm</c>. 917run <c>testparm</c>.
950</p> 918</p>
951 919
952<pre caption="Running the testparm"> 920<pre caption="Running the testparm">
953<comment>(By default, testparm checks /etc/samba/smb.conf)</comment> 921<comment>(By default, testparm checks /etc/samba/smb.conf)</comment>
954# <i>/usr/bin/testparm</i> 922# <i>/usr/bin/testparm</i>
984<section> 952<section>
985<title>Checking our services</title> 953<title>Checking our services</title>
986<body> 954<body>
987 955
988<p> 956<p>
989It would probably be prudent to check our logs at this time also. 957It would probably be prudent to check our logs at this time also. We will also
990We will also want to take a peak at our Samba shares using 958want to take a peak at our Samba shares using <c>smbclient</c>.
991<c>smbclient</c>.
992</p> 959</p>
993 960
994<pre caption="Checking the shares with smbclient"> 961<pre caption="Checking the shares with smbclient">
995# <i>smbclient -L localhost</i> 962# <i>smbclient -L localhost</i>
996Password: 963Password:
1006<section> 973<section>
1007<title>Printer configuration of *nix based clients</title> 974<title>Printer configuration of *nix based clients</title>
1008<body> 975<body>
1009 976
1010<p> 977<p>
1011Despite the variation or distribution, the only thing needed is CUPS. Do the 978Despite the variation or distribution, the only thing needed is CUPS. Do the
1012equivalent on any other UNIX/Linux/BSD client. 979equivalent on any other UNIX/Linux/BSD client.
1013</p> 980</p>
1014 981
1015<pre caption="Configuring a Gentoo system"> 982<pre caption="Configuring a Gentoo system">
1016# <i>emerge cups</i> 983# <i>emerge cups</i>
1047</pre> 1014</pre>
1048 1015
1049<p> 1016<p>
1050Just point your web browser to <c>http://printserver:631</c> on the client if 1017Just point your web browser to <c>http://printserver:631</c> on the client if
1051you want to manage your printers and their jobs with a nice web interface. 1018you want to manage your printers and their jobs with a nice web interface.
1052Replace <c>printserver</c> with the name of the <e>machine</e> that acts as 1019Replace <c>printserver</c> with the name of the <e>machine</e> that acts as your
1053your print server, not the name you gave to the cups print server if you used 1020print server, not the name you gave to the cups print server if you used
1054different names. 1021different names.
1055</p> 1022</p>
1056 1023
1057</body> 1024</body>
1058</section> 1025</section>
1061<body> 1028<body>
1062 1029
1063<p> 1030<p>
1064Now is time to configure our kernel to support smbfs. Since I'm assumming we've 1031Now is time to configure our kernel to support smbfs. Since I'm assumming we've
1065all compiled at least one kernel, we'll need to make sure we have all the right 1032all compiled at least one kernel, we'll need to make sure we have all the right
1066options selected in our kernel. For simplicity sake, make it a module for ease 1033options selected in our kernel. For simplicity's sake, make it a module for ease
1067of use. It is the author's opinion that kernel modules are a good thing and 1034of use. It is the author's opinion that kernel modules are a good thing and
1068should be used whenever possible. 1035should be used whenever possible.
1069</p> 1036</p>
1070 1037
1071<pre caption="Relevant kernel options" > 1038<pre caption="Relevant kernel options" >
1072CONFIG_SMB_FS=m 1039CONFIG_SMB_FS=m
1080<pre caption="Loading the kernel module"> 1047<pre caption="Loading the kernel module">
1081# <i>modprobe smbfs</i> 1048# <i>modprobe smbfs</i>
1082</pre> 1049</pre>
1083 1050
1084<p> 1051<p>
1085Once the modules is loaded, mounting a Windows or Samba share is 1052Once the module is loaded, mounting a Windows or Samba share is possible. Use
1086possible. Use <c>mount</c> to accomplish this, as detailed below: 1053<c>mount</c> to accomplish this, as detailed below:
1087</p> 1054</p>
1088 1055
1089<pre caption="Mounting a Windows/Samba share"> 1056<pre caption="Mounting a Windows/Samba share">
1090<comment>(The syntax for mounting a Windows/Samba share is: 1057<comment>(The syntax for mounting a Windows/Samba share is:
1091 mount -t smbfs [-o username=xxx,password=xxx] //server/share /mnt/point 1058 mount -t smbfs [-o username=xxx,password=xxx] //server/share /mnt/point
1096<comment>(If a password is needed)</comment> 1063<comment>(If a password is needed)</comment>
1097# <i>mount -t smbfs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i> 1064# <i>mount -t smbfs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i>
1098</pre> 1065</pre>
1099 1066
1100<p> 1067<p>
1101After you mount the share, you would access it as if it were a local 1068After you mount the share, you would access it as if it were a local drive.
1102drive.
1103</p> 1069</p>
1104 1070
1105</body> 1071</body>
1106</section> 1072</section>
1107<section> 1073<section>
1108<title>Printer Configuration for Windows NT/2000/XP clients</title> 1074<title>Printer Configuration for Windows NT/2000/XP clients</title>
1109<body> 1075<body>
1110 1076
1111<p> 1077<p>
1112That's just a bit of point-and-click. Browse to 1078That's just a bit of point-and-click. Browse to <path>\\PrintServer</path> and
1113<path>\\PrintServer</path> and right click on the printer 1079right click on the printer (HPDeskJet930C) and click connect. This will download
1114(HPDeskJet930C) and click connect. This will download the drivers to
1115the Windows client and now every application (such as Word or Acrobat) 1080the drivers to the Windows client and now every application (such as Word or
1116will offer HPDeskJet930C as an available printer to print to. :-) 1081Acrobat) will offer HPDeskJet930C as an available printer to print to. :-)
1117</p> 1082</p>
1118 1083
1119</body> 1084</body>
1120</section> 1085</section>
1121</chapter> 1086</chapter>
1125<section> 1090<section>
1126<title>A Fond Farewell</title> 1091<title>A Fond Farewell</title>
1127<body> 1092<body>
1128 1093
1129<p> 1094<p>
1130Well that should be it. You should now have a successful printing enviroment 1095That should be it. You should now have a successful printing enviroment that is
1131that is friendly to both Windows and *nix as well as a fully virus-free working 1096friendly to both Windows and *nix as well as a fully virus-free working share!
1132share!
1133</p> 1097</p>
1134 1098
1135</body> 1099</body>
1136</section> 1100</section>
1137</chapter> 1101</chapter>
1147troubleshooting your installation: 1111troubleshooting your installation:
1148</p> 1112</p>
1149 1113
1150<ul> 1114<ul>
1151 <li><uri link="http://www.cups.org/">CUPS Homepage</uri></li> 1115 <li><uri link="http://www.cups.org/">CUPS Homepage</uri></li>
1116 <li>
1152 <li><uri link="http://www.samba.org/">Samba Homepage</uri></li> 1117 <uri link="http://www.samba.org/">Samba Homepage</uri>, especially the <uri
1118 link="http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/CUPS-printing.html">chapter
1119 on Samba/CUPS configuration</uri>
1120 </li>
1153 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li> 1121 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li>
1154 <li> 1122 <li>
1155 <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt 1123 <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt
1156 Pfeifle's Samba Print HOWTO</uri> ( 1124 Pfeifle's Samba Print HOWTO</uri> ( This HOWTO really covers <e>ANYTHING</e>
1157 This HOWTO really covers <e>ANYTHING</e> and <e>EVERYTHING</e>
1158 I've written here, plus a LOT more concerning CUPS and Samba, and 1125 and <e>EVERYTHING</e> I've written here, plus a LOT more concerning CUPS and
1159 generally printing support on networks. A really interesting read, 1126 Samba, and generally printing support on networks. A really interesting
1160 with lots and lots of details) 1127 read, with lots and lots of details.)
1161 </li> 1128 </li>
1162 <li><uri link="http://www.freebsddiary.org/cups.php">FreeBSD Diary's CUPS Topic</uri></li> 1129 <li><uri link="http://www.freebsddiary.org/cups.php">FreeBSD Diary's CUPS Topic</uri></li>
1163</ul> 1130</ul>
1164 1131
1165</body> 1132</body>
1167<section> 1134<section>
1168<title>Troubleshooting</title> 1135<title>Troubleshooting</title>
1169<body> 1136<body>
1170 1137
1171<p> 1138<p>
1139See <uri
1172See <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37">this 1140link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37">this
1173page</uri> from Kurt Pfeifle's "Printing Support in Samba 3.0" 1141page</uri> from Kurt Pfeifle's "Printing Support in Samba 3.0" manual. Lots of
1174manual. Lots of useful tips there! Be sure to look this one up 1142useful tips there! Be sure to look this one up first, before posting questions
1175first, before posting questions and problems! Maybe the solution 1143and problems! Maybe the solution you're looking for is right there.
1176you're looking for is right there.
1177</p> 1144</p>
1178 1145
1179</body> 1146</body>
1180</section> 1147</section>
1181</chapter> 1148</chapter>

Legend:
Removed from v.1.26  
changed lines
  Added in v.1.29

  ViewVC Help
Powered by ViewVC 1.1.20