Comment 2 for bug 1687217

More subtle, apparently a disconnect between the mysql timezone and the rest of the system timezone is created when using the above proposed solution. ZoneMinder runs, and _most_ things work, but when reviewing event frames, they are stored under GMT timezone instead of the designated timezone, and then cannot be retrieved for playback with log messages like:

Can't open /usr/share/zoneminder/www/events/1/18/08/20/20/55/12/00001-capture.jpg: No such file or directory

.../1/18/20/20/55/... is the GMT time of the event, but the images are stored under .../1/18/20/16/55/... which corresponds to the America/New_York timezone set by the above procedure.

Anybody know the right way to set the mysql timezone to match? I've seen references to using the TZ environment variable, I've got that set to America/New_York, but my mysql still thinks it's on "system" time and that "system" time is GMT.