04-27-2016
The Best practice is to have the service processor/mainboard clock configured to use UTC. Depending on the hardware, that might be the only choice and the internal clock itself always run in UTC anyway.
There is no recommendation for the OS default timezone on the global or non global zones, just set the one that best suit your needs. Setting the timezone doesn't change what the clock contains but how its content is displayed.
9 More Discussions You Might Find Interesting
1. Solaris
Hi All ,
I try to install some packages in my global zone...
On the execution of the installion of the script it quits by saying the error
"Non global zone check failed"
Kindly help me in this regard
Thanks in advance,
jeganr (7 Replies)
Discussion started by: jegaraman
7 Replies
2. Solaris
Hi All
There is one folder in global zone I just want to share the same folder innon global zone. How can i do it?
pls send me script for this. (2 Replies)
Discussion started by: vijaysachin
2 Replies
3. Solaris
Hi,
A quick question: Can Solaris 10 local zones be moved to a Solaris 11 global zone and work well?
Thank you in advance! (5 Replies)
Discussion started by: aixlover
5 Replies
4. Solaris
I have configured three zones on Solaris-11. These are non-global zones contain Solaris-11 only. One of the zone is not booting up, complaining about IP address in use, while it is not.
root@tdpdmsp02 # zoneadm list -icv
ID NAME STATUS PATH BRAND IP... (3 Replies)
Discussion started by: solaris_1977
3 Replies
5. Solaris
Have 2 nics on physical system
net0 phys 1500 up --
net1 phys 1500 up --
1. I want to create a link aggregation with LACP enabled with above 2 nics
2. Create port-group(Like we create on ESXi) with VLAN-ID 2141
3. And assign this... (0 Replies)
Discussion started by: Shirishlnx
0 Replies
6. Solaris
Am new on solaris :):confused:
Have below questions for dedicated-cpu cores
1. For licensing I want to assign 2 core per non-global zone
one from each processor. Am using below but seems it's not supported .
root@solaris-test:~# psrinfo
0 on-line since 04/25/2016... (3 Replies)
Discussion started by: Shirishlnx
3 Replies
7. Programming
I can't compile anything, the final make error says "Command failed for target `install-recursive'", but I am not able to identify the root cause of that error, I tried with cc, gcc 4.5, also gcc 5.2, using make, using gmake 3.82, ld 5.11, gld 2.31... and I am totally stuck yet... please help, to... (4 Replies)
Discussion started by: sugar222
4 Replies
8. Solaris
I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially
Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
Discussion started by: amity
2 Replies
9. Solaris
Hi, hoping someone can help, its been a while since I used Solaris.
After creating a NGZ (non global zone), the NGZ can access the GZ (Global Zone) and the GZ can access the NGZ (using ssh, zlogin)
However, the NGZ cannot access any other netwqork devices, it can't even see the default router
... (2 Replies)
Discussion started by: GazinLincoln
2 Replies
LEARN ABOUT CENTOS
pmnewcontextzone
PMNEWCONTEXTZONE(3) Library Functions Manual PMNEWCONTEXTZONE(3)
NAME
pmNewContextZone - establish a reporting timezone based on a PMAPI context
C SYNOPSIS
#include <pcp/pmapi.h>
int pmNewContextZone(void);
cc ... -lpcp
DESCRIPTION
The current reporting timezone affects the timezone used by pmCtime(3) and pmLocaltime(3).
If the current PMAPI context is an archive, pmNewContextZone uses the timezone from the archive label record to set the current reporting
timezone.
If the current PMAPI context corresponds to a host source of metrics, pmNewContextZone executes a pmFetch(3) to retrieve the value for the
metric pmcd.timezone and uses that to set the current reporting timezone.
In both cases, pmNewContextZone returns a value to identify the current reporting timezone that may be used in a subsequent call to pmUse-
Zone(3) to restore this reporting timezone.
SEE ALSO
PMAPI(3), pmCtime(3), pmFetch(3), pmGetConfig(3), pmLocaltime(3), pmNewContext(3), pmNewZone(3), pmUseZone(3), pmWhichZone(3), pcp.conf(5),
pcp.env(5) and environ(5).
DIAGNOSTICS
PM_ERR_NOCONTEXT
the current PMAPI context is not valid
other a return value less than zero indicates a fatal error from a system call, most likely malloc(3C)
Performance Co-Pilot PCP PMNEWCONTEXTZONE(3)