- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Regarding cron and timezone
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
08-03-2006 07:49 AM
08-03-2006 07:49 AM
>cat /etc/TIMEZONE
TZ=CST0
export TZ
>echo $TZ
CST0
>date
Thu Aug 3 09:30:53 CST 2006
>date -u
Thu Aug 3 09:30:56 UTC 2006
Does CST0 means GMT time? Because date -u and date are giving the same time. If TZ=CST6CDT is set only does it mean central time?
2. Will the root id and other unix user id run under same timezone. In which timezone cron runs and how it is decided for each unix user id?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2006 07:59 AM
08-03-2006 07:59 AM
SolutionTZ=CST6CDT does conform to the standard definition of Central Time (US).
HP-UX adds a wrinkle in that the behavior of a given TZ can be modified by the contents of a textfile, /usr/lib/tztab. Have a look at this file and the tztab man page.
2. Yes, no, maybe. The default TZ is set by sourcing the the /etc/TIMEZONE but this can be overridden by defining an entry in the user's .profile (or for that matter defining TZ later). It's perfectly legal (and quite common) for a UNIX box to have users logged in from all over the planet -- each with a unique TZ setting.
By the way, a useful way to briefly define an environemt variable is this:
TZ=CST0
TZ=CST6CDT date
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2006 08:43 AM
08-03-2006 08:43 AM
Re: Regarding cron and timezone
1. nothing to add to Clay's response
2. If an account has a different timezone to the one that is set in the cron environment, the setting of the correct schedule time is subject to test - my Home Linux SuSE9.3 does not handle this gracefully for differences greater than 3 hours.
If no different timezones are in play (daylight saving is not considered as a different timezone in this context), cron and the user running a crontab command live in the same timezone.
mfG Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2006 12:47 AM
08-04-2006 12:47 AM
Re: Regarding cron and timezone
2. If TZ is set in the .profile, then when i login into the system with particular user id only it will executed. Then when i logoff from the system TZ system will go away. How does the unix system will store the TZ value and continue to run under the same timezone for the particular user id if logoff from the system?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2006 07:43 PM
09-06-2006 07:43 PM