1 <?xml version="1.0" encoding="UTF-8"?>
2 <refentry id="afp.conf.5">
4 <refentrytitle>afp.conf</refentrytitle>
6 <manvolnum>5</manvolnum>
8 <refmiscinfo class="date">13 Sep 2013</refmiscinfo>
10 <refmiscinfo class="source">@NETATALK_VERSION@</refmiscinfo>
14 <refname>afp.conf</refname>
16 <refpurpose>Netatalk configuration file <indexterm>
17 <primary>afp.conf</primary>
18 </indexterm></refpurpose>
22 <title>SYNOPSIS</title>
24 <para>The <filename>afp.conf</filename> file is the configuration file for
25 the <emphasis role="bold">Netatalk</emphasis> AFP file server.</para>
27 <para>All AFP specific configuration and AFP volume definitions are done
31 <refsect1 id="FILEFORMATSECT">
32 <title>FILE FORMAT</title>
34 <para>The file consists of sections and parameters. A section begins with
35 the name of the section in square brackets and continues until the next
36 section begins. Sections contain parameters of the form: <programlisting>
37 <replaceable>name</replaceable> = <replaceable>value </replaceable>
38 </programlisting></para>
40 <para>The file is line-based - that is, each newline-terminated line
41 represents either a comment, a section name or a parameter.</para>
43 <para>Section and parameter names are case sensitive.</para>
45 <para>Only the first equals sign in a parameter is significant. Whitespace
46 before or after the first equals sign is discarded. Leading, trailing and
47 internal whitespace in section and parameter names is irrelevant. Leading
48 and trailing whitespace in a parameter value is discarded. Internal
49 whitespace within a parameter value is retained verbatim.</para>
51 <para>Any line beginning with a semicolon (<quote>;</quote>) or a hash
52 (<quote>#</quote>) character is ignored, as are lines containing only
55 <para>Any line ending in a <quote> <literal>\</literal> </quote> is
56 continued on the next line in the customary UNIX fashion.</para>
58 <para>The values following the equals sign in parameters are all either a
59 string (no quotes needed) or a boolean, which may be given as yes/no, 1/0
60 or true/false. Case is not significant in boolean values, but is preserved
61 in string values. Some items such as create masks are numeric.</para>
63 <para>The parameter <option>include =
64 <replaceable>path</replaceable></option> allows you to include one config
65 file inside another. The file is included literally, as though typed in
66 place. Nested includes are not supported.</para>
70 <title>SECTION DESCRIPTIONS</title>
72 <para>Each section in the configuration file (except for the [Global]
73 section) describes a shared resource (known as a <quote>volume</quote>).
74 The section name is the name of the volume and the parameters within the
75 section define the volume attributes and options.</para>
77 <para>There are two special sections, [Global] and [Homes], which are
78 described under <emphasis>special sections</emphasis>. The following notes
79 apply to ordinary section descriptions.</para>
81 <para>A volume consists of a directory to which access is being given plus
82 a description of the access rights which are granted to the user of the
83 service. For volumes the <option>path</option> option must specify the
84 directory to share.</para>
86 <para>Any volume section without <option>path</option> option is
87 considered a <emphasis>vol preset</emphasis> which can be selected in
88 other volume sections via the <option>vol preset</option> option and
89 constitutes defaults for the volume. For any option specified both in a
90 preset <emphasis>and</emphasis> in a volume section the volume section
91 setting completely substitutes the preset option.</para>
93 <para>The access rights granted by the server are masked by the access
94 rights granted to the specified or guest UNIX user by the host system. The
95 server does not grant more access than the host system grants.</para>
97 <para>The following sample section defines an AFP volume. The user has
98 full access to the path <filename>/foo/bar</filename>. The share is
99 accessed via the share name <literal>baz</literal>: <programlisting> [baz]
100 path = /foo/bar </programlisting></para>
104 <title>SPECIAL SECTIONS</title>
107 <title>The [Global] section</title>
109 <para>Parameters in this section apply to the server as a whole.
110 Parameters denoted by a (G) below are must be set in this
115 <title>The [Homes] section</title>
117 <para>This section enable sharing of the UNIX server user home
118 directories. Specifying an optional <option>path</option> parameter
119 means that not the whole user home will be shared but the subdirectory
120 <option>path</option>. It is necessary to define the <option>basedir
121 regex</option> option. It should be a regex which matches the parent
122 directory of the user homes. Parameters denoted by a (H) belong to
123 volume sections. The optional parameter <option>home name</option> can
124 be used to change the AFP volume name which <emphasis>$u's
125 home</emphasis> by default. See below under VARIABLE
126 SUBSTITUTIONS.</para>
128 <para>The following example illustrates this. Given all user home
129 directories are stored under <filename>/home</filename>:
130 <programlisting> [Homes]
132 basedir regex = /home</programlisting> For a user
133 <emphasis>john</emphasis> this results in an AFP home volume with a path
134 of <filename>/home/john/afp-data</filename>.</para>
136 <para>If <option>basedir regex</option> contains symlink, set the
137 canonicalized absolute path. When <filename>/home</filename> links to
138 <filename>/usr/home</filename>: <programlisting> [Homes]
139 basedir regex = /usr/home</programlisting></para>
144 <title>PARAMETERS</title>
146 <para>Parameters define the specific attributes of sections.</para>
148 <para>Some parameters are specific to the [Global] section (e.g.,
149 <emphasis>log type</emphasis>). All others are permissible only in volume
150 sections. The letter <emphasis>G</emphasis> in parentheses indicates that
151 a parameter is specific to the [Global] section. The letter
152 <emphasis>V</emphasis> indicates that a parameter can be specified in a
153 volume specific section.</para>
157 <title>VARIABLE SUBSTITUTIONS</title>
159 <para>You can use variables in volume names. The use of variables in paths
160 is not supported for now.</para>
164 <para>if you specify an unknown variable, it will not get
169 <para>if you specify a known variable, but that variable doesn't have
170 a value, it will get ignored.</para>
174 <para>The variables which can be used for substitutions are:</para>
181 <para>basename</para>
189 <para>client's ip address</para>
197 <para>volume pathname on server</para>
205 <para>full name (contents of the gecos field in the passwd
214 <para>group name</para>
222 <para>hostname</para>
230 <para>client's ip, without port</para>
238 <para>server name (this can be the hostname)</para>
246 <para>user name (if guest, it is the user that guest is running
255 <para>volume name</para>
263 <para>prints dollar sign ($)</para>
270 <title>EXPLANATION OF GLOBAL PARAMETERS</title>
273 <title>Authentication Options</title>
277 <term>ad domain = <parameter>DOMAIN</parameter>
278 <type>(G)</type></term>
281 <para>Append @DOMAIN to username when authenticating. Useful in
282 Active Directory environments that otherwise would require the
283 user to enter the full user@domain string.</para>
288 <term>admin auth user = <parameter>user</parameter>
289 <type>(G)</type></term>
292 <para>Specifying eg "<option>admin auth user = root</option>"
293 whenever a normal user login fails, afpd will try to authenticate
294 as the specified <option>admin auth user</option>. If this
295 succeeds, a normal session is created for the original connecting
296 user. Said differently: if you know the password of <option>admin
297 auth user</option>, you can authenticate as any other user.</para>
302 <term>k5 keytab = <replaceable>path</replaceable>
303 <type>(G)</type></term>
305 <term>k5 service = <replaceable>service</replaceable>
306 <type>(G)</type></term>
308 <term>k5 realm = <replaceable>realm</replaceable>
309 <type>(G)</type></term>
312 <para>These are required if the server supports the Kerberos 5
313 authentication UAM.</para>
318 <term>nt domain = <parameter>DOMAIN</parameter>
319 <type>(G)</type></term>
321 <term>nt separator = <parameter>SEPARATOR</parameter>
322 <type>(G)</type></term>
325 <para>Use for eg. winbind authentication, prepends both strings
326 before the username from login and then tries to authenticate with
327 the result through the available and active UAM authentication
333 <term>save password = <replaceable>BOOLEAN</replaceable> (default:
334 <emphasis>yes</emphasis>) <type>(G)</type></term>
337 <para>Enables or disables the ability of clients to save passwords
343 <term>set password = <replaceable>BOOLEAN</replaceable> (default:
344 <emphasis>no</emphasis>) <type>(G)</type></term>
347 <para>Enables or disables the ability of clients to change their
348 passwords via chooser or the "connect to server" dialog.</para>
353 <term>uam list = <replaceable>uam list</replaceable>
354 <type>(G)</type></term>
357 <para>Space or comma separated list of UAMs. (The default is
358 "uams_dhx.so uams_dhx2.so").</para>
360 <para>The most commonly used UAMs are:</para>
364 <term>uams_guest.so</term>
367 <para>allows guest logins</para>
372 <term>uams_clrtxt.so</term>
375 <para>(uams_pam.so or uams_passwd.so) Allow logins with
376 passwords transmitted in the clear. (legacy)</para>
381 <term>uams_randum.so</term>
384 <para>allows Random Number and Two-Way Random Number
385 Exchange for authentication (requires a separate file
386 containing the passwords, either @pkgconfdir@/afppasswd file or
387 the one specified via "<option>passwd file</option>". See
389 <refentrytitle>afppasswd</refentrytitle>
391 <manvolnum>1</manvolnum>
392 </citerefentry> for details. (legacy)</para>
397 <term>uams_dhx.so</term>
400 <para>(uams_dhx_pam.so or uams_dhx_passwd.so) Allow
401 Diffie-Hellman eXchange (DHX) for authentication.</para>
406 <term>uams_dhx2.so</term>
409 <para>(uams_dhx2_pam.so or uams_dhx2_passwd.so) Allow
410 Diffie-Hellman eXchange 2 (DHX2) for authentication.</para>
415 <term>uam_gss.so</term>
418 <para>Allow Kerberos V for authentication (optional)</para>
426 <term>uam path = <replaceable>path</replaceable>
427 <type>(G)</type></term>
430 <para>Sets the default path for UAMs for this server (default is
431 @libdir@/netatalk).</para>
438 <title>Charset Options</title>
440 <para>With OS X Apple introduced the AFP3 protocol. One of the big
441 changes was, that AFP3 uses Unicode names encoded as Decomposed UTF-8
442 (UTF8-MAC). Previous AFP/OS versions used charsets like MacRoman,
443 MacCentralEurope, etc.</para>
445 <para>To be able to serve AFP3 and older clients at the same time,
446 <command>afpd</command> needs to be able to convert between UTF-8 and
447 Mac charsets. Even OS X clients partly still rely on the mac charset. As
448 there's no way, <command>afpd</command> can detect the codepage a pre
449 AFP3 client uses, you have to specify it using the <option>mac
450 charset</option> option. The default is MacRoman, which should be fine
451 for most western users.</para>
453 <para>As <command>afpd</command> needs to interact with UNIX operating
454 system as well, it need's to be able to convert from UTF8-MAC / Mac
455 charset to the UNIX charset. By default <command>afpd</command> uses
456 <emphasis>UTF8</emphasis>. You can set the UNIX charset using the
457 <option>unix charset</option> option. If you're using extended
458 characters in the configuration files for <command>afpd</command>, make
459 sure your terminal matches the <option>unix charset</option>.</para>
463 <term>mac charset = <parameter>CHARSET</parameter>
464 <type>(G)/(V)</type></term>
467 <para>Specifies the Mac clients charset, e.g.
468 <emphasis>MAC_ROMAN</emphasis>. This is used to convert strings
469 and filenames to the clients codepage for OS9 and Classic, i.e.
470 for authentication and AFP messages (SIGUSR2 messaging). This will
471 also be the default for the volumes <option>mac charset</option>.
472 Defaults to <emphasis>MAC_ROMAN</emphasis>.</para>
477 <term>unix charset = <parameter>CHARSET</parameter>
478 <type>(G)</type></term>
481 <para>Specifies the servers unix charset, e.g.
482 <emphasis>ISO-8859-15</emphasis> or <emphasis>EUC-JP</emphasis>.
483 This is used to convert strings to/from the systems locale, e.g.
484 for authentication, server messages and volume names. If
485 <emphasis>LOCALE</emphasis> is set, the systems locale is used.
486 Defaults to <emphasis>UTF8</emphasis>.</para>
491 <term>vol charset = <parameter>CHARSET</parameter>
492 <type>(G)/(V)</type></term>
495 <para>Specifies the encoding of the volumes filesystem. By
496 default, it is the same as <option>unix charset</option>.</para>
503 <title>Password Options</title>
507 <term>passwd file = <parameter>path</parameter>
508 <type>(G)</type></term>
511 <para>Sets the path to the Randnum UAM passwd file for this server
512 (default is @pkgconfdir@/afppasswd).</para>
517 <term>passwd minlen = <parameter>number</parameter>
518 <type>(G)</type></term>
521 <para>Sets the minimum password length, if supported by the
529 <title>Network Options</title>
533 <term>advertise ssh = <replaceable>BOOLEAN</replaceable> (default:
534 <emphasis>no</emphasis>) <type>(G)</type></term>
537 <para>Allows old Mac OS X clients (10.3.3-10.4) to automagically
538 establish a tunneled AFP connection through SSH. If this option is
539 set, the server's answers to client's FPGetSrvrInfo requests
540 contain an additional entry. It depends on both client's settings
541 and a correctly configured and running <citerefentry>
542 <refentrytitle>sshd</refentrytitle>
544 <manvolnum>8</manvolnum>
545 </citerefentry> on the server to let things work.</para>
548 <para>Setting this option is not recommended since globally
549 encrypting AFP connections via SSH will increase the server's
550 load significantly. On the other hand, Apple's client side
551 implementation of this feature in MacOS X versions prior to
552 10.3.4 contained a security flaw.</para>
558 <term>afp interfaces = <replaceable>name [name ...]</replaceable>
559 <type>(G)</type></term>
561 <para>Specifies the network interfaces that the server should
562 listens on. The default is advertise the first IP address of the
563 system, but to listen for any incoming request.</para>
568 <term>afp listen = <replaceable>ip address[:port] [ip address[:port]
569 ...]</replaceable> <type>(G)</type></term>
572 <para>Specifies the IP address that the server should advertise
573 <emphasis role="bold">and</emphasis> listens to. The default is
574 advertise the first IP address of the system, but to listen for
575 any incoming request. The network address may be specified either
576 in dotted-decimal format for IPv4 or in hexadecimal format for
578 <para>IPv6 address + port combination must use URL the format
579 using square brackets [IPv6]:port</para>
584 <term>afp port = <replaceable>port number</replaceable>
585 <type>(G)</type></term>
588 <para>Allows a different TCP port to be used for AFP. The default
589 is 548. Also sets the default port applied when none specified in
590 an <option>afp listen</option> option.</para>
595 <term>cnid listen = <replaceable>ip address[:port] [ip
596 address[:port] ...]</replaceable> <type>(G)</type></term>
599 <para>Specifies the IP address that the CNID server should listen
600 on. The default is <emphasis
601 role="bold">localhost:4700</emphasis>.</para>
606 <term>disconnect time = <replaceable>number</replaceable>
607 <type>(G)</type></term>
610 <para>Keep disconnected AFP sessions for
611 <parameter>number</parameter> hours before dropping them. Default
617 <term>dsireadbuf = <replaceable>number</replaceable>
618 <type>(G)</type></term>
621 <para>Scale factor that determines the size of the DSI/TCP
622 readahead buffer, default is 12. This is multiplies with the DSI
623 server quantum (default ~300k) to give the size of the buffer.
624 Increasing this value might increase throughput in fast local
625 networks for volume to volume copies. <emphasis>Note</emphasis>:
626 This buffer is allocated per afpd child process, so specifying
627 large values will eat up large amount of memory (buffer size *
628 number of clients).</para>
633 <term>fqdn = <replaceable>name:port</replaceable>
634 <type>(G)</type></term>
637 <para>Specifies a fully-qualified domain name, with an optional
638 port. This is discarded if the server cannot resolve it. This
639 option is not honored by AppleShare clients <= 3.8.3. This
640 option is disabled by default. Use with caution as this will
641 involve a second name resolution step on the client side. Also
642 note that afpd will advertise this name:port combination but not
643 automatically listen to it.</para>
648 <term>hostname = <replaceable>name</replaceable>
649 <type>(G)</type></term>
652 <para>Use this instead of the result from calling hostname for
653 determining which IP address to advertise, therefore the hostname
654 is resolved to an IP which is the advertised. This is NOT used for
655 listening and it is also overwritten by <option>afp
656 listen</option>.</para>
661 <term>max connections = <replaceable>number</replaceable>
662 <type>(G)</type></term>
665 <para>Sets the maximum number of clients that can simultaneously
666 connect to the server (default is 200).</para>
671 <term>server quantum = <replaceable>number</replaceable>
672 <type>(G)</type></term>
675 <para>This specifies the DSI server quantum. The default value is
676 0x100000 (1 MiB). The maximum value is 0xFFFFFFFFF, the minimum is
677 32000. If you specify a value that is out of range, the default
678 value will be set. Do not change this value unless you're
679 absolutely sure, what you're doing</para>
684 <term>sleep time = <replaceable>number</replaceable>
685 <type>(G)</type></term>
688 <para>Keep sleeping AFP sessions for <parameter>number</parameter>
689 hours before disconnecting clients in sleep mode. Default is 10
695 <term>tcprcvbuf = <replaceable>number</replaceable>
696 <type>(G)</type></term>
699 <para>Try to set TCP receive buffer using setsockpt(). Often OSes
700 impose restrictions on the applications ability to set this
706 <term>tcpsndbuf = <replaceable>number</replaceable>
707 <type>(G)</type></term>
710 <para>Try to set TCP send buffer using setsockpt(). Often OSes
711 impose restrictions on the applications ability to set this
717 <term>use sendfile = <replaceable>BOOLEAN</replaceable> (default:
718 <emphasis>yes</emphasis>) <type>(G)</type></term>
721 <para>Whether to use sendfile<indexterm>
722 <primary>sendfile</primary>
723 </indexterm> syscall for sending file data to clients.</para>
728 <term>zeroconf = <replaceable>BOOLEAN</replaceable> (default:
729 <emphasis>yes</emphasis>) <type>(G)</type></term>
732 <para>Whether to use automatic Zeroconf<indexterm>
733 <primary>Zeroconf</primary>
735 <secondary>Bonjour</secondary>
736 </indexterm> service registration if Avahi or mDNSResponder were
744 <title>Miscellaneous Options</title>
748 <term>admin group = <replaceable>group</replaceable>
749 <type>(G)</type></term>
752 <para>Allows users of a certain group to be seen as the superuser
753 when they log in. This option is disabled by default.</para>
758 <term>afp read locks = <replaceable>BOOLEAN</replaceable> (default:
759 <emphasis>no</emphasis>) <type>(G)</type></term>
762 <para>Whether to apply locks to the byte region read in FPRead
763 calls. The AFP spec mandates this, but it's not really in line
764 with UNIX semantics and is a performance hug.</para>
769 <term>afpstats = <replaceable>BOOLEAN</replaceable> (default:
770 <emphasis>no</emphasis>) <type>(G)</type></term>
773 <para>Whether to provide AFP runtime statistics (connected
774 users, open volumes) via dbus.</para>
779 <term>basedir regex = <replaceable>regex</replaceable>
780 <type>(H)</type></term>
783 <para>Regular expression which matches the parent directory of the
784 user homes. If <option>basedir regex</option> contains symlink,
785 you must set the canonicalized absolute path. In the simple case
786 this is just a path ie <option>basedir regex =
787 /home</option></para>
792 <term>close vol = <replaceable>BOOLEAN</replaceable> (default:
793 <emphasis>no</emphasis>) <type>(G)</type></term>
796 <para>Whether to close volumes possibly opened by clients when
797 they're removed from the configuration and the configuration is
803 <term>cnid server = <replaceable>ipaddress[:port]</replaceable>
804 <type>(G)/(V)</type></term>
807 <para>Specifies the IP address and port of a cnid_metad server,
808 required for CNID dbd backend. Defaults to localhost:4700. The
809 network address may be specified either in dotted-decimal format
810 for IPv4 or in hexadecimal format for IPv6.-</para>
815 <term>dircachesize = <replaceable>number</replaceable>
816 <type>(G)</type></term>
819 <para>Maximum possible entries in the directory cache. The cache
820 stores directories and files. It is used to cache the full path to
821 directories and CNIDs which considerably speeds up directory
824 <para>Default size is 8192, maximum size is 131072. Given value is
825 rounded up to nearest power of 2. Each entry takes about 100
826 bytes, which is not much, but remember that every afpd child
827 process for every connected user has its cache.</para>
832 <term>extmap file = <parameter>path</parameter>
833 <type>(G)</type></term>
836 <para>Sets the path to the file which defines file extension
837 type/creator mappings. (default is @pkgconfdir@/extmap.conf).</para>
842 <term>guest account = <replaceable>name</replaceable>
843 <type>(G)</type></term>
846 <para>Specifies the user that guests should use (default is
847 "nobody"). The name should be quoted.</para>
852 <term>home name = <replaceable>name</replaceable>
853 <type>(H)</type></term>
856 <para>AFP user home volume name. The default is <emphasis>user's
857 home</emphasis>.</para>
862 <term>login message = <replaceable>message</replaceable>
863 <type>(G)/(V)</type></term>
866 <para>Sets a message to be displayed when clients logon to the
867 server. The message should be in <option>unix charset</option> and
868 should be quoted. Extended characters are allowed.</para>
873 <term>ignored attributes = <replaceable>all | nowrite | nodelete | norename</replaceable>
874 <type>(G)/(V)</type></term>
877 <para>Speficy a set of file and directory attributes that shall
878 be ignored by the server, <option>all</option> includes all
879 the other options.</para>
880 <para>In OS X when the Finder sets a lock on a file/directory or you
881 set the BSD uchg flag in the Terminal, all three attributes are
882 used. Thus in order to ignore the Finder lock/BSD uchg flag, add
883 set <emphasis>ignored attributes = all</emphasis>.</para>
888 <term>mimic model = <replaceable>model</replaceable>
889 <type>(G)</type></term>
892 <para>Specifies the icon model that appears on clients. Defaults
893 to off. Note that afpd must support Zeroconf.
894 Examples: RackMac (same as Xserve), PowerBook, PowerMac,
895 Macmini, iMac, MacBook, MacBookPro, MacBookAir, MacPro,
896 AppleTV1,1, AirPort.</para>
901 <term>signature = <text> <type>(G)</type></term>
904 <para>Specify a server signature. The maximum length is 16
905 characters. This option is useful for clustered environments, to
906 provide fault isolation etc. By default, afpd generate signature
908 <filename>@localstatedir@/netatalk/afp_signature.conf</filename>
909 automatically (based on random number). See also
910 asip-status.pl(1).</para>
915 <term>solaris share reservations =
916 <replaceable>BOOLEAN</replaceable> (default:
917 <emphasis>yes</emphasis>) <type>(G)</type></term>
920 <para>Use share reservations on Solaris. Solaris CIFS server uses
921 this too, so this makes a lock coherent multi protocol
928 <replaceable>BOOLEAN</replaceable> (default:
929 <emphasis>no</emphasis>) <type>(G)/(V)</type></term>
932 <para>Whether to enable Spotlight searches. Note: once the global
933 option is enabled, any volume that is not enabled won't be
934 searchable at all.</para>
939 <term>veto message = <replaceable>BOOLEAN</replaceable> (default:
940 <emphasis>no</emphasis>) <type>(G)</type></term>
943 <para>Send optional AFP messages for vetoed files. Then whenever a
944 client tries to access any file or directory with a vetoed name,
945 it will be sent an AFP message indicating the name and the
951 <term>vol dbpath = <replaceable>path</replaceable>
952 <type>(G)</type></term>
955 <para>Sets the database information to be stored in path. You have
956 to specify a writable location, even if the volume is read only.
958 <filename>@localstatedir@/netatalk/CNID/</filename>.</para>
963 <term>vol dbnest = <replaceable>BOOLEAN</replaceable> (default:
964 <emphasis>no</emphasis>) <type>(G)</type></term>
967 <para>Setting this option to true brings back Netatalk 2
968 behaviour of storing the CNID database in a folder called
969 .AppleDB inside the volume root of each share.</para>
974 <term>volnamelen = <replaceable>number</replaceable>
975 <type>(G)</type></term>
978 <para>Max length of UTF8-MAC volume name for Mac OS X. Note that
979 Hangul is especially sensitive to this.</para>
981 <para><programlisting> 73: limit of Mac OS X 10.1 80: limit of Mac
982 OS X 10.4/10.5 (default) 255: limit of recent Mac OS
983 X</programlisting> Mac OS 9 and earlier are not influenced by
984 this, because Maccharset volume name is always limited to 27
990 <term>vol preset = <replaceable>name</replaceable>
991 <type>(G)/(V)</type></term>
994 <para>Use section <option>name</option> as option preset for all
995 volumes (when set in the [Global] section) or for one volume (when
996 set in that volume's section).</para>
1003 <title>Logging Options</title>
1007 <term>log file = <replaceable>logfile</replaceable>
1008 <type>(G)</type></term>
1011 <para>If not specified Netatalk logs to syslogs daemon facility.
1012 Otherwise it logs to <option>logfile</option>.</para>
1017 <term>log level = <replaceable>type:level [type:level
1018 ...]</replaceable> <type>(G)</type></term>
1020 <term>log level = <replaceable>type:level,[type:level,
1021 ...]</replaceable> <type>(G)</type></term>
1024 <para>Specify that any message of a loglevel up to the given
1025 <option>log level</option> should be logged.</para>
1027 <para>By default afpd logs to syslog with a default logging setup
1028 equivalent to <option>default:note</option></para>
1030 <para>logtypes: default, afpdaemon, logger, uamsdaemon</para>
1032 <para>loglevels: severe, error, warn, note, info, debug, debug6,
1033 debug7, debug8, debug9, maxdebug</para>
1036 <para>Both logtype and loglevels are case insensitive.</para>
1043 <refsect2 id="fceconf">
1044 <title>Filesystem Change Events (FCE<indexterm>
1045 <primary>FCE</primary>
1046 </indexterm>)</title>
1048 <para>Netatalk includes a nifty filesystem change event mechanism where
1049 afpd processes notify interested listeners about certain filesystem
1050 event by UDP network datagrams.</para>
1054 <term>fce listener = <replaceable>host[:port]</replaceable>
1055 <type>(G)</type></term>
1058 <para>Enables sending FCE events to the specified
1059 <parameter>host</parameter>, default <parameter>port</parameter>
1060 is 12250 if not specified. Specifying multiple listeners is done
1061 by having this option once for each of them.</para>
1067 <replaceable>fmod,fdel,ddel,fcre,dcre,tmsz</replaceable>
1068 <type>(G)</type></term>
1071 <para>Specifies which FCE events are active, default is
1072 <parameter>fmod,fdel,ddel,fcre,dcre</parameter>.</para>
1077 <term>fce coalesce = <replaceable>all|delete|create</replaceable>
1078 <type>(G)</type></term>
1081 <para>Coalesce FCE events.</para>
1086 <term>fce holdfmod = <replaceable>seconds</replaceable>
1087 <type>(G)</type></term>
1090 <para>This determines the time delay in seconds which is always
1091 waited if another file modification for the same file is done by a
1092 client before sending an FCE file modification event (fmod). For
1093 example saving a file in Photoshop would generate multiple events
1094 by itself because the application is opening, modifying and
1095 closing a file multiple times for every "save". Default: 60
1103 <title>Debug Parameters</title>
1105 <para>These options are useful for debugging only.</para>
1109 <term>tickleval = <replaceable>number</replaceable>
1110 <type>(G)</type></term>
1113 <para>Sets the tickle timeout interval (in seconds). Defaults to
1119 <term>timeout = <replaceable>number</replaceable>
1120 <type>(G)</type></term>
1123 <para>Specify the number of tickles to send before timing out a
1124 connection. The default is 4, therefore a connection will timeout
1125 after 2 minutes.</para>
1130 <term>client polling = <replaceable>BOOLEAN</replaceable> (default:
1131 <emphasis>no</emphasis>) <type>(G)</type></term>
1134 <para>With this option enabled, afpd won't advertise that it is
1135 capable of server notifications, so that connected clients poll
1136 the server every 10 seconds to detect changes in opened server
1137 windows. <emphasis>Note</emphasis>: Depending on the number of
1138 simultaneously connected clients and the network's speed, this can
1139 lead to a significant higher load on your network!</para>
1141 <para>Do not use this option any longer as present Netatalk
1142 correctly supports server notifications, allowing connected
1143 clients to update folder listings in case another client changed
1144 the contents.</para>
1150 <refsect2 id="acl_options">
1151 <title>Options for ACL handling</title>
1153 <para>By default, the effective permission of the authenticated user are
1154 only mapped to the mentioned UARights permission structure, not the UNIX
1155 mode. You can adjust this behaviour with the configuration option
1156 <option>mac acls</option>:</para>
1158 <variablelist id="map_acls">
1160 <term>map acls = <parameter>none|rights|mode</parameter>
1161 <type>(G)</type></term>
1164 <para><variablelist>
1169 <para>no mapping of ACLs </para>
1177 <para>effective permissions are mapped to UARights
1178 structure. This is the default.</para>
1186 <para>ACLs are additionally mapped to the UNIX mode of the
1187 filesystem object.</para>
1190 </variablelist></para>
1195 <para>If you want to be able to display ACLs on the client, you must
1196 setup both client and server as part on a authentication domain
1197 (directory service, eg LDAP, Open Directory, Active Directory). The
1198 reason is, in OS X ACLs are bound to UUIDs, not just uid's or gid's.
1199 Therefor Netatalk must be able to map every filesystem uid and gid to a
1200 UUID so that it can return the server side ACLs which are bound to UNIX
1201 uid and gid mapped to OS X UUIDs.</para>
1203 <para>Netatalk can query a directory server using LDAP queries. Either
1204 the directory server already provides an UUID attribute for user and
1205 groups (Active Directory, Open Directory) or you reuse an unused
1206 attribute (or add a new one) to you directory server (eg
1209 <para>The following LDAP options must be configured for Netatalk:</para>
1213 <term>ldap auth method = <parameter>none|simple|sasl</parameter>
1214 <type>(G)</type></term>
1217 <para>Authentication method: <option>none | simple |
1218 sasl</option></para>
1220 <para><variablelist>
1225 <para>anonymous LDAP bind</para>
1233 <para>simple LDAP bind</para>
1241 <para>SASL. Not yet supported !</para>
1244 </variablelist></para>
1249 <term>ldap auth dn = <parameter>dn</parameter>
1250 <type>(G)</type></term>
1253 <para>Distinguished Name of the user for simple bind.</para>
1258 <term>ldap auth pw = <parameter>password</parameter>
1259 <type>(G)</type></term>
1262 <para>Distinguished Name of the user for simple bind.</para>
1267 <term>ldap server = <parameter>host</parameter>
1268 <type>(G)</type></term>
1271 <para>Name or IP address of your LDAP Server. This is only needed
1272 for explicit ACL support in order to be able to query LDAP for
1275 <para>You can use <citerefentry>
1276 <refentrytitle>afpldaptest</refentrytitle>
1278 <manvolnum>1</manvolnum>
1279 </citerefentry> to syntactically check your config.</para>
1284 <term>ldap userbase = <parameter>base dn</parameter>
1285 <type>(G)</type></term>
1288 <para>DN of the user container in LDAP.</para>
1293 <term>ldap userscope = <parameter>scope</parameter>
1294 <type>(G)</type></term>
1297 <para>Search scope for user search: <option>base | one |
1303 <term>ldap groupbase = <parameter>base dn</parameter>
1304 <type>(G)</type></term>
1307 <para>DN of the group container in LDAP.</para>
1312 <term>ldap groupscope = <parameter>scope</parameter>
1313 <type>(G)</type></term>
1316 <para>Search scope for user search: <option>base | one |
1322 <term>ldap uuid attr = <parameter>dn</parameter>
1323 <type>(G)</type></term>
1326 <para>Name of the LDAP attribute with the UUIDs.</para>
1328 <para>Note: this is used both for users and groups.</para>
1333 <term>ldap name attr = <parameter>dn</parameter>
1334 <type>(G)</type></term>
1337 <para>Name of the LDAP attribute with the users short name.</para>
1342 <term>ldap group attr = <parameter>dn</parameter>
1343 <type>(G)</type></term>
1346 <para>Name of the LDAP attribute with the groups short
1352 <term>ldap uuid string = <parameter>STRING</parameter>
1353 <type>(G)</type></term>
1356 <para>Format of the uuid string in the directory. A series of x
1357 and -, where every x denotes a value 0-9a-f and every - is a
1360 <para>Default: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</para>
1365 <term>ldap uuid encoding = <parameter>string | ms-guid (default:
1366 string)</parameter> <type>(G)</type></term>
1369 <para>Format of the UUID of the LDAP attribute, allows usage of
1370 the binary objectGUID fields from Active Directory. If left
1371 unspecified, string is the default, which passes through the ASCII
1372 UUID returned by most other LDAP stores. If set to ms-guid, the
1373 internal UUID representation is converted to and from the binary
1374 format used in the objectGUID attribute found on objects in Active
1375 Directory when interacting with the server.</para>
1376 <para>See also the options <option>ldap user filter</option> and
1377 <option>ldap group filter</option>.</para>
1378 <para><variablelist>
1383 <para>UUID is a string, use with eg OpenDirectory.</para>
1388 <term>ms-guid</term>
1391 <para>Binary objectGUID from Active Directory</para>
1394 </variablelist></para>
1399 <term>ldap user filter = <parameter>STRING (default: unused)</parameter>
1400 <type>(G)</type></term>
1403 <para>Optional LDAP filter that matches user objects. This is necessary for Active Directory
1404 environments where users and groups are stored in the same directory subtree.</para>
1405 <para>Recommended setting for Active Directory: <parameter>objectClass=user</parameter>.</para>
1410 <term>ldap group filter = <parameter>STRING (default: unused)</parameter>
1411 <type>(G)</type></term>
1414 <para>Optional LDAP filter that matches group objects. This is necessary for Active Directory
1415 environments where users and groups are stored in the same directory subtree.</para>
1416 <para>Recommended setting for Active Directory: <parameter>objectClass=group</parameter>.</para>
1425 <title>EXPLANATION OF VOLUME PARAMETERS</title>
1428 <title>Parameters</title>
1430 <para>The section name defines the volume name.
1431 No two volumes may have the same
1432 name. The volume name cannot contain the <keycode>':'</keycode>
1433 character. The volume name is mangled if it is very long. Mac charset
1434 volume name is limited to 27 characters. UTF8-MAC volume name is limited
1435 to volnamelen parameter.</para>
1439 <term>path = <replaceable>PATH</replaceable> <type>(V)</type></term>
1442 <para>The path name must be a fully qualified path name.</para>
1447 <term>appledouble = <replaceable>ea|v2</replaceable>
1448 <type>(V)</type></term>
1451 <para>Specify the format of the metadata files, which are used for
1452 saving Mac resource fork as well. Earlier versions used
1453 AppleDouble v2, the new default format is <emphasis
1454 role="bold">ea</emphasis>.</para>
1459 <term>vol size limit = <replaceable>size in MiB</replaceable>
1460 <type>(V)</type></term>
1463 <para>Useful for Time Machine: limits the reported volume size,
1464 thus preventing Time Machine from using the whole real disk space
1465 for backup. Example: "vol size limit = 1000" would limit the
1466 reported disk space to 1 GB. <emphasis role="bold">IMPORTANT:
1467 </emphasis> This is an approximated calculation taking into
1468 account the contents of Time Machine sparsebundle images. Therefor
1469 you MUST NOT use this volume to store other content when using
1470 this option, because it would NOT be accounted. The calculation
1471 works by reading the band size from the Info.plist XML file of the
1472 sparsebundle, reading the bands/ directory counting the number of
1473 band files, and then multiplying one with the other.</para>
1478 <term>valid users = <replaceable>user @group</replaceable>
1479 <type>(V)</type></term>
1482 <para>The allow option allows the users and groups that access a
1483 share to be specified. Users and groups are specified, delimited
1484 by spaces or commas. Groups are designated by a @ prefix. Names
1485 may be quoted in order to allow for spaces in names. Example:
1486 <programlisting>valid users = user "user 2" @group “@group 2"</programlisting></para>
1491 <term>invalid users = <replaceable>users/groups</replaceable>
1492 <type>(V)</type></term>
1495 <para>The deny option specifies users and groups who are not
1496 allowed access to the share. It follows the same format as the
1497 "valid users" option.</para>
1502 <term>hosts allow = <replaceable>IP host address/IP netmask bits [
1503 ... ]</replaceable> <type>(V)</type></term>
1506 <para>Only listed hosts and networks are allowed, all others are
1507 rejected. The network address may be specified either in
1508 dotted-decimal format for IPv4 or in hexadecimal format for
1511 <para>Example: hosts allow = 10.1.0.0/16 10.2.1.100
1512 2001:0db8:1234::/48</para>
1517 <term>hosts deny = <replaceable>IP host address/IP netmask bits [
1518 ... ]</replaceable> <type>(V)</type></term>
1521 <para>Listed hosts and nets are rejected, all others are
1524 <para>Example: hosts deny = 192.168.100/24 10.1.1.1
1525 2001:db8::1428:57ab</para>
1530 <term>cnid scheme = <replaceable>backend</replaceable>
1531 <type>(V)</type></term>
1534 <para>set the CNID backend to be used for the volume, default is
1535 [@DEFAULT_CNID_SCHEME@] available schemes:
1536 [@compiled_backends@]</para>
1541 <term>ea = <replaceable>none|auto|sys|ad</replaceable>
1542 <type>(V)</type></term>
1545 <para>Specify how Extended Attributes<indexterm>
1546 <primary>Extended Attributes</primary>
1547 </indexterm> are stored. <option>auto</option> is the
1555 <para>Try <option>sys</option> (by setting an EA on the
1556 shared directory itself), fallback to <option>ad</option>.
1557 Requires writable volume for performing test. "<option>read
1558 only = yes</option>" overwrites <option>auto</option> with
1559 <option>none</option>. Use explicit "<option>ea =
1560 sys|ad</option>" for read-only volumes where
1569 <para>Use filesystem Extended Attributes.</para>
1577 <para>Use files in <emphasis>.AppleDouble</emphasis>
1586 <para>No Extended Attributes support.</para>
1594 <term>mac charset = <replaceable>CHARSET</replaceable>
1595 <type>(V)</type></term>
1598 <para>specifies the Mac client charset for this Volume, e.g.
1599 <emphasis>MAC_ROMAN</emphasis>, <emphasis>MAC_CYRILLIC</emphasis>.
1600 If not specified the global setting is applied. This setting is
1601 only required if you need volumes, where the Mac charset differs
1602 from the one globally set in the [Global] section.</para>
1607 <term>casefold = <option>option</option> <type>(V)</type></term>
1610 <para>The casefold option handles, if the case of filenames should
1611 be changed. The available options are:</para>
1613 <para><option>tolower</option> - Lowercases names in both
1616 <para><option>toupper</option> - Uppercases names in both
1619 <para><option>xlatelower</option> - Client sees lowercase, server
1620 sees uppercase.</para>
1622 <para><option>xlateupper</option> - Client sees uppercase, server
1623 sees lowercase.</para>
1628 <term>password = <replaceable>password</replaceable>
1629 <type>(V)</type></term>
1632 <para>This option allows you to set a volume password, which can
1633 be a maximum of 8 characters long (using ASCII strongly
1634 recommended at the time of this writing).</para>
1639 <term>file perm = <replaceable>mode</replaceable>
1640 <type>(V)</type></term>
1642 <term>directory perm = <replaceable>mode</replaceable>
1643 <type>(V)</type></term>
1646 <para>Add(or) with the client requested permissions: <option>file
1647 perm</option> is for files only, <option>directory perm</option>
1648 is for directories only. Don't use with "<option>unix priv =
1649 no</option>".</para>
1652 <title>Volume for a collaborative workgroup</title>
1654 <para><programlisting>file perm = 0660 directory perm =
1655 0770</programlisting></para>
1661 <term>umask = <replaceable>mode</replaceable>
1662 <type>(V)</type></term>
1665 <para>set perm mask. Don't use with "<option>unix priv =
1666 no</option>".</para>
1671 <term>preexec = <replaceable>command</replaceable>
1672 <type>(V)</type></term>
1675 <para>command to be run when the volume is mounted, ignored for
1676 user defined volumes</para>
1681 <term>postexec = <replaceable>command</replaceable>
1682 <type>(V)</type></term>
1685 <para>command to be run when the volume is closed, ignored for
1686 user defined volumes</para>
1691 <term>root preexec = <replaceable>command</replaceable>
1692 <type>(V)</type></term>
1695 <para>command to be run as root when the volume is mounted,
1696 ignored for user defined volumes</para>
1701 <term>root postexec = <replaceable>command</replaceable>
1702 <type>(V)</type></term>
1705 <para>command to be run as root when the volume is closed, ignored
1706 for user defined volumes</para>
1711 <term>rolist = <option>users/groups</option> <type>(V)</type></term>
1714 <para>Allows certain users and groups to have read-only access to
1715 a share. This follows the allow option format.</para>
1720 <term>rwlist = <replaceable>users/groups</replaceable>
1721 <type>(V)</type></term>
1724 <para>Allows certain users and groups to have read/write access to
1725 a share. This follows the allow option format.</para>
1730 <term>veto files = <replaceable>vetoed names</replaceable>
1731 <type>(V)</type></term>
1734 <para>hide files and directories,where the path matches one of the
1735 '/' delimited vetoed names. The veto string must always be
1736 terminated with a '/', eg. "veto1/", "veto1/veto2/".</para>
1743 <title>Volume options</title>
1745 <para>Boolean volume options.</para>
1749 <term>acls = <replaceable>BOOLEAN</replaceable> (default:
1750 <emphasis>yes</emphasis>) <type>(V)</type></term>
1753 <para>Whether to flag volumes as supporting ACLs. If ACL support
1754 is compiled in, this is yes by default.</para>
1759 <term>cnid dev = <replaceable>BOOLEAN</replaceable> (default:
1760 <emphasis>yes</emphasis>) <type>(V)</type></term>
1763 <para>Whether to use the device number in the CNID backends. Helps
1764 when the device number is not constant across a reboot, eg
1770 <term>convert appledouble = <replaceable>BOOLEAN</replaceable>
1771 (default: <emphasis>yes</emphasis>) <type>(V)</type></term>
1774 <para>Whether automatic conversion from <option>appledouble =
1775 v2</option> to <option>appledouble = ea</option> is performed when
1776 accessing filesystems from clients. This is generally useful, but
1777 costs some performance. It's recommendable to run
1778 <command>dbd</command> on volumes and do the conversion with that.
1779 Then this option can be set to no.</para>
1784 <term>delete veto files = <replaceable>BOOLEAN</replaceable>
1785 (default: <emphasis>no</emphasis>) <type>(V)</type></term>
1788 <para>This option is used when Netatalk is attempting to delete a
1789 directory that contains one or more vetoed files or directories
1790 (see the veto files option). If this option is set to no (the
1791 default) then if a directory contains any non-vetoed files or
1792 directories then the directory delete will fail. This is usually
1793 what you want.</para>
1794 <para>If this option is set to yes, then Netatalk will attempt to
1795 recursively delete any files and directories within the vetoed
1801 <term>follow symlinks = <replaceable>BOOLEAN</replaceable> (default:
1802 <emphasis>no</emphasis>) <type>(V)</type></term>
1805 <para>The default setting is false thus symlinks are not followed
1806 on the server. This is the same behaviour as OS X's AFP server.
1807 Setting the option to true causes afpd to follow symlinks on the
1808 server. symlinks may point outside of the AFP volume, currently
1809 afpd doesn't do any checks for "wide symlinks".</para>
1811 <para>This option will subtly break when the symlinks point
1812 across filesystem boundaries.</para>
1818 <term>invisible dots = <replaceable>BOOLEAN</replaceable> (default:
1819 <emphasis>no</emphasis>) <type>(V)</type></term>
1822 <para>make dot files invisible. WARNING: enabling this option will
1823 lead to unwanted sideeffects were OS X applications when saving
1824 files to a temporary file starting with a dot first, then renaming
1825 the temp file to its final name, result in the saved file being
1826 invisible. The only thing this option is useful for is making
1827 files that start with a dot invisible on Mac OS 9. It's
1828 completely useless on Mac OS X, as both in Finder and in Terminal
1829 files starting with a dot are hidden anyway.</para>
1834 <term>network ids = <replaceable>BOOLEAN</replaceable> (default:
1835 <emphasis>yes</emphasis>) <type>(V)</type></term>
1838 <para>Whether the server support network ids. Setting this to
1839 <emphasis>no</emphasis> will result in the client not using ACL
1840 AFP functions.</para>
1845 <term>preexec close = <replaceable>BOOLEAN</replaceable> (default:
1846 <emphasis>no</emphasis>) <type>(V)</type></term>
1849 <para>A non-zero return code from preexec close the volume being
1850 immediately, preventing clients to mount/see the volume in
1856 <term>read only = <replaceable>BOOLEAN</replaceable> (default:
1857 <emphasis>no</emphasis>) <type>(V)</type></term>
1860 <para>Specifies the share as being read only for all users.
1861 Overwrites <option>ea = auto</option> with <option>ea =
1862 none</option></para>
1867 <term>root preexec close= <replaceable>BOOLEAN</replaceable>
1868 (default: <emphasis>no</emphasis>) <type>(V)</type></term>
1871 <para>A non-zero return code from root_preexec closes the volume
1872 immediately, preventing clients to mount/see the volume in
1878 <term>search db = <replaceable>BOOLEAN</replaceable> (default:
1879 <emphasis>no</emphasis>) <type>(V)</type></term>
1882 <para>Use fast CNID database namesearch instead of slow recursive
1883 filesystem search. Relies on a consistent CNID database, ie Samba
1884 or local filesystem access lead to inaccurate or wrong results.
1885 Works only for "dbd" CNID db volumes.</para>
1890 <term>stat vol = <replaceable>BOOLEAN</replaceable> (default:
1891 <emphasis>yes</emphasis>) <type>(V)</type></term>
1894 <para>Whether to stat volume path when enumerating volumes list,
1895 useful for automounting or volumes created by a preexec
1901 <term>time machine = <replaceable>BOOLEAN</replaceable> (default:
1902 <emphasis>no</emphasis>) <type>(V)</type></term>
1905 <para>Whether to enable Time Machine support for this
1911 <term>unix priv = <replaceable>BOOLEAN</replaceable> (default:
1912 <emphasis>yes</emphasis>) <type>(V)</type></term>
1915 <para>Whether to use AFP3 UNIX privileges. This should be set for
1916 OS X clients. See also: <option>file perm</option>,
1917 <option>directory perm</option> and <option>umask</option>.</para>
1925 <title>CNID backends</title>
1927 <para>The AFP protocol mostly refers to files and directories by ID and
1928 not by name. Netatalk needs a way to store these ID's in a persistent way,
1929 to achieve this several different CNID backends are available. The CNID
1930 Databases are by default located in the
1931 <filename>@localstatedir@/netatalk/CNID/(volumename)/.AppleDB/</filename>
1939 <para>"Concurrent database", backend is based on Oracle Berkley DB.
1940 With this backend several <command>afpd</command> daemons access the
1941 CNID database directly. Berkeley DB locking is used to synchronize
1942 access, if more than one <command>afpd</command> process is active
1943 for a volume. The drawback is, that the crash of a single
1944 <command>afpd</command> process might corrupt the database.</para>
1952 <para>Access to the CNID database is restricted to the
1953 <command>cnid_metad</command> daemon process.
1954 <command>afpd</command> processes communicate with the daemon for
1955 database reads and updates. If built with Berkeley DB transactions
1956 the probability for database corruption is practically zero, but
1957 performance can be slower than with <option>cdb</option></para>
1965 <para>This backend is an exception, in terms of ID persistency. ID's
1966 are only valid for the current session. This is basically what
1967 <command>afpd</command> did in the 1.5 (and 1.6) versions. This
1968 backend is still available, as it is useful for e.g. sharing cdroms.
1969 Starting with Netatalk 3.0, it becomes the <emphasis>read only
1970 mode</emphasis> automatically.</para>
1972 <para><emphasis role="bold">Warning</emphasis>: It is
1973 <emphasis>NOT</emphasis> recommended to use this backend for volumes
1974 anymore, as <command>afpd</command> now relies heavily on a
1975 persistent ID database. Aliases will likely not work and filename
1976 mangling is not supported.</para>
1981 <para>Even though <command>./configure --help</command> might show that
1982 there are other CNID backends available, be warned those are likely broken
1983 or mainly used for testing. Don't use them unless you know what you're
1984 doing, they may be removed without further notice from future
1989 <title>Charset options</title>
1991 <para>With OS X Apple introduced the AFP3 protocol. One of the most
1992 important changes was that AFP3 uses unicode names encoded as UTF-8
1993 decomposed. Previous AFP/OS versions used codepages, like MacRoman,
1994 MacCentralEurope, etc.</para>
1996 <para><command>afpd</command> needs a way to preserve extended Macintosh
1997 characters, or characters illegal in unix filenames, when saving files on
1998 a unix filesystem. Earlier versions used the the so called CAP encoding.
1999 An extended character (>0x7F) would be converted to a :xx sequence,
2000 e.g. the Apple Logo (MacRoman: 0xF0) was saved as <literal>:f0</literal>.
2001 Some special characters will be converted as to :xx notation as well.
2002 '<keycode>/</keycode>' will be encoded to <literal>:2f</literal>, if
2003 <option>usedots</option> is not specified, a leading dot
2004 '<keycode>.</keycode>' will be encoded as <literal>:2e</literal>.</para>
2006 <para>This version now uses UTF-8 as the default encoding for names.
2007 '<keycode>/</keycode>' will be converted to '<keycode>:</keycode>'.</para>
2009 <para>The <option>vol charset</option> option will allow you to select
2010 another volume encoding. E.g. for western users another useful setting
2011 could be vol charset ISO-8859-15. <command>afpd</command> will accept any
2013 <refentrytitle><command>iconv</command></refentrytitle>
2015 <manvolnum>1</manvolnum>
2016 </citerefentry> provided charset. If a character cannot be converted
2017 from the <option>mac charset</option> to the selected <option>vol
2018 charset</option>, afpd will save it as a CAP encoded character. For AFP3
2019 clients, <command>afpd</command> will convert the UTF-8<indexterm>
2020 <primary>UTF8</primary>
2022 <secondary>afpd's vol charset setting</secondary>
2023 </indexterm><indexterm>
2024 <primary>UTF8-MAC</primary>
2026 <secondary>afpd's vol charset setting</secondary>
2027 </indexterm><indexterm>
2028 <primary>ISO-8859-15</primary>
2030 <secondary>afpd's vol charset setting</secondary>
2031 </indexterm><indexterm>
2032 <primary>ISO-8859-1</primary>
2034 <secondary>afpd's vol charset setting</secondary>
2035 </indexterm> character to <option>mac charset</option> first. If this
2036 conversion fails, you'll receive a -50 error on the mac.</para>
2038 <para><emphasis>Note</emphasis>: Whenever you can, please stick with the
2039 default UTF-8 volume format.</para>
2043 <title>SEE ALSO</title>
2045 <para><citerefentry>
2046 <refentrytitle>afpd</refentrytitle>
2048 <manvolnum>8</manvolnum>
2049 </citerefentry>, <citerefentry>
2050 <refentrytitle>afppasswd</refentrytitle>
2052 <manvolnum>5</manvolnum>
2053 </citerefentry>, <citerefentry>
2054 <refentrytitle>afp_signature.conf</refentrytitle>
2056 <manvolnum>5</manvolnum>
2057 </citerefentry>, <citerefentry>
2058 <refentrytitle>extmap.conf</refentrytitle>
2060 <manvolnum>5</manvolnum>
2061 </citerefentry>, <citerefentry>
2062 <refentrytitle>cnid_metad</refentrytitle>
2064 <manvolnum>8</manvolnum>
2065 </citerefentry></para>