Bug - Dashboard subscription says "US/Pacific" but runs in GMT

RT Users
1

We have noticed that although the subscription page says the local
timezone next to the time, the reports actually run based on GMT time.

Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source
and other randomness

2

We have noticed that although the subscription page says the local
timezone next to the time, the reports actually run based on GMT time.

I figured it out. On FreeBSD timezone data is stored in /usr/share/
timezones and has some different names. “US/Pacific” would actually
be “America/Log_Angeles”. This solved the problem.

Can we get RT to throw out a message if the timezone it’s given proves
not to resolve?

Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source
and other randomness

3

We have noticed that although the subscription page says the local
timezone next to the time, the reports actually run based on GMT time.

I figured it out. On FreeBSD timezone data is stored in /usr/share/
timezones and has some different names. “US/Pacific” would actually
be “America/Log_Angeles”. This solved the problem.

Can we get RT to throw out a message if the timezone it’s given proves
not to resolve?

I’d take a patch for that