9 More Discussions You Might Find Interesting
1. Solaris
Hi,
I installed Solaris 10 recommended patch cluster (patch bundle of 400+ patches). After reboot global zone is fine, but a lot of services was in uninitialized state. I had to run /lib/svc/bin/restore_repository and then services came online.
Now I can't login to server with NIS account... (1 Reply)
Discussion started by: ron323232
1 Replies
2. Solaris
I have a question regarding installing recommended patch clusters via ZFS snapshots. Someone wrote a pretty good blog about it here:
Initial Program Load: Live Upgrade to install the recommended patch cluster on a ZFS snapshot
The person's article is similar to what I've done in the past. ... (0 Replies)
Discussion started by: christr
0 Replies
3. Solaris
I am working with a Sun StoredgeTek 6540 disk array connected to two Sun 490 servers. After taking one of the 490 nodes on the cluster down to single user mode I proceeded to install the latest cluster patch from Oracle. After the patch was completed the system rebooted, failed to rejoin the... (2 Replies)
Discussion started by: buggin
2 Replies
4. Solaris
I'm trying to setup our jumpstart server to automatically apply the latest patch cluster during installs, but I'm running into an issue. Every time Jumpstart runs it has this error. Obviously it's processing the patch_order file, so I'm not sure what I'm missing.
... (0 Replies)
Discussion started by: christr
0 Replies
5. Solaris
Hi Admins,
I came across an error while installing patch cluster on solaris.
# ./installcluster --s10cluster
ERROR: Another instance of an install script is already running for target
boot
environment '/'.
I did killed the related processes. Now there is no any process running from ps... (1 Reply)
Discussion started by: snchaudhari2
1 Replies
6. Solaris
Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC.
Am thinking how to migrate to sun cluster setup instead.
My plan as follows leave the existing vcs intact as a fallback plan.
Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies
7. Solaris
Hi there,
Apologies if this question has been asked and answered already but I've not been able to find the thread.
Question: Is it possible to apply the Solaris 10 Recommended Patch Cluster to a whole root (non-global) zone locally? I.E. apply the patch cluster from the non-global in... (3 Replies)
Discussion started by: nm146332
3 Replies
8. High Performance Computing
hi all,
can someone please share their process on how to kernel patch a red hat ent 4 with veritas cluster 5? it's compose of a primary and backup node. the resources are db, disk, nic.
it doesn't need to be detail, just give me the steps like:
login to the backup node and update the... (0 Replies)
Discussion started by: itik
0 Replies
9. Solaris
Does anyone have an alternate site to download J2SE Solaris Recommended Patch Cluster for Solaris 8. Sun does not let me download the patches unless I have a support contract. I do not. Our software is legal, but our support contract wore out. I need this patchset to avoid downloading 30... (6 Replies)
Discussion started by: hshapiro
6 Replies
STG-PUSH(1) StGit Manual STG-PUSH(1)
NAME
stg-push - Push one or more patches onto the stack
SYNOPSIS
stg push [options] [<patch1>] [<patch2>] [<patch3>..<patch4>]
DESCRIPTION
Push one or more patches (defaulting to the first unapplied one) onto the stack. The push operation allows patch reordering by commuting
them with the three-way merge algorithm. If there are conflicts while pushing a patch, those conflicts are written to the work tree, and
the command halts. Conflicts raised during the push operation have to be fixed and the git add --update command run (alternatively, you may
undo the conflicting push with stg undo).
The command also notifies when the patch becomes empty (fully merged upstream) or is modified (three-way merged) by the push operation.
OPTIONS
-a, --all
Push all the unapplied patches.
-n NUMBER, --number NUMBER
Push the specified number of patches.
--reverse
Push the patches in reverse order.
--set-tree
Push the patches, but don't perform a merge. Instead, the resulting tree will be identical to the tree that the patch previously
created.
This can be useful when splitting a patch by first popping the patch and creating a new patch with some of the changes. Pushing the
original patch with --set-tree will avoid conflicts and only the remaining changes will be in the patch.
-k, --keep
Keep the local changes.
-m, --merged
Check for patches merged upstream.
STGIT
Part of the StGit suite - see linkman:stg[1]
StGit 03/13/2012 STG-PUSH(1)