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
ovdb_init
OVDB_INIT(8) InterNetNews Documentation OVDB_INIT(8)
NAME
ovdb_init - Prepare ovdb database for use
SYNOPSYS
ovdb_init ["-u"|"-r"]
DESCRIPTION
This command must be run before any other process can access the overview database. It performs the following steps:
1. Creates the database environment, if necessary
2. If the database is idle (and if the "-u" option is not specified), it performs a normal recovery. The recovery will remove stale
locks, recreate the memory pool cache, and repair any damage caused by a system crash or improper shutdown.
3. If the "-u" option is specified, it performs any necessary upgrades to the database. See the UPGRADING section below.
4. Starts the DB housekeeping processes (ovdb_monitor) if they're not already running. (Unless the "-r" option is specified).
5. Starts the ovdb readserver (ovdb_server) processes if readserver in ovdb.conf is true, and if they are not already running. (Unless
the "-r" option is specified).
Returns exit status of 0 if all steps were completed successfully. In the event of an error, messages are written to syslog and/or stderr.
If a recovery was attempted but it failed, the database may be damaged beyond repair, requiring a rebuild with makehistory(8).
This command is normally invoked automatically by rc.news(8).
It is OK to run this command multiple times.
OPTIONS
"-r"
Perform recovery only. "ovdb_monitor" is not started.
"-u"
Perform any needed upgrades. Recovery is not attempted. "ovdb_monitor" is started if the upgrade succeeded.
UPGRADING
There are two situations in which the database will need to be upgraded:
o You upgrade the Berkeley DB library to a newer version, for example from 2.7.7 to 3.1.17. In this case, the Berkeley DB db->upgrade()
method is used.
o You upgrade ovdb to a newer major version; i.e., ovdb-1.0 to ovdb-2.0.
In both of these cases, the database is upgraded in-place; and the upgrade can not be undone. Do not interrupt the upgrade process once it
has started, because there is a risk of irrepairable corruption. The upgrade may take several minutes to complete. If an upgrade does get
interrupted, try running the upgrade again.
Here's an example procedure to upgrade a database created with Berkeley DB 2.7.7 to use Berkeley DB 3.1.17:
1. Build and install the Berkeley DB 3.1.17;
2. Run configure in the INN source tree and make sure it picks up the right Berkeley DB directory (e.g., /usr/local/BerkeleyDB.3.1);
3. Do a "make";
4. Shut down INN (e.g., with "rc.news stop") and be sure to kill all instances of nnrpd as well;
5. Do a "make update" to install the new binaries;
6. Run "ovdb_init -u" as the news user;
7. Start INN with "rc.news".
It is OK to specify "-u" even if no upgrades are needed.
HISTORY
Written by Heath Kehoe <hakehoe@avalon.net> for InterNetNews.
$Id: ovdb_init.pod 7851 2008-05-26 19:33:08Z iulius $
SEE ALSO
ovdb(5), makehistory(8)
INN 2.5.3 2009-05-21 OVDB_INIT(8)