04-03-2018
Take a look at this link :
Patches: HP-UX
HP offers a tool called HPSUM to analyze and patch all of their servers running any supported operating system (HPUX, RHEL ...)
It's a essentially a program, ran on the PC/laptop with ssh credentials and IP address of the server provided.
It will connect to machine and generate report for you, on which to act.
Most of the HPUX patching nowdays consist of applying bundles not individual patches.
Hope that helps
Regards
Peasant.
This User Gave Thanks to Peasant For This Post:
9 More Discussions You Might Find Interesting
1. 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
2. Shell Programming and Scripting
I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies
3. 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
4. Solaris
Hello to all, I have a quick question. I am learning Solaris, with Solaris 10 x86, and one of the chapters in the manual is about patching. So can I download free patches from the Sun page, I mean with out paying a license. Because It would be a great exercise to patch my installation of Solaris.... (1 Reply)
Discussion started by: piukeman
1 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. HP-UX
I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email.
original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies
7. 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
8. Shell Programming and Scripting
Hi all,
I have used a bash script which ultimately converts a string into date using date --date option:
DATE=$DATE" "$TIME" "`date +%Y` //concatenating 2 strings
TMRW_DATE=`date --date="$DATE" +"%s"` //applying date command on string and getting the unixtime
Please use code tags... (7 Replies)
Discussion started by: Rashu123
7 Replies
9. Shell Programming and Scripting
Hi All,
I have scenario where i have to compare two dates.
I thought of converting them to epoch seconds and do a numeric comparison.
This works fine on Linux systems.
$ date -d '2015/12/31' +%s
1451538000
$ date +%s
1449159121
But we don't have -d option in HPUX.
What would be... (5 Replies)
Discussion started by: veeresh_15
5 Replies
LEARN ABOUT DEBIAN
stg-import
STG-IMPORT(1) StGit Manual STG-IMPORT(1)
NAME
stg-import - Import a GNU diff file as a new patch
SYNOPSIS
stg import [options] [<file>|<url>]
DESCRIPTION
Create a new patch and apply the given GNU diff file (or the standard input). By default, the file name is used as the patch name but this
can be overridden with the --name option. The patch can either be a normal file with the description at the top or it can have standard
mail format, the Subject, From and Date headers being used for generating the patch information. The command can also read series and mbox
files.
If a patch does not apply cleanly, the failed diff is written to the .stgit-failed.patch file and an empty StGIT patch is added to the
stack.
The patch description has to be separated from the data with a --- line.
OPTIONS
-m, --mail
Import the patch from a standard e-mail file.
-M, --mbox
Import a series of patches from an mbox file.
-s, --series
Import a series of patches from a series file or a tar archive.
-u, --url
Import a patch from a URL.
-n NAME, --name NAME
Use NAME as the patch name.
-p N, --strip N
Remove N leading slashes from diff paths (default 1).
-t, --stripname
Strip numbering and extension from patch name.
-i, --ignore
Ignore the applied patches in the series.
--replace
Replace the unapplied patches in the series.
-b BASE, --base BASE
Use BASE instead of HEAD for file importing.
--reject
Leave the rejected hunks in corresponding *.rej files.
-e, --edit
Invoke an editor for the patch description.
-d, --showdiff
Show the patch content in the editor buffer.
-a "NAME <EMAIL>", --author "NAME <EMAIL>"
Use "NAME <EMAIL>" as the author details.
--authname AUTHNAME
Use AUTHNAME as the author name.
--authemail AUTHEMAIL
Use AUTHEMAIL as the author e-mail.
--authdate AUTHDATE
Use AUTHDATE as the author date.
--sign
Add a "Signed-off-by:" to the end of the patch.
--ack
Add an "Acked-by:" line to the end of the patch.
STGIT
Part of the StGit suite - see linkman:stg[1]
StGit 03/13/2012 STG-IMPORT(1)