if read multi times when waiting for a slow client, then bytes is much shorter than datalen
so it could incorrectly terminate the string and data could be lost

* commit '9d9feb64':
  make the tzfile header check look for "TZif" instead of "TZif2"

ref: commit ce96d95c

...rather than `storage`.

ref: commit ce96d95c

FS-5992 #resolve

* commit 'a159b587':
  fix missing "/" in path
  add support for cache directory make configs use specific directory variables instead of just base_dir so that one configuration can be used for fhs and legacy installations

In `sofia status gateway ...` let's show the uptime in seconds rather
than in microseconds.  We'll output the uptime in microseconds in
`xmlstatus` and we'll label it as such.

The 'UP' status indicates a gateway is online as determined by
registration and/or SIP OPTIONS pinging.

The time the gateway has been in the 'UP' status is recorded,
and can be monitored using 'sofia status' and 'sofia xmlstatus'.

This can be used to detect and graph when there are outages.

ref: FS-6772
Reviewed-by: Travis Cross <tc@traviscross.com>

GCC doesn't like when variables that are set but never used.

do not use this unless you understand what you are doing and you want to take the risk,
you are warnned

What if the hash were destroyed by one thread holding the lock while
another thread was waiting for the lock?  The waiting thread would
have already checked that the hash was non-null and would proceed on
that assumption after acquiring the lock.

With this commit we check only after acquiring the lock.

ref: FS-6783
ref: FS-6775