HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: NTP and time zones
Operating System - Linux
1826291
Members
4412
Online
109692
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2007 07:52 AM
02-14-2007 07:52 AM
Greetings all,
I just had a discussion with a superior about the upcoming necessity to dhange our timezone data on an old Mandrake 8.2 Linux machine.
He claims that we don't have to because the machine clock is maintained by NTP.
I would think the time returned fro the time server is in universal time format which is then interpreted by the client's timezone settings ($TZ for UNIX, /etc/localtime for linux).
Can anyone confirm the process and/or point me to documentation that clearly explains it?
Thank you.
RayB
I just had a discussion with a superior about the upcoming necessity to dhange our timezone data on an old Mandrake 8.2 Linux machine.
He claims that we don't have to because the machine clock is maintained by NTP.
I would think the time returned fro the time server is in universal time format which is then interpreted by the client's timezone settings ($TZ for UNIX, /etc/localtime for linux).
Can anyone confirm the process and/or point me to documentation that clearly explains it?
Thank you.
RayB
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2007 07:59 AM
02-14-2007 07:59 AM
Solution
You are right. The NTP server provides the time in UTC, and your client timezone dictates when to enter and leave DST.
A good explanation about the whole process is here:
http://tldp.org/HOWTO/TimePrecision-HOWTO/
A good explanation about the whole process is here:
http://tldp.org/HOWTO/TimePrecision-HOWTO/
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2007 09:33 AM
02-14-2007 09:33 AM
Re: NTP and time zones
Hi Ray:
You are correct. Show your "superior" the following and see if it doesn't reinforce the notion of a timezone as a +- offset of time *from* universal (Greenwich) time:
# date
# TZ=UTC date
# TZ=EST5EDT date
# TZ=PST8PDT date
# TZ=CST-9:30CDT date
The above set the TZ variable only for the duration of the commandline.
The dates for Standard or Daylight Saving time transitions are coded in configuration files. In the United States, as you aware, the Spring transition will occur three weeks earlier than before and the Fall change a week later than previously. Once again, though, the actual server clock (and, of course the time returned by NTP from its sources) never changes --- only the +- delta value defined for the timezone.
Regards!
...JRF...
You are correct. Show your "superior" the following and see if it doesn't reinforce the notion of a timezone as a +- offset of time *from* universal (Greenwich) time:
# date
# TZ=UTC date
# TZ=EST5EDT date
# TZ=PST8PDT date
# TZ=CST-9:30CDT date
The above set the TZ variable only for the duration of the commandline.
The dates for Standard or Daylight Saving time transitions are coded in configuration files. In the United States, as you aware, the Spring transition will occur three weeks earlier than before and the Fall change a week later than previously. Once again, though, the actual server clock (and, of course the time returned by NTP from its sources) never changes --- only the +- delta value defined for the timezone.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2007 03:19 AM
02-15-2007 03:19 AM
Re: NTP and time zones
Thank you,
2 good responses!
Case closed.
2 good responses!
Case closed.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP