Sponsored Content
Operating Systems Solaris Patch management (Solaris, AIX , Linux ) Post 302849137 by Peasant on Saturday 31st of August 2013 01:36:14 AM
Old 08-31-2013
Well for patching, first thing you learn is backup then you learn repositories (IPS).
Having local repositories is a major advantage.

In Solaris 11, if you do major patching the pkg will patch the inactive boot environment then it will be active after next reboot (utilizing zfs clone ability on root zpool).

That helps you, since if things go berserk, you can always reboot the host and revert to old environment.

On HPUX, the tool for patching is swinstall and for backup/repositories it's Ignite.

Great help here is HPSIM tool with SWA (Software assistant), which generates reports what to patch, connecting to HP site and your HP machines.

For linux, for major kernel patches, you will have your last couple of kernels to boot from if things go wrong. For backup i use tar/gzip (read full drive backup for your distribution).

And the final piece of advice (not OS related) is to have test environments to try patching first.
Nothing can substitute that.

Hope that helps
Regards
Peasant.
These 2 Users Gave Thanks to Peasant For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

linux patch management tool

I have a suse linux 9(SLES 9) I have configured "YOU" (yast online update) and it all working fine, synchronising on a daily base with http://sdb.suse.de/download but I would like to know if they is a tools or scripts that inform you of any patches that has not been applied and notify you via... (0 Replies)
Discussion started by: hassan1
0 Replies

2. Linux

Linux Patch Management

Does anyone know who to centrally manage the distribution and application of patches to multiple Linux platforms ? Is there software for this ? (0 Replies)
Discussion started by: jimthompson
0 Replies

3. Linux

Apache in enterprise, patch management

I was wondering how everyone else manages patching/upgrades for apache. Latest doesnt mean greatest, we typically dont install the newest patches for our OS's. We typically run 3-6 months behind, to let fixes get fixed before installing them. Does anyone here have a written detailed plan... (0 Replies)
Discussion started by: Ikon
0 Replies

4. UNIX for Advanced & Expert Users

Patch Management over mixed unix platforms

Does anyone know of any tools that manage the rollout of patches across multiple types of Unix platform ( eg Solaris, Aix etc ). I am looking for something that does a similiar job to SMS or WSUS in the Windows world (3 Replies)
Discussion started by: jimthompson
3 Replies

5. Red Hat

Patch management dilemma

I've inherited about 10 RHEL 3 boxes that are located in Europe behind a corporate firewall with no access to rhn.redhat.com I've been tasked with patching all of these systems but I ask, Does redhat issue patch bundles? In AIX, there are maintenance levels and Sun has patch clusters available... (4 Replies)
Discussion started by: Steelysteel
4 Replies

6. Solaris

Help needed regarding Solaris 10 patch Management

Hello Friends.. I have not tried anything related to Solaris patch and wish to learn more about it. I just wanted to try the patchadd and patchrm commands and how they work, just for educational purpose. I tried to download Solaris 10 patches, it asked me to register at sunsolve.com and i... (5 Replies)
Discussion started by: saagar
5 Replies

7. UNIX for Advanced & Expert Users

Multi-platform Centralized Patch Management

We have a mix of AIX, HP-UX, Linux (RHEL and SLES), and Solaris in our environment. Currently we have seperate patch management systems for each platform (NIM, SD, Spacewalk, etc), but have started looking for a centralized patch management solution that would work for most, if not all, of our... (0 Replies)
Discussion started by: kknigga
0 Replies

8. HP-UX

Patch Management

HI all, As per the audit policy, patch has to be apply periodically, but in my scenerio, it has been applied lastly in the year 2010. Using HP UX 11.11, 11.21 and 11.31 I would like to know, how to identify the patches which are need to update, what will be the procedure to update, how to... (5 Replies)
Discussion started by: selvaforum
5 Replies

9. Cybersecurity

ID Management Security guideline for Linux, AIX, SunOS and HP UX

I'm searching for COMPREHENSIVE ID management security guideline to manage user administration in my current job. I couldn't find it online or the books that could help. What I need to know: User security directories and how to use it. How user should be managed. How the standard user... (0 Replies)
Discussion started by: blinkingdan
0 Replies
SPLITDIFF(1)							     Man pages							      SPLITDIFF(1)

NAME
splitdiff - separate out incremental patches SYNOPSIS
splitdiff [-a] [-d] [-p n] [file] splitdiff {[--help] | [--version]} DESCRIPTION
If you have a patch file composed of several incremental patches, you can use splitdiff to separate them out. You may want to do this in preparation for re-combining them with combinediff(1). The effect of running splitdiff is to separate its input into a set of output files, with no output file patching the same file more than once. OPTIONS
-a Split out every single file-level patch. -d Create file names such as a_b.c for a patch that modifies a/b.c. -p n Strip the first n components of the pathname to aid comparisons. --help Display a short usage message. --version Display the version number of splitdiff. SEE ALSO
combinediff(1), lsdiff(1) AUTHOR
Tim Waugh <twaugh@redhat.com> Package maintainer patchutils 21 Oct 2003 SPLITDIFF(1)
All times are GMT -4. The time now is 05:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy