10 More Discussions You Might Find Interesting
1. Red Hat
I have a couple of questions regarding multipath.
If I do vgdisplay vg01, I see it is using 1 PV: /dev/dm-13
If I type multipath -ll I see dm-9, dm-10, dm-11, dm-12, but do not see dm-13. Is my vg01 multipathed? How can I actually know for sure?
Secondly, let's say this time vg01 says... (1 Reply)
Discussion started by: keelba
1 Replies
2. AIX
Guy's
I have script doing many steps as the below ...
#############
## step1# mount all Files system
mount all
## step2# Start the application
/app/appsh
#############
but some time mount points will not be mounted completely so that will give an error if the next step started... (1 Reply)
Discussion started by: Mr.AIX
1 Replies
3. Shell Programming and Scripting
I run the script with one parameter : myscript abc002
But I need my script to check the parameter in txt array first:
txt="abc001 abc002 abc004"
What's the best way to do it? I am using ksh.
#! /usr/bin/ksh
txt="abc001 abc002 abc004"
if ; then
echo " Your input is wrong,... (9 Replies)
Discussion started by: newoz
9 Replies
4. Solaris
Hi Gurus,
I am new to solaris patching.. while doing the patching do we need to have the root previligies and also need help while doing patching work if the server has veritas on it........
Thanks in advance.......... (10 Replies)
Discussion started by: samanth009
10 Replies
5. Solaris
Hi all
Ive got 12 odd sun servers, running solars 8, 9 and soon 10. Have to admit I havent patched for years. Infact the last time I did patch a load of servers, sun provided you will a small script which would review the current patch levels, create a xml file that you would use on sunsolve... (3 Replies)
Discussion started by: sbk1972
3 Replies
6. Solaris
Hi Folks,
I new to SunOs, mostly used to HP-UX and AIX way of patching. I'm trying to bring my two 420R test blades to the same patch level as my two prod ones. I've been reading a lot on how to patch SunOs but I'm still not sure how to achieve this. Both prod boxes says SunOs 5.8 Generic Patch... (2 Replies)
Discussion started by: supergumby
2 Replies
7. AIX
hi,
folks i have a challenging problem for you. i need to get the patching history, like what date the patch was applied and from which patch has it been upgarded to the current level.
i have tried everything and and all resources available but did not find a suitable answer. can some1 help,... (2 Replies)
Discussion started by: vinix
2 Replies
8. 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
9. Shell Programming and Scripting
thanks for your help, im gonna skip this one and try a different question. thanks for your help though. (2 Replies)
Discussion started by: bebop1111116
2 Replies
10. Shell Programming and Scripting
I have a unix script written in the korn shell. At the top of the script I call a script that exports the values of the variables I use in my script. I know that when you execute the script using ksh -x it shows you the script running. I was wondering if there was a way you could run the script... (2 Replies)
Discussion started by: lesstjm
2 Replies
APPLYPATCH(1p) User Contributed Perl Documentation APPLYPATCH(1p)
NAME
applypatch - apply 'makepatch' generated script to update a source tree
SYNOPSIS
applypatch [ options ] patch-kit
DESCRIPTION
Applypatch applies a patch kit as generated by the makepatch program. It performs the following actions:
o First, it will extensively verify that the patch kit is complete and did not get corrupted during transfer.
o Then it will apply some heuristics to verify that the directory in which the patch will be applied does indeed contain the expected
sources.
If a corruption or verification error is detected, applypatch exits without making changes.
o If the kit is okay, and the directory seems to be the right one: it creates new files and directories as necessary.
o Then it runs the patch program to apply the patch to the source files.
o Upon completion, obsolete files, directories and .orig files are removed, file modes of new files are set, and the timestamps of all
patched files are adjusted.
Applypatch arguments
Applypatch takes one argument, the name of the patch kit as generated by makepatch. If no name is specified, the patch kit is read from
standard input.
Applypatch options
Options are matched case insensitive, and may be abbreviated to uniqueness.
-directory dir
The name of the source directory to be patched.
-check
Perform the checks on the patch kit and patch directory, but do not make any changes.
-force
Force continuation of the patch process even when corruption or verification errors are detected. This is very dangerous!
-retain
Do not remove patch backup files (with extension ".orig") upon completion.
-patch cmd
The patch command to be used. Default is ""patch -p0 -N"". Additionally, a ""-s"" will be added unless option -verbose was specified.
-verbose
This option will cause applypatch and the patch program to emit verbose progress information.
-quiet
This option will cause applypatch and the patch program to emit no progress information, only error messages.
Environment variables
SIMPLE_BACKUP_SUFFIX
The suffix used by (some versions of?) patch to back up the originals of patched files. Upon completion, these files are removed by
applypatch unless the option -retain was specified. Default value if "".orig"".
SEE ALSO
makepatch(1), diff(1), patch(1), perl(1), rm(1).
AUTHOR AND CREDITS
This program is written by Johan Vromans <jvromans@squirrel.nl>.
See section AUTHOR AND CREDITS of the makepatch program for an extensive list of people that helped one way or another in the makepatch /
applypatch project.
COPYRIGHT AND DISCLAIMER
This program is Copyright 1992,1999,2006 by Squirrel Consultancy. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the terms of either: a) the GNU General Public License as
published by the Free Software Foundation; either version 1, or (at your option) any later version, or b) the "Artistic License" which
comes with Perl.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See either the GNU General Public License or the Artistic License for more details.
perl v5.10.0 2006-10-08 APPLYPATCH(1p)
