04-13-2006
Pach Installation Problems
HI: thanks for your help
Im follow the steps describe on the link
http://docs.hp.com/en/B2355-90772/ch06s01.html and have a diffetrent types of error messages and warning messages describes below:
on the step two
sh: PH* not found
on step three
*session started for user "root@test"
*Beginning selection
Warning "test / var/opt/ignite/Patches "Thre no other sessions in
progress on this host that may affect the results on the
Disk Space Anaslysis calculation.
* "test: /var/opt/ignite/Patches": This target does not exist
and will be created.
ERROR There is currently no depot software on host "test" at
location "/etc/conf/PH*.depot"
*Some connection failed for "test:/etc/conf/PH*.depot"
Warning More information may be found in the daemon log file on this
target (default location is test" /var/adm/sw/swagentd.log).
* Selection had errors.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Can someone tell me how to get the installation date of a patch? I've done a showrev which I assume tells me if the patch cluster has been installed. It shows...SunOS 5.8 Generic 108528-23 June 2003. I'm assuming June 2003 is the patch release date. Is that right? How can I determine the... (1 Reply)
Discussion started by: kiloflash
1 Replies
2. Post Here to Contact Site Administrators and Moderators
I am having trouble installing some HPUX patches on my 11.00. I am a novice at this so bear with me. I do not understand how to install depots.
Now I'm trying to patch my system so I can get the Oracle client installed.
Oracle says I need these two patches: PHSS_21950, QPK_11.00.64
I go to:... (0 Replies)
Discussion started by: RAFA
0 Replies
3. HP-UX
HI: Thanks for your help
Im follow the steps describe on the link http://docs.hp.com/en/B2355-90772/ch06s01.html and have a diffetrent types of error messages and warning messages describes below:
on the step two
sh: PH* not found
on step three
*session started for user "root@test"... (0 Replies)
Discussion started by: RAFA
0 Replies
4. Solaris
Hi,
When we install patch on solaris box, if the server gets rebooted, do we need remove the patch and install? Or can we just re install? Please advise. (2 Replies)
Discussion started by: mokkan
2 Replies
5. Solaris
Hey hi all,
I just recently encountered these question regarding patch installation, the scenario is like these that i have three patches a,b,c and each of them require a server reboot.And I don't have to reboot the server three times..i can reboot it only once.. so what should i do ?
Mine... (1 Reply)
Discussion started by: sahil_shine
1 Replies
6. Solaris
Hi All,
I am new to Solaris. I have to install some latest patches on my SPARC Machine running Solaris 10. I have installed the required patches.
Please guide me through the rest of the process. Please include even minute details so that I don't face any problems while doing this activity.
... (12 Replies)
Discussion started by: kamaldeep1986
12 Replies
7. Red Hat
Dear All,
I have some 6 RedHat Servers ( 5.4 ) tikanga connected to the Intranet.
Some are Database Servers and application servers.
For the past 1.5 years , we have not installed any patches..
Is there any way to find out , whether these systems needs patches
and where to... (5 Replies)
Discussion started by: jegaraman
5 Replies
8. Solaris
Can any one let me know the complete steps to install patch on a production server like Sun Fire V440. (7 Replies)
Discussion started by: chetansingh23
7 Replies
9. Solaris
Hello,
I'm very new to this forum and solaris -
I have solaris 5.10 installed on my machine (x86) and when I did a prerequisite check for Oracle Database 11g R2, it was showing the following patches are missing -
OS Patch:137104-02
OS Patch:120754-06
OS Patch:119961-05
OS Patch:119964-14... (3 Replies)
Discussion started by: dsreedharan
3 Replies
10. Linux
Am new to Linux and this forum
From where can I download sysstatx86_64 and numactl-devel patches ?
Thanks!
:b: (1 Reply)
Discussion started by: dsreedharan
1 Replies
LEARN ABOUT OSX
svk::command::patch
SVK::Command::Patch(3) User Contributed Perl Documentation SVK::Command::Patch(3)
NAME
SVK::Command::Patch - Manage patches
SYNOPSIS
patch --ls [--list]
patch --cat [--view] PATCHNAME
patch --regen [--regenerate] PATCHNAME
patch --up [--update] PATCHNAME
patch --apply PATCHNAME [DEPOTPATH | PATH] [-- MERGEOPTIONS]
patch --rm [--delete] PATCHNAME
OPTIONS
--depot DEPOTNAME : operate on a depot other than the default one
DESCRIPTION
To create a patch, use "commit -P" or "smerge -P". To import a patch that's sent to you by someone else, just drop it into the "patch"
directory in your local svk repository. (That's usually "~/.svk/".)
svk patches are compatible with GNU patch. Extra svk-specific metadata is stored in an encoded chunk at the end of the file.
A patch name of "-" refers to the standard input and output.
INTRODUCTION
"svk patch" command can help out on the situation where you want to maintain your patchset to a given project. It is used under the
situation that you have no direct write access to remote repository, thus "svk push" cannot be used.
Suppose you mirror project "foo" to "//mirror/foo", create a local copy on "//local/foo", and check out to "~/dev/foo". After you've done
some work, you type:
svk commit -m "Add my new feature"
to commit changes from "~/dev/foo" to "//local/foo". If you have commit access to the upstream repository, you can submit your changes
directly like this:
svk push //local/foo
Sometimes, it's useful to send a patch, rather than submit changes directly, either because you don't have permission to commit to the
upstream repository or because you don't think your changes are ready to be committed.
To create a patch containing the differences between "//local/foo" and "//mirror/foo", use this command:
svk push -P Foo //local/foo
The "-P" flag tells svk that you want to create a patch rather than push the changes to the upstream repository. "-P" takes a single flag:
a patch name. It probably makes sense to name it after the feature implemented or bug fixed by the patch. Patch files you generate will be
created in the "patch" subdirectory of your local svk repository.
Over time, other developers will make changes to project "foo". From time to time, you may need to update your patch so that it still
applies cleanly.
First, make sure your local branch is up to date with any changes made upstream:
svk pull //local/foo
Next, update your patch so that it will apply cleanly to the newest version of the upstream repository:
svk patch --update Foo
Finally, regenerate your patch to include other changes you've made on your local branch since you created or last regenerated the patch:
svk patch --regen Foo
To get a list of all patches your svk knows about, run:
svk patch --list
To see the current version of a specific patch, run:
svk patch --view Foo
When you're done with a patch and don't want it hanging around anymore, run:
svk patch --delete Foo
To apply a patch to the repository that someone else has sent you, run:
svk patch --apply - < contributed_feature.patch
perl v5.10.0 2008-08-04 SVK::Command::Patch(3)