06-05-2009
I can just imagine how irritating it must be to patch those servers, especially since they have not been patched for years.
Are you familiar with xVM Ops Center 2.1 by any chance? It's Sun new product which is great for patching and provisioning. It has an intelligent knowledge base and it makes the patching scalable and automated. You might want to take a look at it.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
quick and question for the unix expert here
i downloaded the lastest patch from sun.
i'm ready to patch my production server. should i just patch it as is or go in to init 1 or init S to do the patching.
someone told me that you can just patch the server in init 3 and some other... (2 Replies)
Discussion started by: xNYx
2 Replies
2. Solaris
Hi all,
I'm new to Solaris. How can i make sure that all my servers are patched to the same level. When i do a uname -a, i see different level. How can i make sure that they are having the same patches. Any expert to guide me through pls?
eg.
ServerA#uname -a
SunOS ServerA 5.10... (0 Replies)
Discussion started by: ahlude
0 Replies
3. Solaris
Hi Gurus
I wanted to patch two servers yesterday with the SUN provided patch_cluster for solaris 10
One server is had the same patchlevel before and after patching
SunOS svr10008 5.10 Generic_125100-10 sun4v sparc SUNW,Sun-Fire-T200
The other had after the patching a different patchlevel... (3 Replies)
Discussion started by: gnom
3 Replies
4. Solaris
I know the smpatch utility has the set-uid 0 bit on it, so I'm wondering what privileges does it take to use this tool? I don't have to be root do I? How can I let a normal account do maintenance?
Thanks in advance. (4 Replies)
Discussion started by: solarisx86
4 Replies
5. Solaris
Hi All,
I have a question ? Which all patches need to be applied in single user mode and which all not .Is there any rule all patches need to be applied in /var/tmp.Thanks in advance for answers.:) (1 Reply)
Discussion started by: rama krishna
1 Replies
6. Solaris
HI Friends....
kindly explain os mirror patching?in SVM and Vxvm.
:wall: (1 Reply)
Discussion started by: Rajesh_Apple
1 Replies
7. Solaris
what are prerequisites or precautions we take before we install a patch in a zone.what if zone fails to boot after patching.How to recover form this situation.?
Thanks in advance..:) (1 Reply)
Discussion started by: ravijanjanam12
1 Replies
8. Solaris
OK, finally managed to get root access to the machines.
Now running
# uname -a
SunOS unknown 5.8 Generic_108528-22 sun4u sparc SUNW,UltraAX-e2
# showrev -p
Patch: 112668-01 Obsoletes: Requires: Incompatibles: Packages: SUNWgzip
Patch: 109889-01 Obsoletes: 109353-04 Requires: ... (2 Replies)
Discussion started by: Norman Khine
2 Replies
9. Red Hat
hello,
I'm a Solaris admin and I was asked to patch some RHEL servers. I'm having trouble trying to figure out the RHEL java version. Can someone help me?
This what I do in Solaris
java -version
java version "1.5.0_34"
java(TM) 2 Runtime Envirement, Standard Edition (build 1.5.0_34-b03)... (5 Replies)
Discussion started by: bitlord
5 Replies
10. Solaris
Greetings everyone! I have the task of patching six ldoms and two control domains. I have never done this before and would like to know of any pitfalls or "gotchas" I may encounter. I have been looking online but have found very little about patching ldoms. Thank you all. (4 Replies)
Discussion started by: desertdenizen
4 Replies
LEARN ABOUT CENTOS
thin_dump
THIN_DUMP(8) System Manager's Manual THIN_DUMP(8)
NAME
thin_dump - dump thin provisioning metadata from device or file to standard output
SYNOPSIS
thin_dump [options] {device|file}
DESCRIPTION
thin_dump dumps binary thin provisioning metadata (optionally from alternate block; see option --metadata-snap) created by the device-map-
per thin provisioning target on a device or file to standard output for analysis or postprocessing in either XML or human readable format.
XML formated metadata can be fed into thin_restore (see thin_restore(8)) in order to put it back onto a metadata device (to process by the
device-mapper target) or file.
-f, --format {xml|human_readable}
Print output in XML or human readable format.
-r, --repair
Repair the metadata whilst dumping it.
-m, --metadata_snap [block#]
Dump metadata snapshot created by device-mapper thin provisioning target. If block is not provided, access the default metadata snapshot
created by the thin provisioning device-mapper target, else try the one at block#. See the thin provisioning target documentation on how
to create or release a metadata snapshot and retrieve the block number from the kernel.
-h, --help
Print help and exit.
-V, --version
Output version information and exit.
EXAMPLES
Dumps the thin provisioning metadata on logical volume /dev/vg/metadata to standard output in human readable format:
thin_dump -f human_redable /dev/vg/metadata
Dumps the thin provisioning metadata on logical volume /dev/vg/metadata to standard output in XML format:
thin_dump /dev/vg/metadata
Dumps the thin provisioning metadata snapshot on logical volume /dev/vg/metadata to standard output in human readable format (not process-
able by thin_restore(8) ):
thin_dump --format human_readable --metadata-snap /dev/vg/metadata
DIAGNOSTICS
thin_dump returns an exit code of 0 for success or 1 for error.
SEE ALSO
thin_check(8) thin_repair(8) thin_restore(8) thin_rmap(8) thin_metadata_size(8)
AUTHOR
Joe Thornber <ejt@redhat.com>
Heinz Mauelshagen <HeinzM@RedHat.com>
Red Hat, Inc. Thin Provisioning Tools THIN_DUMP(8)