09-18-2012
Typical steps to be followed while applying an application patch upgrade on linux
what are the typical steps used by system adminstrators while applying an application patch upgrade
10 More Discussions You Might Find Interesting
1. Solaris
The above was the result i obtained from my live upgrade, will i have to manually installed this downloaded patch or is it alright to leave it like that (1 Reply)
Discussion started by: seyiisq
1 Replies
2. Solaris
Hi,
As in the solaris material i know that the patch is added through the command "patchadd <patch no.>".
But i need to know, what are all the steps we have to follow while applying a patch in a production server. My friend says that we have to detach mirror before applying patch and not... (6 Replies)
Discussion started by: Sesha
6 Replies
3. Solaris
Solaris 10 10/09 (Update 8) Patch upgrade can be done in single user mode? any suggestions.. thanks (2 Replies)
Discussion started by: chandravadrevu
2 Replies
4. Solaris
Hi there,
Apologies if this question has been asked and answered already but I've not been able to find the thread.
Question: Is it possible to apply the Solaris 10 Recommended Patch Cluster to a whole root (non-global) zone locally? I.E. apply the patch cluster from the non-global in... (3 Replies)
Discussion started by: nm146332
3 Replies
5. UNIX and Linux Applications
Hello. I need upgrade memcached. This software is installed throuth yum. In official repositories isn`t newest version of memcached, but this one is vulnerable. So looks like I need built it from source, but I dont really want to install c libraries un compilers on system.
1.) So can I compile... (0 Replies)
Discussion started by: jabalv
0 Replies
6. Solaris
I'm trying to setup our jumpstart server to automatically apply the latest patch cluster during installs, but I'm running into an issue. Every time Jumpstart runs it has this error. Obviously it's processing the patch_order file, so I'm not sure what I'm missing.
... (0 Replies)
Discussion started by: christr
0 Replies
7. Solaris
Hello Guys,
I am a little confused about the first step in the live upgrade process. I will be glad if someone can clarify this for me.
The pre-live upgrade patch, when do you add this patch to the OS you want to upgrade?
1. before creating the new boot environment? or
2. after creating... (1 Reply)
Discussion started by: cjashu
1 Replies
8. Ubuntu
I have applied a patch using this command:
patch -p1 < (file)
then I did git commit -a.
Now I want to recompile the kernel for making this patch live.
Should I use
make oldconfig
or
make localmodconfig
After that,
make -j$(grep -c "processor" /proc/cpuinfo)
sudo make... (1 Reply)
Discussion started by: BHASKAR JUPUDI
1 Replies
9. Debian
The version of Samba in our billing server is 4.1.17-Debian.
I have been reminded by our management to implement the patch for Samba on this server.
However, I am not sure how to implement the patch. I have browsed some websites for the correct patch to implement for Samba 4.1.17, and the patch... (11 Replies)
Discussion started by: anaigini45
11 Replies
10. Solaris
Hi,
I have Solaris-10 x86 (running on HP hardware), with 12 non-global zones running on this. I have to install latest patch cluster/set on this server. This server is not under backup schedule, so before installing patch cluster, I want to keep a backup. In case of any issue (bad patch or... (4 Replies)
Discussion started by: solaris_1977
4 Replies
LEARN ABOUT DEBIAN
stg-refresh
STG-REFRESH(1) StGit Manual STG-REFRESH(1)
NAME
stg-refresh - Generate a new commit for the current patch
SYNOPSIS
stg refresh [options] [<files or dirs>]
DESCRIPTION
Include the latest work tree and index changes in the current patch. This command generates a new git commit object for the patch; the old
commit is no longer visible.
You may optionally list one or more files or directories relative to the current working directory; if you do, only matching files will be
updated.
Behind the scenes, stg refresh first creates a new temporary patch with your updates, and then merges that patch into the patch you asked
to have refreshed. If you asked to refresh a patch other than the topmost patch, there can be conflicts; in that case, the temporary patch
will be left for you to take care of, for example with stg squash.
The creation of the temporary patch is recorded in a separate entry in the patch stack log; this means that one undo step will undo the
merge between the other patch and the temp patch, and two undo steps will additionally get rid of the temp patch.
OPTIONS
-u, --update
Only update the current patch files.
-i, --index
Instead of setting the patch top to the current contents of the worktree, set it to the current contents of the index.
-p PATCH, --patch PATCH
Refresh (applied) PATCH instead of the top patch.
-e, --edit
Invoke an editor for the patch description.
-a NOTE, --annotate NOTE
Annotate the patch log entry.
-m MESSAGE, --message MESSAGE
Use MESSAGE instead of invoking the editor.
-f FILE, --file FILE
Use the contents of FILE instead of invoking the editor. (If FILE is "-", write to stdout.)
--sign
Add a "Signed-off-by:" to the end of the patch.
--ack
Add an "Acked-by:" line to the end of the patch.
--author "NAME <EMAIL>"
Set the author details.
--authname NAME
Set the author name.
--authemail EMAIL
Set the author email.
--authdate DATE
Set the author date.
STGIT
Part of the StGit suite - see linkman:stg[1]
StGit 03/13/2012 STG-REFRESH(1)