During the ISO build process from the Wizard, I selected US/Eastern as my time zone; however, the system time appears to be about 4 hours off.
We run an HTML file that pulls the system time and displays it in a webpage. The time is 4 hrs off from the system Bios which I verified to be the correct time.
Is there a way to verify that it really is applying the setting I chose on the ISO creation Wizard where I specified US/Eastern?
This is part of the reason I had another post looking for a way to use an NTP server to acquire the time.
If I can't this to work I'll try to get the website to get the time from somewhere else instead.
Thanks
[Solved] System Time
Forum rules
Porteus Kiosk section of the forum is unmaintained now. Its kept in a 'read only' mode for archival purposes.
Please use the kiosk contact page for directing your queries: https://porteus-kiosk.org/contact.html
Porteus Kiosk section of the forum is unmaintained now. Its kept in a 'read only' mode for archival purposes.
Please use the kiosk contact page for directing your queries: https://porteus-kiosk.org/contact.html
-
- Black ninja
- Posts: 51
- Joined: 21 Mar 2014, 14:02
- Distribution: porteus 3.7 kiosk
- Location: Chattanooga
[Solved] System Time
Last edited by rh102801 on 02 Apr 2014, 14:05, edited 1 time in total.
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: System Time
please check on this website:
http://www.uize.com/examples/digital-clock.html
as yesterday i have created 2 ISOs through our wizard: one with timezone set to 'Europe/Minsk' and one with 'Europe/Dublin' and there was 2 hrs difference between them so i assume it's working ok.
EDIT:\\
after some reading i think i have got it now
https://wiki.archlinux.org/index.php/time#Time_standard
your hardware clock (RTC/time in the BIOS) must be set to localtime and kiosk is expecting the UTC one. UTC is better as Daylight Saving Time will be adjusted automatically. to fix you hw clock please do as follows:
a) generate ISO with ssh component enabled and time set to your timezone (ie: Europe/Warsaw)
b) boot kiosk and login through ssh
c) set the time manually, ie:
c) run 'hwclock --systohc --utc' command to save current time to the RTC
d) after reboot everything should be ok
http://www.uize.com/examples/digital-clock.html
as yesterday i have created 2 ISOs through our wizard: one with timezone set to 'Europe/Minsk' and one with 'Europe/Dublin' and there was 2 hrs difference between them so i assume it's working ok.
EDIT:\\
after some reading i think i have got it now
https://wiki.archlinux.org/index.php/time#Time_standard
your hardware clock (RTC/time in the BIOS) must be set to localtime and kiosk is expecting the UTC one. UTC is better as Daylight Saving Time will be adjusted automatically. to fix you hw clock please do as follows:
a) generate ISO with ssh component enabled and time set to your timezone (ie: Europe/Warsaw)
b) boot kiosk and login through ssh
c) set the time manually, ie:
Code: Select all
date --set "5 Aug 2012 12:54"
d) after reboot everything should be ok
Please add [Solved] to your thread title if the solution was found.
-
- Black ninja
- Posts: 51
- Joined: 21 Mar 2014, 14:02
- Distribution: porteus 3.7 kiosk
- Location: Chattanooga
Re: [Solved] System Time
As always fanthom excellent instructions.
I had some trouble with the command to set the date and time. This is what I typed:
root@porteus:~# date --set "2 Apr 2014 09:02"
date: invalid date '2 Apr 2014 09:02'
Note: I also tried April instead of Apr (I am sure the answer is something simple)
I tried a few combinations and finally opted for just entering the time since the date seemed to be already correct
root@porteus:~# date +%T -s "09:07:00"
09:07:00
and then
root@porteus:~# hwclock --systohc --utc
root@porteus:~# reboot
Upon reboot everything was as it should.
Thank you so much, you rock.
I had some trouble with the command to set the date and time. This is what I typed:
root@porteus:~# date --set "2 Apr 2014 09:02"
date: invalid date '2 Apr 2014 09:02'
Note: I also tried April instead of Apr (I am sure the answer is something simple)
I tried a few combinations and finally opted for just entering the time since the date seemed to be already correct
root@porteus:~# date +%T -s "09:07:00"
09:07:00
and then
root@porteus:~# hwclock --systohc --utc
root@porteus:~# reboot
Upon reboot everything was as it should.
Thank you so much, you rock.