04-04-2012
Yes. We have contract with HP....Can u let me know the procedure to that. I m helpless...
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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. IP Networking
Hello friends I'm running Redhat 9.0 with linux kernel 2.4.20-8 & have iptables version 1.2.7a & encountering a problem that I narrate down.
I need to apply patch to my iptable and netfilter for connection tracking and load balancing that are available in patch-o-matic distribution by netfilter.... (0 Replies)
Discussion started by: Rakesh Ranjan
0 Replies
3. Linux
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
4. Linux
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
5. UNIX for Advanced & Expert Users
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
6. Red Hat
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
7. Solaris
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
8. UNIX for Advanced & Expert Users
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
9. Solaris
Hi Guys,
I am doing L1 Level support for Solaris Platform. Eg. User Management, File system , Print management and Job monitoring.
I recently completer my IBM Aix 7 Administration certification. Issue is that my manager is asking me do full time unix / linux patch management work for new... (5 Replies)
Discussion started by: Nats
5 Replies
10. What is on Your Mind?
Original post from this thread on browser caching.
To add to this, it is an effective security measure to clear absolutely all cached data (cookies, web content, ....) when closing the browser - i.e. in case of a shutdown. It takes a bit of work to re-login to all the sites but websites will not... (7 Replies)
Discussion started by: bakunin
7 Replies
LEARN ABOUT BSD
shape_patch
SHAPE_PATCH(1) General Commands Manual SHAPE_PATCH(1)
NAME
shape_patch - shapeTools RMS generate patch file
SYNOPSIS
shape patch OLDRELEASE=<name1> NEWRELEASE=<name2> [PATCHFILE=<filename>]
DESCRIPTION
Shape patch generates a patch file for updating $(OLDRELEASE) to $(NEWRELEASE). Both releases are identified by release names associated
with the macros OLD-/NEWRELEASE on the command line. Valid release names are those generated by any of the shape_RMS (pre-)release building
procedures (see shape_releas(1)). Performing 'vl -all' with the release identification file as argument usually gives a good overview of
existing release names. Patch generation happens recursively over all subsystems being part of the current node. Hence, triggering shape
patch from the top node of the central source repository creates a patch file for the whole system.
The output of shape patch is stored in a file named <name1>+2+<name2>.pat. When the PATCHFILE macro is set on the command line, $(PATCH-
FILE) is taken as output file name instead. Defining PATCHFILE=- on the command line causes the patch to be written to standard output.
Note: For patches invoking multiple subsystems, $(PATCHFILE) should be set to an absolute pathname. If not, the patch generation procedure
will leave an equally named patch file for each visited subsystem.
The patch is constructed using the vdiff(1) command and can be applied to any installation of $(OLDRELEASE) by invoking patch(1).
INCONVENIENCES
On System V machines, the generated patch file name will almost certainly exceed the 14 characters filename length limit.
SEE ALSO
shape_releas(1), vdiff(1), patch(1)
FILES
<name1>+2+<name2>.pat
9.9.119 SHAPE_PATCH(1)