amuled forks to background before checking the validity of the config file.
So, in a scenario where one doesn't have EC enabled, amuled -f would happily start up, check for another running instance, fork to background and then silently exit.
Combining that with the fact that the config file usually gets lost after a system crash.. Every time I start up amuled, I have to check with top that the bloody thing actually stays running.
