On Solaris 9 with 112874-19 or later, the vxconfigd log time stamp is always in GMT format regardless of the time zone when /usr put on a separate partition and boot disk is encapsulated.
| Article:TECH201149 | | | Created: 2012-12-24 | | | Updated: 2012-12-24 | | | Article URL http://www.symantec.com/docs/TECH201149 |
Problem
On Solaris 9 with 112874-19 or later, the vxconfigd log time stamp is always in GMT format regardless of the time zone when /usr put on a separate partition and boot disk is encapsulated.
Solution
On systems where:
1. Solaris 9 patch 112874-19 (lgroup API lic Patch) or later is installed, and
2. the boot disk is encapsulated with the /usr file system on a separate file system,
vxconfigd will print its messages with time stamps in GMT time.
This is a result of changes in the Solaris localtime() library call introduced by Patch 112874-19. Prior to the changes, if the /usr/share/lib/zoneinfo/* files do not exist, localtime() will attempt to access these files to determine the time zone in subsequent calls. With the patch installed, localtime() will not retry these operations.
If the boot disk is encapsulated with the /usr file system on a separate file system, then during the early stages of the system boot process, when vxconfigd is first started, the /usr file system will not be mounted. Thus the /usr/share/lib/zoneinfo/* files will not be available. When vxconfigd issues the localtime() library call, it will not be able to determine the time zone. Therefore, vxconfigd will print its messages in GMT time, instead of the local time.
There are several workarounds:
1. Specify timezone as offset from GMT rather than as zoneinfo
2. Create a /usr/share/zoneinfo/XXX file on the root partition that will be hidden once the mount occurs, but will be used prior to that
3. Combine root and user
4. Restart vxconfigd after /usr is mounted
1. Solaris 9 patch 112874-19 (lgroup API lic Patch) or later is installed, and
2. the boot disk is encapsulated with the /usr file system on a separate file system,
vxconfigd will print its messages with time stamps in GMT time.
This is a result of changes in the Solaris localtime() library call introduced by Patch 112874-19. Prior to the changes, if the /usr/share/lib/zoneinfo/* files do not exist, localtime() will attempt to access these files to determine the time zone in subsequent calls. With the patch installed, localtime() will not retry these operations.
If the boot disk is encapsulated with the /usr file system on a separate file system, then during the early stages of the system boot process, when vxconfigd is first started, the /usr file system will not be mounted. Thus the /usr/share/lib/zoneinfo/* files will not be available. When vxconfigd issues the localtime() library call, it will not be able to determine the time zone. Therefore, vxconfigd will print its messages in GMT time, instead of the local time.
There are several workarounds:
1. Specify timezone as offset from GMT rather than as zoneinfo
2. Create a /usr/share/zoneinfo/XXX file on the root partition that will be hidden once the mount occurs, but will be used prior to that
3. Combine root and user
4. Restart vxconfigd after /usr is mounted
|
|
| Value | 340443 |
| Description | vxconfigd logs in GMT format, regardless of timezone, when /usr is a separate parition |
Legacy ID
276114
Article URL http://www.symantec.com/docs/TECH201149
Terms of use for this information are found in Legal Notices
Thank you.