Please make the next version of FTD so that is actually logs what it's doing (like every other daemon does). Now we have no clue if it's stalling because it cannot find the tracker,. has no diskspace, thetracker is corrupt etc etc. Preferably the output should listen to verbosity statements in the config file.
I know there is some output to daemon.log but this:
ftd: Caught exception waiting for message: [Unable to read message: Interrupted system call]
is really not very usefull
...and why is there an empty ftdaemon file in tmp that is not removed upon termination of the service?