Did someone summon me?
Here’s the long explanation: the Drobo FS and 5N are GLIBC-based devices. GLIBC is the library responsible for all timezone related functionality. In GLIBC systems, the timezone is specified through the TZ environment variable, and the default value comes from /etc/localtime. More information here: http://www.gnu.org/software/libc/manual/html_node/TZ-Variable.html
In other words: if you want a specific timezone, set the TZ environment variable. If TZ is undefined, then GLIBC will use whatever is in /etc/localtime.
The Drobo FS does not have an /etc/localtime. It exports the default timezone in the file /etc/init.d/rcS like this: “export TZ=‘PST +8PDT,M4.1.0/2,M10.5.0/2’”
The Drobo 5N does have an /etc/localtime. It exports the default timezone as “PST8PDT,M3.2.0,M11.1.0”.
With that being said, I strongly advise against messing with either /etc/init.d/rcS or /etc/localtime. Neither Drobo ships with the required binaries to change the timezone correctly (missing tzselect, timezone data, …).
The recommended way of dealing with this on Drobos is to explicitly set TZ whenever you need it, i.e., in the app’s service.sh script. It is not an ideal solution since you’ll need to set it in each app separately, but unfortunately this is the only reasonable choice until there’s a DroboApp with all the missing bits and pieces required to properly update the default timezone.