-.TH achfile 1 26\ Feb\ 1998 "Netatalk 2.0-beta1"
+.TH achfile 1 26\ Feb\ 1998 "Netatalk 2.0-beta2"
.SH NAME
achfile \- change type and/or creator of Apple Macintosh files (netatalk format)
.SH SYNOPSIS
-.TH acleandir 1 26\ Feb\ 1998 "Netatalk 2.0-beta1"
+.TH acleandir 1 26\ Feb\ 1998 "Netatalk 2.0-beta2"
.SH NAME
acleandir \- clean up a directory containing netatalk Apple Macintosh files
.SH SYNOPSIS
-.TH aecho 1 17\ Dec\ 1991 "Netatalk 2.0-beta1"
+.TH aecho 1 17\ Dec\ 1991 "Netatalk 2.0-beta2"
.SH NAME
aecho \- send AppleTalk Echo Protocol packets to network hosts
.SH SYNOPSIS
-.TH afile 1 26\ Feb\ 1998 "Netatalk 2.0-beta1"
+.TH afile 1 26\ Feb\ 1998 "Netatalk 2.0-beta2"
.SH NAME
afile \- display type and creator of Apple Macintosh files (netatalk format)
.SH SYNOPSIS
9 bad magic in AppleDouble
.SH SEE\ ALSO
\fBachfile\fR(1),
-\fBafpd\fR(1)
+\fBafpd\fR(8)
-.TH afppasswd 1 03\ Aug\ 2000 "Netatalk 2.0-beta1"
+.TH afppasswd 1 03\ Aug\ 2000 "Netatalk 2.0-beta2"
.SH NAME
afppasswd \- netatalk password maintenance utility
.SH SYNOPSIS
-.TH apple_cp 1 15\ Oct\ 2001 "Netatalk 2.0-beta1"
+.TH apple_cp 1 15\ Oct\ 2001 "Netatalk 2.0-beta2"
.SH NAME
apple_cp \- Do an apple copy, copying the resource fork as well
.SH SYNOPSIS
-.TH apple_mv 1 16\ Oct\ 2001 "Netatalk 2.0-beta1"
+.TH apple_mv 1 16\ Oct\ 2001 "Netatalk 2.0-beta2"
.SH NAME
apple_mv \- Do an apple move, moving the resource fork as well
.SH SYNOPSIS
-.TH getzones 1 17\ Dec\ 1991 "Netatalk 2.0-beta1"
+.TH getzones 1 17\ Dec\ 1991 "Netatalk 2.0-beta2"
.SH NAME
getzones \- list AppleTalk zone names
.SH SYNOPSIS
-.TH megatron 1 8\ Jan\ 1992 "Netatalk 2.0-beta1"
+.TH megatron 1 8\ Jan\ 1992 "Netatalk 2.0-beta2"
.SH NAME
megatron, unhex, unbin, unsingle, hqx2bin, single2bin, macbinary \- Macintosh file format transformer
.SH SYNOPSIS
-.TH nbp 1 17\ Dec\ 1991 "Netatalk 2.0-beta1"
+.TH nbp 1 24\ June\ 2004 "Netatalk 2.0-beta2"
.SH NAME
nbplkup, nbprgstr, nbpunrgstr \- access NBP database
.SH SYNOPSIS
-\fBnbplkup\fR [ \-r \fBnresp\fR ] [\fBnbpname\fR] \fBnbprgstr\fR [ \-p \fBport\fR ] \fBnbpnamenbpunrgstrnbpname\fR
+\fBnbplkup \fR [\-r \fBmaxresponses\fR] [\-A \fBaddress\fR] [\-m \fBmaccodepage\fR] \fBnbpname\fR
+.PP
+\fBnbprgstr \fR [\-A \fBaddress\fR] [\-p \fBport\fR] [\-m \fBmaccodepage\fR] \fBnbpname\fR
+.PP
+\fBnbpunrgstr\fR [\-A \fBaddress\fR] [\-m \fBmaccodepage\fR] \fBnbpname\fR
.SH DESCRIPTION
-\fInbprgstr\fR registers \fInbpname\fR with \fBatalkd\fR(8),
-at the given \fIport\fR. \fInbpunrgstr\fR
-informs \fIatalkd\fR that \fInbpname\fR
-is no longer to be advertised.
+nbprgstr registers \fInbpname\fR
+with \fBatalkd\fR(8),
+at the given \fIport\fR. nbpunrgstr
+informs \fIatalkd\fR that
+\fInbpname\fR is no longer to be advertised.
.PP
-nbplkup displays up to \fInresp\fR
-(default 1000) entities registered on the AppleTalk internet. \fInbpname\fR is parsed by \fBnbp_name\fR(3).
+nbplkup displays up to
+\fImaxresponses\fR (default 1000) entities registered
+on the AppleTalk internet. \fInbpname\fR
+is parsed by \fBnbp_name\fR(3).
An `\fI=\fR' for the \fIobject\fR
or \fItype\fR matches anything, and an `\fI*\fR' for \fIzone\fR means
the local zone. The default values are taken from the \fINBPLKUP\fR
environment variable, parsed as an \fInbpname\fR.
+.SH ENVIRONMENT\ VARIABLES
+.TP
+NBPLKUP
+default nbpname for nbplkup
+.TP
+ATALK_MAC_CHARSET
+the codepage used by the clients on the Appletalk network
+.TP
+ATALK_UNIX_CHARSET
+the codepage used to display extended characters on this
+shell.
.SH EXAMPLE
Find all devices of type \fILaserWriter\fR
in the local zone.
-.TH netatalk\-config 1 09\ June\ 2001 "Netatalk 2.0-beta1"The\ Netatalk\ Project
+.TH netatalk\-config 1 09\ June\ 2001 "Netatalk 2.0-beta2"The\ Netatalk\ Project
.SH NAME
netatalk\-config \- script to get information about the installed version of netatalk
.SH SYNOPSIS
-.TH pap 1 6\ May\ 2002 "Netatalk 2.0-beta1"
+.TH pap 1 6\ May\ 2002 "Netatalk 2.0-beta2"
.SH NAME
pap, papstatus \- client interface to remote printers using Printer Access Protocol
.SH SYNOPSIS
-.TH psorder 1 17\ Dec\ 1991 "Netatalk 2.0-beta1"
+.TH psorder 1 17\ Dec\ 1991 "Netatalk 2.0-beta2"
.SH NAME
psorder \- PostScript pageorder filter
.SH SYNOPSIS
-.TH timeout 1 19\ Jul\ 2001 "Netatalk 2.0-beta1"The\ Netatalk\ Project
+.TH timeout 1 19\ Jul\ 2001 "Netatalk 2.0-beta2"The\ Netatalk\ Project
.SH NAME
timeout \- Send a signal to a program after a certain time
.SH SYNTAX
-.TH atalk_aton 3 12\ Jan\ 1994 "Netatalk 2.0-beta1"
+.TH atalk_aton 3 12\ Jan\ 1994 "Netatalk 2.0-beta2"
.SH NAME
atalk_aton \- AppleTalk address parsing
.SH SYNOPSIS
-.TH nbp_name 3 12\ Jan\ 1994 "Netatalk 2.0-beta1"
+.TH nbp_name 3 12\ Jan\ 1994 "Netatalk 2.0-beta2"
.SH NAME
nbp_name \- NBP name parsing
.SH SYNOPSIS
-.TH atalk 4 17\ Dec\ 1991 "Netatalk 2.0-beta1"
+.TH atalk 4 17\ Dec\ 1991 "Netatalk 2.0-beta2"
.SH NAME
atalk \- AppleTalk protocol family
.SH SYNOPSIS
-.TH AppleVolumes.default 5 05\ January\ 2004 "Netatalk 2.0-beta1"
+.TH AppleVolumes.default 5 05\ January\ 2004 "Netatalk 2.0-beta2"
.SH NAME
AppleVolumes.default \- Configuration file used by afpd(8) to determine the shares made available through Appletalk
.SH DESCRIPTION
.PP
The possible options and their meanings are:
.TP
-adouble:\fI[v1/v2]\fR
+adouble:\fI[v1|v2|osx]\fR
specify the format of the metadata files, which are used for
saving Mac resource fork as well. Earlier versions used AppleDouble
-V1, the new default format is V2.
+V1, the new default format is V2. Starting with Netatalk 2.0, the
+scheme MacOS X uses currently (10.3.x), is also supported
+.RS
+\fBNote\fR
+
+Using \fBadouble:osx\fR is \fBnot\fR
+recommended for production use. Its only aim is to temporarely share eg.
+FAT32 formatted FireWire harddrives written on a Macintosh with afpd. Apple's
+metadata scheme lacks several essential features, so using it on the server's
+side will break both CNIDs and MacOS 9 compatibility
+.RE
.TP
allow:\fI[users/groups]\fR
The allow option allows the users and groups that access a
-.TH afpd.conf 5 05\ Jan\ 2004 "Netatalk 2.0-beta1"
+.TH afpd.conf 5 05\ Jan\ 2004 "Netatalk 2.0-beta2"
.SH NAME
afpd.conf \- Configuration file used by afpd(8) to determine the setup of its file sharing services
.SH DESCRIPTION
Make both available (default)
.SH TRANSPORT\ OPTIONS
.TP
+\-advertise_ssh
+Allows Mac OS X clients (10.3.3 or above) to automagically
+establish a tunneled AFP connection through SSH. If this option is set,
+the server's answers to client's FPGetSrvrInfo requests contain an
+additional entry. It depends on both client's settings and a correctly
+configured and running \fBsshd\fR(8)
+on the server to let things work.
+.RS
+\fBNote\fR
+
+Setting this option is not recommended since globally encrypting
+AFP connections via SSH will increase the server's load significantly.
+On the other hand, Apple's client side implementation of this feature
+in MacOS X versions prior to 10.3.4 contained a security flaw
+.RE
+.TP
\-ddpaddr \fI[ddp address]\fR
Specifies the DDP address of the server. The default is to
auto\-assign an address (0.0). This is only useful if you are running
\fBafpd.conf setup for Kerberos V auth\fR
.PP
.nf
-\- \-transall \-uamlist uams_clrtxt.so,uams_dhx.so,uams_guest.so,uams_gss.so \-k5service afpserver \-k5keytab /path/to/afpserver.keytab \-k5realm YOUR.REALM \-fqdn your.fqdn.namel:548
+\- \-transall \-uamlist uams_clrtxt.so,uams_dhx.so,uams_guest.so,uams_gss.so \\
+\-k5service afpserver \-k5keytab /path/to/afpserver.keytab \\
+\-k5realm YOUR.REALM \-fqdn your.fqdn.namel:548
.fi
.PP
\fBafpd.conf letting afpd appear as three servers on the net\fR
-.TH atalkd.conf 5 22\ September\ 2000 "Netatalk 2.0-beta1"
+.TH atalkd.conf 5 22\ September\ 2000 "Netatalk 2.0-beta2"
.SH NAME
atalkd.conf \- Configuration file used by atalkd(8) to determine the interfaces used by the master Netatalk daemon
.SH DESCRIPTION
-.TH netatalk.conf 5 28\ September\ 2000 "Netatalk 2.0-beta1"
+.TH netatalk.conf 5 24\ June\ 2004 "Netatalk 2.0-beta2"
.SH NAME
netatalk.conf \- Configuration file used by netatalk(8) to determine its general configuration
.SH DESCRIPTION
\fIExample:\fR \fIAFPD_UAMLIST\fR=\fI"\-U uams_guest.so,uams_randnum.so"\fR
.TP
\fICNID_METAD_RUN\fR
-Enables the cnid_metad daemon if set to "yes". This should
-be enabled if you are going to use the dbd CNID backend.
+Enables the cnid_metad daemon if set to "yes". This
+should be enabled if you are going to use the dbd CNID backend.
.TP
\fIATALK_BGROUND\fR
"yes" will set netatalk to initialize in the
\fIPAPD_RUN\fR
Enables the papd daemon if set to "yes". This should
be enabled if you are planning on using netatalk as a print server.
+.TP
+\fIATALK_MAC_CHARSET\fR
+Set the Mac client codepage, used by atalkd and papd to
+convert extended characters from the Unix to the Mac codepage.
+.TP
+\fIATALK_UNIX_CHARSET\fR
+Set the Unix codepage, used by atalkd and papd to convert
+extended characters from the Unix to the Mac codepage. Has to match
+the codepage of the configuration files.
.SH SEE\ ALSO
\fBatalkd\fR(8),
\fBatalkd.conf\fR(5)
-.TH papd.conf 5 26\ September\ 2000 "Netatalk 2.0-beta1"
+.TH papd.conf 5 13\ June\ 2004 "Netatalk 2.0-beta2"
.SH NAME
papd.conf \- Configuration file used by papd(8) to determine the configuration of printers used by the Netatalk printing daemon
.SH DESCRIPTION
.PP
\fIprintername:[options]\fR
.PP
-The simplest case is to have either no papd.conf, or to have one
-that has no active lines. In this case, atalkd should auto\-discover the
-local printers on the machine. Please note that you can split lines by
-using \fI\\\\fR.\fR
+On systems running a System V printing system the simplest case
+is to have either no papd.conf, or to have one that has no active lines.
+In this case, atalkd should auto\-discover the local printers on the machine.
+Please note that you can split lines by using \fI\\\\fR.\fR
.PP
printername may be just a name (\fIPrinter 1\fR),
or it may be a full name in nbp_name format (\fIPrinter
you should explicitly define the zone for each printer. Otherwise, the Mac
Chooser not show all the printers.
.PP
+Systems using a BSD printing system should make use of a pipe to
+the printing command in question within the \fIpr\fR
+option (eg. \fIpr=|/usr/bin/lpr \-J%J \-u%U\fR). Note:
+When printing using a pipe, papd recognizes several wildcards: %F will be
+replaced by the name present in the "%%For:" comment in the PostScript stream,
+same with %J for the "%%Title:" comment. %U will be substituted with the login
+name (the latter applies only when authenticated printing is in effect)
+.PP
+When CUPS support is compiled in, then \fIcupsautoadd
+\fRas the first entry in papd.conf will automagically share all
+CUPS printers by papd utilizing the PPDs assigned in CUPS (customizable \-\- see
+below). This can be overwritten for individal printers by subsequently adding
+individual entries using the CUPS queue name as \fIpr
+\fRentry. Note: CUPS support is mutually exclusive with System V
+support described above
+.PP
The possible options are colon delimited (\fI:\fR),
and lines must be terminated with colons. The possible options and flags
are:
The \fIam\fR option allows specific
UAMs to be specified for a particular printer. It has no effect if
the \fIau\fR flag is not present or if papd
-authentication was not built into netatalk.
+authentication was not built into netatalk. Note: possible values are
+\fIuams_guest.so\fR and \fI
+uams_clrtxt.so\fR only. The first method requires a valid
+username, but no password. The second requires both a valid username
+and the correct password
.TP
\fIau\fR
If present, this flag enables authentication for the printer.
Please note that papd authentication must be built into netatalk for
this to take effect.
.TP
+\fIco=(CUPS options)\fR
+The \fIco\fR option allows options to
+be passed through to CUPS (eg. \fIco="protocol=TBCP"
+\fRor \fIco="raw"\fR).
+.TP
+\fIcupsautoadd[:type][@zone]\fR
+If used as the first entry in papd.conf this will share all CUPS
+printers via papd. type/zone settings as well as other parameters
+assigned to this special printer share will apply to all CUPS printers.
+Unless the \fIpd\fR option is set, the CUPS PPDs
+will be used. To overwrite these global settings for individual printers
+simply add them subsequently to papd.conf and assign different settings
+.TP
+\fIfo\fR
+If present, this flag enables a hack to translate line endings
+originating from pre Mac OS X LaserWriter drivers to let \fIfoomatic\-rip\fR recognize foomatic PPD options set in
+the printer dialog. Attention: Use with caution since this might corrupt
+binary print jobs!
+.TP
\fIop=(operator)\fR
This specifies the operator name, for lpd spooling.
.TP
Specifies a particular PPD (printer description file) to
associate with the selected printer.
.TP
-\fIpr=(lpd printer name)\fR
-Sets the \fIlpd\fR printer that this
-is spooled to.
+\fIpr=(lpd/CUPS printer name or pipe command)\fR
+Sets the \fIlpd\fR or \fICUPS\fR printer that this is spooled to.
+.SH EXAMPLES
+Unless CUPS support has been compiled in (which is default from
+Netatalk 2.0 on) one simply defines the lpd queue in question by
+setting the \fBpr\fR parameter to the queue name, in the
+following example "ps". If no \fBpr\fR parameter is set,
+the default printer will be used.
+.PP
+\fBpapd.conf System V printing system examples\fR
+.PP
+The first spooler is known by the AppleTalk name Mac Printer
+Spooler, and uses a PPD file located in
+\fB/usr/share/lib/ppd\fR. In addition, the user mcs
+will be the owner of all jobs that are spooled. The second spooler
+is known as HP Printer and all options are the default.
+
+.nf
+Mac Printer Spooler:\\
+ :pr=ps:\\
+ :pd=/usr/share/lib/ppd/HPLJ_4M.PPD:\\
+ :op=mcs:
+
+HP Printer:\\
+ :
+.fi
+.PP
+An alternative to the technique outlined above is to direct
+papd's output via a pipe into another program. Using this mechanism
+almost all printing systems can be driven. Netatalk supplies three
+"wildcards" that get substituted with values of the already printed
+job: \fB%F\fR, \fB%U\fR and \fB%J\fR. Using these wildcards, one can pass those parameters directly to
+programs or implement small wrapper scripts to call the printing
+system in question.
+.PP
+\fBpapd.conf examples using pipes\fR
+.PP
+The first spooler is known as HP 8100. It pipes the print job
+to /usr/bin/lpr for printing using the value of
+the \fI%%Title: \fR comment as job name. PSSP
+authenticated printing is enabled, as is CAP\-style authenticated
+printing. Both methods support guest and cleartext authentication as
+specified by the '\fBam\fR' option. The PPD used is
+\fB/etc/atalk/ppds/hp8100.ppd\fR. The second spooler
+is called "Dump PostScript" and uses a pipe to
+cat to send the raw PostScript code into the
+user's home directory into a file called like the printjob.
+
+.nf
+HP 8100:\\
+ :pr=|/usr/bin/lpr \-Plp \-J"%J":\\
+ :sp:\\
+ :ca=/tmp/print:\\
+ :am=uams_guest.so,uams_pam.so:\\
+ :pd=/etc/atalk/ppds/hp8100.ppd:
+
+Dump PostScript:LaserWriter@Server:\\
+ :pr=|cat >/home/%U/%J\-prn.out:\\
+ :pd=/usr/share/lib/ppd/mooralana.ppd:\\
+ :sp:au:op=lp:\\
+ :am=uams_clrtxt.so:
+.fi
+.PP
+Starting with Netatalk 2.0 direct CUPS integration is available.
+In this case, defining only a queue name as \fBpr\fR
+parameter won't invoke the SysV lpd daemon but uses CUPS instead.
+Unless a specific PPD has been assigned using the \fBpd\fR
+switch, the PPD configured in CUPS will be used by
+papd, too.
+.PP
+There exists one special share named "cupsautoadd". If this is
+present as the first entry then all available CUPS queues will be served
+automagically using the parameters assigned to this global share. But
+subsequent printer definitions can be used to override these global
+settings for individual spoolers.
+.PP
+\fBpapd.conf CUPS examples\fR
+.PP
+The first entry sets up automatic sharing of all CUPS
+printers. All those shares appear in the zone "1st floor" and since
+no additional settings have been made, they use the CUPS printer
+name as NBP name and use the PPD configured in CUPS. The second
+entry defines different settings for one single CUPS printer. It's
+NBP name is differing from the printer's name and the registration
+happens in another zone.
+
+.nf
+cupsautoadd@1st floor:op=root:
+
+Boss' LaserWriter@2nd floor:\\
+ :pr=laserwriter\-chief:
+.fi
.SH SEE\ ALSO
\fBpapd\fR(8),
\fBatalkd.conf\fR(5),
-\fBlpd\fR(8)
+\fBlpd\fR(8),
+\fBlpoptions\fR(8)
+
-.TH afpd 8 06\ Jan\ 2004 "Netatalk 2.0-beta1"
+.TH afpd 8 06\ Jan\ 2004 "Netatalk 2.0-beta2"
.SH NAME
afpd \- AppleTalk Filing Protocol daemon
.SH SYNOPSIS
-.TH atalkd 8 17\ Nov\ 1995 "Netatalk 2.0-beta1"
+.TH atalkd 8 17\ Nov\ 1995 "Netatalk 2.0-beta2"
.SH NAME
atalkd \- AppleTalk RTMP, NBP, ZIP, and AEP manager
.SH SYNOPSIS
-.TH cnid_dbd 8 2\ Dec\ 2003 "Netatalk 2.0-beta1"
+.TH cnid_dbd 8 2\ Dec\ 2003 "Netatalk 2.0-beta2"
.SH NAME
cnid_dbd \- implement access to CNID databases through a dedicated daemon process
.SH SYNOPSIS
the \fIcdb\fR backend. It is therefore possible
to switch between the two backends as necessary.
.PP
-cnid_dbd inherits the effective userid and
-groupid from \fIcnid_metad\fR on startup, which
-is normally caused by \fIafpd\fR serving a
-netatalk volume to a client. It changes to the \fIBerkleley
-DB\fR database home directory \fIdbdir\fR
-that is associated with the volume, opens the database and starts serving
-requests using the filedescriptor \fIclntfd\fR.
-Subsequent instances of \fIafpd\fR that
-want to access the same volume are redirected to the running
-cnid_dbd by \fIcnid_metad\fR
-via the filedescriptor \fIctrlfd\fR.
+cnid_dbd inherits the effective userid and groupid
+from \fIcnid_metad\fR on startup, which is normally
+caused by \fIafpd\fR serving a netatalk volume to a
+client. It changes to the \fIBerkleley DB\fR
+database home directory \fIdbdir\fR that is
+associated with the volume. If the userid inherited from \fIcnid_metad\fR is 0 (root), cnid_dbd
+will change userid and groupid to the owner and group of the database home
+directory. Otherwise, it will continue to use the inherited values.
+cnid_dbd will then attempt to open the database and
+start serving requests using filedescriptor \fIclntfd\fR. Subsequent instances of \fIafpd\fR that want to access the same volume are redirected
+to the running cnid_dbd process by \fIcnid_metad\fR via the filedescriptor \fIctrlfd\fR.
.PP
cnid_dbd can be configured to run forever or to
exit after a period of inactivity. If cnid_dbd receives
updates during recovery (transactions).
.PP
If transactions are used the \fIBerkleley DB\fR
-database subsystem will create files named log.xxxxxxxxxx in the
-database home directory \fIdbdir\fR, where xxxxxxxxxx
-is a monotonically increasing integer. These files contain information to
-replay database changes and are not automatically removed. Please see the sections
+database subsystem will create files named log.xxxxxxxxxx in the database home
+directory \fIdbdir\fR, where xxxxxxxxxx is a monotonically
+increasing integer. These files contain information to replay database changes and are
+not automatically removed, unless the \fIlogfile_autoremove\fR option is specified in the \fIdb_param\fR configuration file (see below). Please see the sections
\fIDatabase and log file archival\fR, \fI
Log file removal\fR and the documentation of the \fI
db_archive\fR command line utility in the Berkeley DB Tutorial and Reference
-for information when and how it is safe to remove these files.
+for information when and how it is safe to remove these files manually.
.PP
Do not use cnid_dbd for databases on NFS mounted file
systems. It makes the whole point of securing database changes properly moot. Use
more spaces, followed by the parameter value, followed by a newline. The
following parameters are currently recognized:
.TP
+\fIlogfile_autoremove\fR
+This flag is ignored unless transactional support is enabled. If set to 1,
+unused Berkeley DB transactional logfiles (log.xxxxxxxxxx in the database home
+directory) are removed on startup of cnid_dbd. This is
+usually safe if the content of the database directory is backed up on a
+regular basis. Default: 0.
+.TP
\fIcachesize\fR
Determines the size of the Berkeley DB cache in kilobytes.
Default: 1024. Each cnid_dbd process grabs that
size\fR that gives more detailed information.
.TP
\fInosync\fR
-This flag is only valid if transactional support is enabled.
+This flag is ignored unless transactional support is enabled.
If it is set to 1, transactional changes to the database are not
synchronously written to disk when the transaction completes. This
will increase performance considerably at the risk of recent changes
cnid_dbd exits. Default: 600. Set this to 0 to
disable the timeout.
.SH SEE\ ALSO
-\fBcnid_metad\fR(1),
+\fBcnid_metad\fR(8),
\fBafpd\fR(8)
-.TH cnid_metad 8 28\ Nov\ 2003 "Netatalk 2.0-beta1"
+.TH cnid_metad 8 28\ Nov\ 2003 "Netatalk 2.0-beta2"
.SH NAME
cnid_metad \- start cnid_dbd daemons on request
.SH SYNOPSIS
as cnid_metad is restarted \fIafpd\fR
processes will transparently reconnect.
.SH SEE\ ALSO
-\fBcnid_dbd\fR(1),
+\fBcnid_dbd\fR(8),
\fBafpd\fR(8)
.\" t
-.TH papd 8 06\ January\ 2004 "Netatalk 2.0-beta1"
+.TH papd 8 13\ June\ 2004 "Netatalk 2.0-beta2"
.SH NAME
papd \- AppleTalk print server daemon
.SH SYNOPSIS
.SH DESCRIPTION
papd is the AppleTalk printer daemon. This daemon
accepts print jobs from AppleTalk clients (typically Macintosh computers)
-using the Printer Access Protocol (PAP). papd spools
-jobs directly into an \fBlpd\fR(8)
+using the Printer Access Protocol (PAP). When used with System V printing
+systems, papd spools jobs directly into an
+\fBlpd\fR(8)
spool directory and wakes up lpd after accepting a job
from the network to have it re\-examine the appropriate spool directory.
The actual printing and spooling is handled entirely by
-lpd. papd can also pipe the print
-job to an external program for processing, and this is the preferred
-method to avoid compatibility problems with all the flavors of
-lpd in use.
+lpd.
+.PP
+papd can also pipe the print job to an external
+program for processing, and this is the preferred method on systems not using
+CUPS to avoid compatibility problems with all the flavours of lpd
+in use.
+.PP
+As of version 2.0, CUPS is also supported. Simply using
+\fIcupsautoadd\fR as first papd.conf entry will
+share all CUPS printers automagically using the PPD files configured in CUPS.
+It ist still possible to overwrite these defaults by individually define
+printer shares. See \fBpapd.conf\fR(5)
+for details
.PP
papd is typically started at boot time, out of
system init scripts. It first reads from its configuration file,
\&'lp'
T} T{
LPD
-printer name (or print command)
+or CUPS printer name (or pipe to a print command)
T}
T{
op
name for LPD spooling
T}
T{
+au
+T} T{
+bool
+T} T{
+false
+T} T{
+Whether to do authenticated printing or not
+T}
+T{
ca
T} T{
str
Printer's
AppleTalk address
T}
+T{
+co
+T} T{
+str
+T} T{
+NULL
+T} T{
+CUPS options as supplied to the \fBlp\fR(1) command with "\-o"
+T}
+T{
+fo
+T} T{
+bool
+T} T{
+false
+T} T{
+adjust lineending for foomatic\-rip
+T}
.TE
-If no
-configuration file is given, the hostname of the machine is used as the
+If no configuration file is given, the hostname of the machine is used as the
NBP name and all options take their default value.
.SH OPTIONS
.TP
Consult \fIprintcap\fR instead of
\fB/etc/printcap\fR for LPD configuration
information.
-.SH EXAMPLES
-The following papd configuration file sets up three print spoolers.
-The first spooler is known by the NBP name Mac Printer Spooler, and uses a
-PPD file located in \fB/usr/share/lib/ppd\fR. In addition,
-the user mcs will be the owner of all jobs that are spooled. The second
-spooler is known as HP Printer and all options are the default. The third
-spooler is known as HP 8100. It pipes the print job to lpr for printing.
-PSSP authenticated printing is enabled, as is CAP\-style authenticated
-printing. Both methods support guest and cleartext authentication as
-specified by the '\fBam\fR' option. The PPD used is
-\fB/etc/atalk/ppds/hp8100.ppd\fR.
-
-.nf
-Mac Printer Spooler:\\
- :pr=ps:\\
- :pd=/usr/share/lib/ppd/HPLJ_4M.PPD:\\
- :op=mcs:
-
-HP Printer:\\
- :
-
-HP 8100:\\
- :pr=|/usr/bin/lpr \-Plp:\\
- :sp:\\
- :ca=/tmp/print:\\
- :am=uams_guest.so,uams_pam.so:\\
- :pd=/etc/atalk/ppds/hp8100.ppd:
-.fi
.SH NOTES
PSSP (Print Server Security Protocol) is an authentication protocol
carried out through postscript printer queries to the print server. Using
It may be necessary to re\-setup the printer on each client the first time
PSSP is enabled, so that the client can figure out that authentication is
required to print. You can enable PSSP on a per\-printer basis. PSSP is the
-recommended method of authenticating printers as it is more robust that
+recommended method of authenticating printers as it is more robust than
CAP\-style authentication, described below.
.PP
CAP\-style authentication gets its name from the method the CAP
\&'am' option) applies to all printers. It is not possible to define
different authentication methods on each printer. You can specify the list
of UAMS multiple times, but only the last setting will be used. Currently
-only uams_guest.so, uams_passwd.so, and uams_pam.so are supported as
-printer authentication methods. The guest method requires a valid
-username, but not a password. The passwd and pam methods require both a
-valid username and the correct password.
+only uams_guest.so and uams_clrtxt.so are supported as printer authentication
+methods. The guest method requires a valid username, but not a password.
+The Cleartext UAM requires both a valid username and the correct password.
.RS
\fBNote\fR
.PP
-The OSX printing system doesn't seem to support
-authentification anymore.
+As of this writing, Mac OS X makes no use of PSSP authentication
+any longer. CAP\-style authentication normally won't be an option, too
+caused by the use of AFP over TCP these days.
.RE
.PP
.SH FILES
papd accepts characters with the high bit set (a
full 8\-bits) from the clients, but some PostScript printers (including
Apple Computer's LaserWriter family) only accept 7\-bit characters on
-their serial interface by default. You will need to configure your printer
-to accept a full 8 bits.
+their serial interface by default. The same applies for some printers when
+they're accessed via TCP/IP methods (remote LPR or socket). You will need
+to configure your printer to accept a full 8 bits or take special
+precautions and convert the printjob's encoding (eg. by using \fIco="protocol=BCP"\fR when using CUPS 1.1.19 or above).
+.PP
+When printing clients run MacOS 10.2 or above, take care that PPDs do
+not make use of \fI*cupsFilter:\fR comments unless
+the appropriate filters are installed at the client's side, too (remember:
+Starting with 10.2 Apple chose to integrate CUPS into MacOS X). For in\-depth
+information on how CUPS uses PPDs see chapter 3.4 in
+http://tinyurl.com/zbxn)
.SH SEE\ ALSO
-\fBlpr\fR(1),\fBlprm\fR(1),\fBprintcap\fR(5),\fBlpc\fR(8),\fBlpd\fR(8).
+\fBlpr\fR(1),\fBlprm\fR(1),\fBprintcap\fR(5),\fBlpc\fR(8),\fBlpd\fR(8), \fBlp\fR(1).
-.TH papstatus 8 17\ Dec\ 1991 "Netatalk 2.0-beta1"
+.TH papstatus 8 17\ Dec\ 1991 "Netatalk 2.0-beta2"
.SH NAME
papstatus \- get the status of an AppleTalk\-connected printer
.SH SYNOPSIS
file that contains printer name
.SH SEE\ ALSO
\fBnbp\fR(1),
-\fBpap\fR(8)
+\fBpap\fR(1)
-.TH psf 8 17\ Dec\ 1991 "Netatalk 2.0-beta1"
+.TH psf 8 17\ Dec\ 1991 "Netatalk 2.0-beta2"
.SH NAME
psf \- PostScript filter
.SH SYNOPSIS
.SH SEE\ ALSO
\fBpsorder\fR(1),
\fBprintcap\fR(5),
-\fBlpd\fR(8),
-\fBmknod\fR(8),
-\fBpap\fR(8).
+\fBlpd\fR(1),
+\fBmknod\fR(1),
+\fBpap\fR(1).
-.TH timelord 8 27\ Jun\ 2001 "Netatalk 2.0-beta1"The\ Netatalk\ Project
+.TH timelord 8 27\ Jun\ 2001 "Netatalk 2.0-beta2"The\ Netatalk\ Project
.SH NAME
timelord \- Macintosh time server daemon
.SH SYNTAX
projects / netatalk.git / commitdiff