Basically revert commit 2064f3a4

In a new install, the "Date" value in dsts.ini will be 0/Never and thus would
never be rolled over (e.g. stats moved o csts.tab files).

Since getstats() now reliably detects any read failures, we shouldn't need
this as a work-around any more anyway - if the "date" field is 0, it just
means a new install and it's expected.

This should fix the issue reported by Basis where the ctrl/csts.tab and
node*/csts.tab files were never created in fresh install of v3.20. A work
around is to just set the Date field in the ctrl/dsts.ini file to the current
date (one time).