Difference between revisions of "Timezone in RoR"
From Kolmisoft Wiki
Jump to navigationJump to search
| (2 intermediate revisions by one other user not shown) | |||
| Line 29: | Line 29: | ||
Next step, change hardware clock time to your localtime: | Next step, change hardware clock time to your localtime: | ||
hwclock -- | hwclock --systohc | ||
Check hardware clock time by running: | Check hardware clock time by running: | ||
| Line 35: | Line 35: | ||
hwclock --show | hwclock --show | ||
Then restart asterisk, if this doesn't help, restart your server. | Then '''restart asterisk''', if this doesn't help, restart your server. | ||
| Line 41: | Line 41: | ||
= See also = | = See also = | ||
* [[Active Calls do not start from 00:00:00]] | * [[Active Calls do not start from 00:00:00]] | ||
* [[Timezones]] | |||
Latest revision as of 16:01, 9 September 2013
If time is not displayed correctly in GUI and date command in SSH shows correct time, then:
- In file /home/mor/config/environment.rb write:
ENV['TZ'] = 'Europe/Vilnius'
Off course change timezone value to correct one.
- Restart Apache
Correct format is:
ENV['TZ'] = 'Continent/Capital'
Check time by entering
date
into console. You'll see your localtime, if you still see new calls with old time, then you have to restart asterisk (How to restart Asterisk server)
Available timezones could be found in /usr/share/zoneinfo
You have to choose correct timezone file and copy it on top of /etc/localtime file.
Example if your server is in Dublin , Europe:
cp /usr/share/zoneinfo/Europe/Dublin /etc/localtime
Next step, change hardware clock time to your localtime:
hwclock --systohc
Check hardware clock time by running:
hwclock --show
Then restart asterisk, if this doesn't help, restart your server.
