inconsistent incorrect config file handling

if there's an incorrect parameter in the config file (like asdf=1), daemons print message in the commandline and stop.

if the problem is with userparameter or alias (for example, duplicate key), nothing is printed in the commandline, only in the logfile. what's worse, logfile only logs the warning but does not go through the normal shutdown sequence, thus no log entry about daemon being stopped.

any problems in the config file should be checked for and reported before writing to the logfile.

if current architecture prevents that from being easily done, we should print "stopping" message in the logfile, as that is not currently done and can be pretty confusing; logfile validation before attempting to start up can be split out in a separate issue.