| | 1 | = Fixing Timezone = |
| | 2 | |
| | 3 | I had some trouble with the wrong timezone being used in SHR-unstable. It would use EST no matter what I did with /etc/timezone. This turned out to be a simple fix. Just add a section to /etc/frameworkd.conf for otimed. The one I used is below: |
| | 4 | |
| | 5 | {{{ |
| | 6 | [otimed] |
| | 7 | # a list of time/zone sources to use or NONE |
| | 8 | timesources = GPS,NTP |
| | 9 | zonesources = NONE |
| | 10 | }}} |
| | 11 | |
| | 12 | Next, restart frameworkd with '''/etc/init.d/frameworkd restart'''. Note that your /etc/timezone may have been overwritten, so you need to set it back to the correct timezone. |
| | 13 | |
| | 14 | Timezones are in /usr/share/zoneinfo/ and can be copied over to /etc/localtime or /etc/timezone as needed. You can also link /etc/localtime or /etc/timezone to the appropriate timezone in /usr/share/zoneinfo/. Note that if you had linked to a timezone in /usr/share/zoneinfo/ when the timezone was overwritten, you will need to fix the file in /usr/share/zoneinfo/. You can use '''opkg search /usr/share/zoneinfo/''whatever/file''''' to find out which package contains it, and then '''opkg install -force-reinstall ''pkgname''''' to reinstall it. |
| | 15 | |
| | 16 | After this, you can run '''date''' to see what timezone the system is using. |
