/[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.18 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.18 2005/05/29 16:28:50 swift 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="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>
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 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.12</version> 23<version>1.17</version>
24<date>2005-03-26</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 an 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>
299 <li> 273 <li>
300 While Active Directory, ACL, and PDC functions are out of the intended 274 While Active Directory, ACL, and PDC functions are out of the intended
301 scope of this HOWTO, you may find these links as helpful to your cause: 275 scope of this HOWTO, you may find these links as helpful to your cause:
302 <ul> 276 <ul>
303 <li><uri>http://www.bluelightning.org/linux/samba_acl_howto/</uri></li> 277 <li><uri>http://www.bluelightning.org/linux/samba_acl_howto/</uri></li>
304 <li><uri>http://open-projects.linuxcare.com/research-papers/winbind-08162000.html</uri></li>
305 <li><uri>http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory</uri></li> 278 <li><uri>http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory</uri></li>
306 </ul> 279 </ul>
307 </li> 280 </li>
308</ul> 281</ul>
309 282
316<section> 289<section>
317<title>Emerging Samba</title> 290<title>Emerging Samba</title>
318<body> 291<body>
319 292
320<p> 293<p>
321First of all: be sure that all your hostnames resolve correctly. 294First of all: be sure that all your hostnames resolve correctly. Either have a
322Either have a working domain name system running on your network 295working domain name system running on your network or appropriate entries in
323or appropriate entries in your <path>/etc/hosts</path> file. 296your <path>/etc/hosts</path> file. <c>cupsaddsmb</c> often borks if hostnames
324<c>cupsaddsmb</c> often borks if hostnames don't point to the correct 297don't point to the correct machines.
325machines.
326</p>
327
328<p> 298</p>
299
300<p>
329Hopefully 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
330order 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:
331HOWTO is:
332</p> 303</p>
333 304
334<ul> 305<ul>
335 <li>oav</li> 306 <li>oav</li>
336 <li>cups</li> 307 <li>cups</li>
337 <li>readline</li> 308 <li>readline</li>
338 <li>pam</li> 309 <li>pam</li>
339</ul> 310</ul>
340 311
341<p> 312<p>
342To optimize performance, size and the time of the build, the 313To optimize performance, size and the time of the build, the USE flags are
343USE flags are specifically included or excluded. 314specifically included or excluded.
344</p> 315</p>
345 316
346<pre caption="Emerge Samba"> 317<pre caption="Emerge Samba">
347# <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>
348# <i>emerge net-fs/samba</i> 319# <i>emerge net-fs/samba</i>
349</pre> 320</pre>
350 321
351<note> 322<note>
352The 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,
353ppc, sparc, hppa, ia64 and alpha 324ppc, sparc, hppa, ia64 and alpha
354</note> 325</note>
355 326
356<p> 327<p>
357This will emerge Samba and CUPS (if CUPS is not already emerged). 328This will emerge Samba and CUPS (if CUPS is not already emerged).
362<section> 333<section>
363<title>Emerging ClamAV</title> 334<title>Emerging ClamAV</title>
364<body> 335<body>
365 336
366<p> 337<p>
367Because 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
368virus scanning, the actual virus scanner must be emerged. The scanner 339virus scanning, the actual virus scanner must be emerged. The scanner used in
369used in this HOWTO is ClamAV. 340this HOWTO is ClamAV.
370</p> 341</p>
371 342
372<pre caption="Emerge Clamav"> 343<pre caption="Emerge Clamav">
373# <i>emerge app-antivirus/clamav</i> 344# <i>emerge app-antivirus/clamav</i>
374</pre> 345</pre>
384</pre> 355</pre>
385 356
386</body> 357</body>
387</section> 358</section>
388<section> 359<section>
389<title>Emerging net-print/hpijs</title> 360<title>Emerging net-print/hplip</title>
390<body> 361<body>
391 362
392<p> 363<p>
393You only need to emerge this if you use an HP printer. 364You only need to emerge this if you use an HP printer.
394</p> 365</p>
395 366
396<pre caption="Emerge hpijs"> 367<pre caption="Emerge hplip">
397# <i>emerge net-print/hpijs</i> 368# <i>emerge net-print/hplip</i>
398</pre> 369</pre>
399 370
400</body> 371</body>
401</section> 372</section>
402</chapter> 373</chapter>
406<section> 377<section>
407<title>Configuring Samba</title> 378<title>Configuring Samba</title>
408<body> 379<body>
409 380
410<p> 381<p>
411The 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
412It is divided in sections indicated by [sectionname]. Comments are either 383divided in sections indicated by [sectionname]. Comments are either
413# 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
414suggestions for modifications. If more details are required, see the 385suggestions for modifications. If more details are required, see the man page
415man page for <path>smb.conf</path>, the installed 386for <path>smb.conf</path>, the installed <path>smb.conf.example</path>, the
416<path>smb.conf.example</path>, the Samba Web site or any of the 387Samba Web site or any of the numerous Samba books available.
417numerous Samba books available.
418</p> 388</p>
419 389
420<pre caption="A Sample /etc/samba/smb.conf"> 390<pre caption="A Sample /etc/samba/smb.conf">
421[global] 391[global]
422<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment> 392<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment>
507guest ok = yes 477guest ok = yes
508path = /home/samba/public 478path = /home/samba/public
509</pre> 479</pre>
510 480
511<warn> 481<warn>
512If 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
513printing 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>
514the <c>[global]</c> section. The guest account seems to cause 484section. The guest account seems to cause problems when running
515problems when running <c>cupsaddsmb</c> sometimes when trying to 485<c>cupsaddsmb</c> sometimes when trying to connect from Windows machines. See
516connect from Windows machines. See below, too, when we talk about 486below, too, when we talk about <c>cupsaddsmb</c> and the problems that can
517<c>cupsaddsmb</c> and the problems that can arise. Use a dedicated
518printer user, like <c>printeruser</c> or <c>printer</c> or 487arise. Use a dedicated printer user, like <c>printeruser</c> or <c>printer</c>
519<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
520protect you from a lot of problems. 489from a lot of problems.
521</warn> 490</warn>
522 491
523<warn> 492<warn>
524Turning 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
525down the performance of your Samba server dramatically. 494down the performance of your Samba server dramatically.
526</warn> 495</warn>
527 496
528<p> 497<p>
529Now create the directories required for the minimum configuration of 498Now create the directories required for the minimum configuration of Samba to
530Samba to share the installed printer throughout the network. 499share the installed printer throughout the network.
531</p> 500</p>
532 501
533<pre caption="Create the directories"> 502<pre caption="Create the directories">
534# <i>mkdir /etc/samba/printer</i> 503# <i>mkdir /etc/samba/printer</i>
535# <i>mkdir /var/spool/samba</i> 504# <i>mkdir /var/spool/samba</i>
536# <i>mkdir /home/samba/public</i> 505# <i>mkdir /home/samba/public</i>
537</pre> 506</pre>
538 507
539<p> 508<p>
540At 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
541drivers 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
542exist in the system's <path>/etc/passwd</path> file. 511<path>/etc/passwd</path> file.
543</p> 512</p>
544 513
545<pre caption="Creating the users"> 514<pre caption="Creating the users">
546# <i>smbpasswd -a root</i> 515# <i>smbpasswd -a root</i>
547 516
570<section> 539<section>
571<title>Configuring ClamAV</title> 540<title>Configuring ClamAV</title>
572<body> 541<body>
573 542
574<p> 543<p>
575The 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
576<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
577to the defaults, the infected file action may need to be changed. 546defaults, the infected file action may need to be changed.
578</p> 547</p>
579 548
580<pre caption="/etc/samba/vscan-clamav.conf"> 549<pre caption="/etc/samba/vscan-clamav.conf">
581[samba-vscan] 550[samba-vscan]
582<comment>; run-time configuration for vscan-samba using 551<comment>; run-time configuration for vscan-samba using
639<comment>; port number the ScannerDaemon listens on</comment> 608<comment>; port number the ScannerDaemon listens on</comment>
640oav port = 8127 609oav port = 8127
641</pre> 610</pre>
642 611
643<p> 612<p>
644It 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
645it 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.
646immediately. The service has two processes: freshclam keeps the virus definition 615The service has two processes: freshclam keeps the virus definition database up
647database 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
648want to set the paths of the logfiles so that it fits your needs. 617the paths of the logfiles so that it fits your needs.
649</p> 618</p>
650 619
651<pre caption="Checking the location of the logfiles"> 620<pre caption="Checking the location of the logfiles">
652# <i>vim /etc/clamd.conf</i> 621# <i>vim /etc/clamd.conf</i>
653<comment>(Check the line "LogFile /var/log/clamd.log")</comment> 622<comment>(Check the line "LogFile /var/log/clamd.log")</comment>
671<section> 640<section>
672<title>Configuring CUPS</title> 641<title>Configuring CUPS</title>
673<body> 642<body>
674 643
675<p> 644<p>
676This is a little more complicated. CUPS' main config file is 645This is a little more complicated. CUPS' main config file is
677<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
678<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
679in the example are the directives that need to be changed: 648example are the directives that need to be changed:
680</p> 649</p>
681 650
682<pre caption="/etc/cups/cupsd.conf"> 651<pre caption="/etc/cups/cupsd.conf">
683ServerName <i>PrintServer</i> <comment># your printserver name</comment> 652ServerName <i>PrintServer</i> <comment># your printserver name</comment>
684ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, eg you</comment> 653ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, e.g. you</comment>
685 654
686AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment> 655AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment>
687ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment> 656ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment>
688 657
689LogLevel debug <comment># only while isntalling and testing, should later be 658LogLevel debug <comment># only while isntalling and testing, should later be
690 # changed to 'info'</comment> 659 # changed to 'info'</comment>
691 660
692MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back, 661MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back,
693 # there seemed to be a bug in CUPS' controlling of the web interface, 662 # there seemed to be a bug in CUPS' controlling of the web interface,
694 # making CUPS think a denial of service attack was in progress when 663 # making CUPS think a denial of service attack was in progress when
695 # I tried to configure a printer with the web interface. weird.</comment> 664 # I tried to configure a printer with the web interface. weird.</comment>
698 667
699&lt;Location /&gt; 668&lt;Location /&gt;
700Order Deny,Allow 669Order Deny,Allow
701Deny From All 670Deny From All
702Allow From <i>192.168.1.*</i> <comment># the addresses of your internel network 671Allow From <i>192.168.1.*</i> <comment># the addresses of your internel network
703 # eg 192.168.1.* will allow connections from any host on 672 # e.g. 192.168.1.* will allow connections from any host on
704 # the 192.168.1.0 network. change to whatever suits you</comment> 673 # the 192.168.1.0 network. change to whatever suits you</comment>
705&lt;/Location&gt; 674&lt;/Location&gt;
706 675
707&lt;Location /admin&gt; 676&lt;Location /admin&gt;
708AuthType Basic 677AuthType Basic
754 723
755<p> 724<p>
756First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to 725First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to
757find 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,
758click the link Printer Listings to the left. Select your printers manufacturer 727click the link Printer Listings to the left. Select your printers manufacturer
759and the model in the pulldown menu, eg HP and DeskJet 930C. Click "Show". On 728and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click "Show". On
760the page coming up click the "recommended driver" link after reading the 729the page coming up click the "recommended driver" link after reading the various
761various 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
762again 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
763your printers manufacturer and model again. Reading the <uri 732manufacturer and model again. Reading the <uri
764link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri> 733link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri> is
765is also very helpful when working with CUPS. 734also very helpful when working with CUPS.
766</p>
767
768<p> 735</p>
736
737<p>
769Now 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
770<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
771named <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.
772This 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
773interface 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.
774</p> 743</p>
775 744
776<pre caption="Install the printer via command line"> 745<pre caption="Install the printer via command line">
777# <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>
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>
807
808<p> 775</p>
776
777<p>
809There are two sets of printer drivers for this. First, the Adobe PS 778There are two sets of printer drivers for this. First, the Adobe PS drivers
810drivers which can be obtained from <uri 779which can be obtained from <uri
811link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> 780link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript
812(PostScript printer drivers). Second, there are the CUPS PS drivers, 781printer drivers). Second, there are the CUPS PS drivers, to be obtained <uri
813to be obtained from <uri link="http://www.cups.org/software.php">the 782link="http://dev.gentoo.org/~nightmorph/misc/cups-samba-5.0rc2.tar.gz">here</uri>.
814CUPS homepage</uri> and selecting "CUPS Driver for Windows" from the 783There doesn't seem to be a difference between the functionality of the two, but
815pull down menu. There doesn't seem to be a difference between the 784the Adobe PS drivers need to be extracted on a Windows System since it's a
816functionality of the two, but the Adobe PS drivers need to be extracted 785Windows binary. Also the whole procedure of finding and copying the correct
817on a Windows System since it's a Windows binary. Also the whole procedure 786files is a bit more hassle. The CUPS drivers seem to support some options the
818of finding and copying the correct files is a bit more hassle. The CUPS 787Adobe drivers don't.
819drivers seem to support some options the Adobe drivers don't.
820</p> 788</p>
789<!--
790used to be available at www.cups.org/articles.php?L142+p4, but only 6.0 is
791available. at some point, we should update this for 6.0.
792-->
821 793
822<p> 794<p>
823This HOWTO uses the CUPS drivers for Windows. The downloaded file is 795This HOWTO uses the CUPS drivers for Windows. The downloaded file is
824called <path>cups-samba-5.0rc2.tar.gz</path>. Extract the files 796called <path>cups-samba-5.0rc2.tar.gz</path>. Extract the files
825contained into a directory. 797contained into a directory.
837<path>cups5.hlp</path>, <path>cupsdrvr5.dll</path> and 809<path>cups5.hlp</path>, <path>cupsdrvr5.dll</path> and
838<path>cupsui5.dll</path>. These are the actual driver files. 810<path>cupsui5.dll</path>. These are the actual driver files.
839</p> 811</p>
840 812
841<warn> 813<warn>
842The script <c>cups-samba.install</c> may not work for all *nixes (ie FreeBSD) 814The script <c>cups-samba.install</c> may not work for all *nixes (i.e. FreeBSD)
843because almost everything which is not part of the base system is 815because almost everything which is not part of the base system is installed
844installed somewhere under the prefix <path>/usr/local/</path>. This 816somewhere under the prefix <path>/usr/local/</path>. This seems not to be the
845seems 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
846However, if your CUPS installation is somewhere other than 818installation is somewhere other than <path>/usr/share/cups/</path> see the
847<path>/usr/share/cups/</path> see the example below. 819example below.
848</warn> 820</warn>
849 821
850<p> 822<p>
851Suppose your CUPS installation resides under 823Suppose your CUPS installation resides under
852<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.
853Do the following: 825Do the following:
854</p> 826</p>
855 827
856<pre caption="Manually installing the drivers"> 828<pre caption="Manually installing the drivers">
857# <i>cd /path/you/extracted/the/CUPS-driver/tarball/into</i> 829# <i>cd /path/you/extracted/the/CUPS-driver/tarball/into</i>
858# <i>tar -xf cups-samba.ss</i> 830# <i>tar -xf cups-samba.ss</i>
859<comment>(This extracts the files to usr/share/cups/drivers under the CURRENT WORKING DIRECTORY)</comment> 831<comment>(This extracts the files to usr/share/cups/drivers under the CURRENT WORKING DIRECTORY)</comment>
860# <i>cd usr/share/cups/drivers</i> 832# <i>cd usr/share/cups/drivers</i>
861<comment>(no leading / !)</comment> 833<comment>(no leading / !)</comment>
862# <i>cp cups* /usr/local/share/cups/drivers</i> 834# <i>cp cups* /usr/local/share/cups/drivers</i>
835# <i>/etc/init.d/cupsd restart</i>
863</pre> 836</pre>
864 837
865<p> 838<p>
866Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS 839Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS distribution.
867distribution. It's man page is an interesting read. 840Its man page is an interesting read.
868</p> 841</p>
869 842
870<pre caption="Run cupsaddsmb"> 843<pre caption="Run cupsaddsmb">
871# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C</i> 844# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C</i>
872<comment>(Instead of HPDeskJet930C you could also specify "-a", which will 845<comment>(Instead of HPDeskJet930C you could also specify "-a", which will
873"export all known printers".)</comment> 846"export all known printers".)</comment>
874# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -a</i> 847# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -a</i>
875</pre> 848</pre>
876 849
877<warn> 850<warn>
878The execution of this command often causes the most trouble. 851The execution of this command often causes the most trouble. Read through the
879Reading through the <uri
880link="http://forums.gentoo.org/viewtopic.php?t=110931">posts in this 852<uri link="http://forums.gentoo.org/viewtopic.php?t=110931">posts in this
881thread</uri>. 853thread</uri> for some troubleshooting tips.
882</warn> 854</warn>
883 855
884<p> 856<p>
885Here are common errors that may happen: 857Here are common errors that may happen:
886</p> 858</p>
887 859
888<ul> 860<ul>
889 <li> 861 <li>
890 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>
891 (<c>PrintServer</c>) often does not resolve correctly and doesn't 863 (<c>PrintServer</c>) often does not resolve correctly and doesn't identify
892 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:
893 like: <b>Warning: No PPD file for printer "CUPS_PRINTER_NAME" - 865 No PPD file for printer "CUPS_PRINTER_NAME" - skipping!</b> occurs, the
894 skipping!</b> occurs, the first thing you should do is substitute 866 first thing you should do is substitute <c>PrintServer</c> with
895 <c>PrintServer</c> with <c>localhost</c> and try it again. 867 <c>localhost</c> and try it again.
896 </li> 868 </li>
897 <li> 869 <li>
898 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
899 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
900 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 =
901 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
902 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
903 before. 875 before.
904 </li> 876 </li>
905</ul> 877</ul>
906 878
907<p> 879<p>
908This should install the correct driver directory structure under 880This should install the correct driver directory structure under
909<path>/etc/samba/printer</path>. That would be 881<path>/etc/samba/printer</path>. That would be
910<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
911be 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
912(the name which you gave the printer when installing it (see above). 884name which you gave the printer when installing it (see above).
913</p>
914
915<p> 885</p>
886
887<p>
916Pending no errors or other complications, your drivers are now 888Pending no errors or other complications, your drivers are now installed.
917installed.
918</p> 889</p>
919 890
920</body> 891</body>
921</section> 892</section>
922<section> 893<section>
940<title>Testing our Samba configuration</title> 911<title>Testing our Samba configuration</title>
941<body> 912<body>
942 913
943<p> 914<p>
944We 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
945properly 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
946this we run <c>testparm</c>. 917run <c>testparm</c>.
947</p> 918</p>
948 919
949<pre caption="Running the testparm"> 920<pre caption="Running the testparm">
950<comment>(By default, testparm checks /etc/samba/smb.conf)</comment> 921<comment>(By default, testparm checks /etc/samba/smb.conf)</comment>
951# <i>/usr/bin/testparm</i> 922# <i>/usr/bin/testparm</i>
981<section> 952<section>
982<title>Checking our services</title> 953<title>Checking our services</title>
983<body> 954<body>
984 955
985<p> 956<p>
986It 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
987We 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>.
988<c>smbclient</c>.
989</p> 959</p>
990 960
991<pre caption="Checking the shares with smbclient"> 961<pre caption="Checking the shares with smbclient">
992# <i>smbclient -L localhost</i> 962# <i>smbclient -L localhost</i>
993Password: 963Password:
1003<section> 973<section>
1004<title>Printer configuration of *nix based clients</title> 974<title>Printer configuration of *nix based clients</title>
1005<body> 975<body>
1006 976
1007<p> 977<p>
1008Despite 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
1009equivalent on any other UNIX/Linux/BSD client. 979equivalent on any other UNIX/Linux/BSD client.
1010</p> 980</p>
1011 981
1012<pre caption="Configuring a Gentoo system"> 982<pre caption="Configuring a Gentoo system">
1013# <i>emerge cups</i> 983# <i>emerge cups</i>
1044</pre> 1014</pre>
1045 1015
1046<p> 1016<p>
1047Just 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
1048you 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.
1049Replace <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
1050your 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
1051different names. 1021different names.
1052</p> 1022</p>
1053 1023
1054</body> 1024</body>
1055</section> 1025</section>
1058<body> 1028<body>
1059 1029
1060<p> 1030<p>
1061Now 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
1062all 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
1063options 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
1064of 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
1065should be used whenever possible. 1035should be used whenever possible.
1066</p> 1036</p>
1067 1037
1068<pre caption="Relevant kernel options" > 1038<pre caption="Relevant kernel options" >
1069CONFIG_SMB_FS=m 1039CONFIG_SMB_FS=m
1077<pre caption="Loading the kernel module"> 1047<pre caption="Loading the kernel module">
1078# <i>modprobe smbfs</i> 1048# <i>modprobe smbfs</i>
1079</pre> 1049</pre>
1080 1050
1081<p> 1051<p>
1082Once 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
1083possible. Use <c>mount</c> to accomplish this, as detailed below: 1053<c>mount</c> to accomplish this, as detailed below:
1084</p> 1054</p>
1085 1055
1086<pre caption="Mounting a Windows/Samba share"> 1056<pre caption="Mounting a Windows/Samba share">
1087<comment>(The syntax for mounting a Windows/Samba share is: 1057<comment>(The syntax for mounting a Windows/Samba share is:
1088 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
1093<comment>(If a password is needed)</comment> 1063<comment>(If a password is needed)</comment>
1094# <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>
1095</pre> 1065</pre>
1096 1066
1097<p> 1067<p>
1098After 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.
1099drive.
1100</p> 1069</p>
1101 1070
1102</body> 1071</body>
1103</section> 1072</section>
1104<section> 1073<section>
1105<title>Printer Configuration for Windows NT/2000/XP clients</title> 1074<title>Printer Configuration for Windows NT/2000/XP clients</title>
1106<body> 1075<body>
1107 1076
1108<p> 1077<p>
1109That'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
1110<path>\\PrintServer</path> and right click on the printer 1079right click on the printer (HPDeskJet930C) and click connect. This will download
1111(HPDeskJet930C) and click connect. This will download the drivers to
1112the 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
1113will offer HPDeskJet930C as an available printer to print to. :-) 1081Acrobat) will offer HPDeskJet930C as an available printer to print to. :-)
1114</p> 1082</p>
1115 1083
1116</body> 1084</body>
1117</section> 1085</section>
1118</chapter> 1086</chapter>
1122<section> 1090<section>
1123<title>A Fond Farewell</title> 1091<title>A Fond Farewell</title>
1124<body> 1092<body>
1125 1093
1126<p> 1094<p>
1127Well 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
1128that 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!
1129share!
1130</p> 1097</p>
1131 1098
1132</body> 1099</body>
1133</section> 1100</section>
1134</chapter> 1101</chapter>
1144troubleshooting your installation: 1111troubleshooting your installation:
1145</p> 1112</p>
1146 1113
1147<ul> 1114<ul>
1148 <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>
1149 <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>
1150 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li> 1121 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li>
1151 <li> 1122 <li>
1152 <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt 1123 <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt
1153 Pfeifle's Samba Print HOWTO</uri> ( 1124 Pfeifle's Samba Print HOWTO</uri> ( This HOWTO really covers <e>ANYTHING</e>
1154 This HOWTO really covers <e>ANYTHING</e> and <e>EVERYTHING</e>
1155 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
1156 generally printing support on networks. A really interesting read, 1126 Samba, and generally printing support on networks. A really interesting
1157 with lots and lots of details) 1127 read, with lots and lots of details.)
1158 </li> 1128 </li>
1159 <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>
1160</ul> 1130</ul>
1161 1131
1162</body> 1132</body>
1164<section> 1134<section>
1165<title>Troubleshooting</title> 1135<title>Troubleshooting</title>
1166<body> 1136<body>
1167 1137
1168<p> 1138<p>
1139See <uri
1169See <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
1170page</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
1171manual. 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
1172first, before posting questions and problems! Maybe the solution 1143and problems! Maybe the solution you're looking for is right there.
1173you're looking for is right there.
1174</p> 1144</p>
1175 1145
1176</body> 1146</body>
1177</section> 1147</section>
1178</chapter> 1148</chapter>

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

  ViewVC Help
Powered by ViewVC 1.1.20