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

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

Parent Directory | Revision Log | View Patch Patch

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

 Legend:



Removed from v.1.9
 


changed lines


 
Added in v.1.34
 Legend:



Removed from v.1.9
 


changed lines


 
Added in v.1.34
-Removed from v.1.9
+Added in v.1.34

	ViewVC Help
Powered by ViewVC 1.1.20