Post #2421362

@dmark@hachyderm.io @smallsco@oldbytes.space @nikdoof@social.doofnet.uk - I wonder if it might help newbies to have netatalk write a "note" log event to the effect of "Reading configuration file: /path/to/afp.conf", or perhaps logging a "warn" event if the config file is in a default unaltered state. The first thing I did was run "journalctl -f" to determine what netatalk was doing. I imagine others might be so inclined to tail -f /var/log/messages (or /syslog) — whatever their OS'es default log path is. OR ... make the default config file inoperable (comment everything out) until the user makes definitive changes to define a share. A blank config / commented config should cause netatalk not to run.