Jeff,
Those lines were already commented out. It looks like the problem is in these
lines:
500 # Get amount and cap of memory locked by processes in each zone.
501 $kstat-update();
502 my $zh = $kstat-{caps};
503 foreach my $z (keys(%$zh)) {
504($lkd_use[$z], $lkd_cap[$z]) =
I have a couple of servers that are still running U1 but I'd still like to use
zonestat to get as much info as I can.
I get the following output when I run zonestat 1.4.1 with debug turned on:
root zonestat -l -N
/usr/sbin/prtconf
/bin/pagesize
/bin/echo 'pages_pp_maximum/D;segspt_minfree/D' |
Hi Gael,
I went through thinking about this situation almost a year ago and came to the
conclusion that the zone root filesystems have to be UFS so they can be
upgraded. I have turned on MPxIO to give me multipathing support for the zone
roots which are all setup on separate SAN LUNs. I can
Just a reminder that QuickIO is only supported in a global zone. It uses a
special device that can't be created in a non-global zone. It should be a
fairly moot issue anyway since QuickIO is only useful for Oracle 8i and lower
releases, none of which are still supported. QuickIO is still
Enda,
All of the zones were booted to milestone all when 119254-34 was applied. Since
the patch didn't require a reboot, I did it with all zones and global fully
operational.
Phil
This message posted from opensolaris.org
___
zones-discuss mailing
When is it necessary to patch whole root zones directly?
I was trying to make sure that I had all of my zones ready to be updated with
DST patch 122034-04 so I made sure to install patch utilities patch 119254-34
on all of the global zones. I never thought to install it on the whole root
zones
You can also remove a LOFS mounted filesystem from a running zone with no
problem. I do it all the time.
To do it, logon to the global zone and umount the filesystem with:
umount mount point in the non-global zone
Phil
This message posted from opensolaris.org
The blastwave.org Samba distribution doesn't have this issue: its shutdown
(/etc/init.d/cswsamba stop) uses the pid IDs for smbd, nmbd, and winbindd
stored in /opt/csw/var/locks/.
A quick FYI on using the blastwave distribution: If you are using sparse zones
and need to run Samba with winbind,
I have hit a problem with zones in relation to doing Solaris upgrades - I can’t
do them currently. I have expended considerable effort in trying to be
positioned to do upgrades but they do not work for me as currently implemented.
I’ll provide a summary of my situation and then make suggestions
If you are going to backup a zone using the NetBackup client from within the
zone and you want to get all the filesystems automatically, you have to do the
following NetBackup policy setup:
In the NetBackup policy:
1. Enable the Follow NFS option
2. Enable the Cross mount points option
3.
10 matches
Mail list logo
