-# Specify that the given loglevel should be applied
-# to log messages of the given logtype and that
-# these messages should be logged to the given file.
-# If the filename is ommited the loglevel applies to
-# messages passed to syslog.
-# Each logtype may have a loglevel applied to syslog
-# and a loglevel applied to a single file. Latter
-# -setuplog settings will override earlier ones of
-# the same logtype (file or syslog).
-# logtypes: Default, Core, Logger, CNID, AFPDaemon
-# loglevels: LOG_SEVERE, LOG_ERROR, LOG_WARN, LOG_NOTE,
-# LOG_INFO, LOG_DEBUG, LOG_DEBUG6, LOG_DEBUG7,
-# LOG_DEBUG8, LOG_DEBUG9, LOG_MAXDEBUG
-#
-# for example:
-# -setuplog "logger log_maxdebug /var/log/netatalk-logger.log"
-# -setuplog "afpdaemon log_maxdebug /var/log/netatalk-afp.log"
-# -unsetuplog "default level file"
-# -setuplog "default log_maxdebug"
+# Specify that any message of a loglevel up to the
+# given loglevel should be logged to the given file.
+# If the filename is ommited the loglevel applies to
+# messages passed to syslog.
+#
+# By default (no explicit -setuplog and no buildtime
+# configure flag --with-logfile) afpd logs to syslog
+# with a default logging setup equivalent to
+# "-setuplog default log_info".
+#
+# If build with --with-logfile[=somefile]
+# (default logfile /var/log/netatalk.log) afpd
+# defaults to a setup that is equivalent to
+# "-setuplog default log_info [netatalk.log|somefile]"
+#
+# logtypes: Default, AFPDaemon, Logger, UAMSDaemon
+# loglevels: LOG_SEVERE, LOG_ERROR, LOG_WARN,
+# LOG_NOTE, LOG_INFO, LOG_DEBUG,
+# LOG_DEBUG6, LOG_DEBUG7, LOG_DEBUG8,
+# LOG_DEBUG9, LOG_MAXDEBUG
+#
+# Example: Useful default config
+# -setuplog "default log_info /var/log/afpd.log"
+#
+# Debugging config
+# -setuplog "default log_maxdebug /var/log/afpd.log"
+#
+# -signature { user:<text> | auto }
+# Specify a server signature. This option is useful
+# while running multiple independent instances of
+# afpd on one machine (eg. in clustered environments,
+# to provide fault isolation etc.).
+# Default is "auto".
+# "auto" signature type allows afpd generating
+# signature and saving it to afp_signature.conf
+# automatically (based on random number).
+# "host" signature type switches back to "auto"
+# because it is obsoleted.
+# "user" signature type allows administrator to
+# set up a signature string manually.
+# Examples: three servers running on one machine:
+# first -signature user:USERS
+# second -signature user:USERS
+# third -signature user:ADMINS
+# First two servers will act as one logical AFP service.
+# If user logs in to first one and then connects to second
+# one, session will be automatically redirected to the first
+# one. But if client connects to first and then to third,
+# will be asked for password twice and will see resources of
+# both servers.
+# Traditional method of signature generation causes two
+# independent afpd instances to have the same signature and
+# thus cause clients to be redirected automatically to
+# server (s)he logged in first.
+# -k5service <service>
+# -k5realm <realm>
+# These are required if the server supports Kerberos 5
+# authentication
+#
+# Codepage Options:
+# -unixcodepage <CODEPAGE> Specifies the servers unix codepage,
+# e.g. "ISO-8859-15" or "UTF8".
+# This is used to convert strings to/from
+# the systems locale, e.g. for authenthication.
+# Defaults to LOCALE if your system supports it,
+# otherwise ASCII will be used.
+#
+# -maccodepage <CODEPAGE> Specifies the mac clients codepage,
+# e.g. "MAC_ROMAN".
+# This is used to convert strings to the
+# systems locale, e.g. for authenthication
+# and SIGUSR2 messaging. This will also be
+# the default for volumes maccharset.
+#
+# CNID related options:
+# -cnidserver ipaddress:port Specifies the IP address and port of
+# a cnid_metad server.
+#
+