> I like this idea even more, along with a warning message about the problem. > In fact, I would even suggest that all that checking should be done before > the -d processing, before the fork. So even > daemons should fail with invalid settings. I once had an issue with my > daemon because I had a typo when changing my memcached.conf settings and even > though memcached started up and my monitoring > didn't notice anything wrong, it was not usable. > > Failing to start would have been a dead giveaway.
It'll now fail to start on some obvious limits... However not all things can be checked before the daemon spawns. We also can't protect against all typos. If you accidentally reset a configfile to the default, the default -m setting will probably start just fine, and might be 100x lower than your normal value. -Dormando
