8 More Discussions You Might Find Interesting
1. Linux
Hi everyone,
I am trying to prevent the ehci_hcd kernel module to load at boot time.
Here's what I've tried so far:
1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here):
2) Blacklisted the module by adding the following string to
3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
2. Solaris
Hi Guys,
I am getting into patching activity now a days.
I had already done kernel upgrade through LU.
My doubt is if i had to install 3 patches to get my system to current available patch level, can i directly patch one by one on an inactive LU and once done i can activate it later on
or... (3 Replies)
Discussion started by: Rockyc3400
3 Replies
3. Hardware
Hi,
I would like to ask related to video graphics driver specifically the AMD (radeon HD 7000 series) or had someone with the same experience or problem that im currently experiencing and willing to share some info. I understand that the kernel is self contain it will not affect the installed... (3 Replies)
Discussion started by: jao_madn
3 Replies
4. Red Hat
Hello, everyone.
I am using Fedora 15, and want to upgrade to version 16. I follow the official link Upgrading Fedora using yum - FedoraProject to upgrade my OS by the following command:
yum update kernel* --releasever=16
yum groupupdate Base --releasever=16
reboot
After reboot, OS... (2 Replies)
Discussion started by: 915086731
2 Replies
5. Solaris
Hi gurus
Could anybody tell me which file is read by kernel to set its default system kernal parameters values in solaris. Here I am not taking about /etc/system file which is used to load kernal modules or to change any default system kernal parameter value
Is it /dev/kmem file or something... (1 Reply)
Discussion started by: girish.batra
1 Replies
6. SuSE
Hi All,
Is there a max number of slabs that can be used per kernel module? I'm having a tough time finding out that kind of information, but the array 'node_zonelists' (mmzone.h) has a size of 5. I just want to avoid buffer overruns and other bad stuff.
Cheers,
Brendan (4 Replies)
Discussion started by: Brendan Kennedy
4 Replies
7. Red Hat
Hello,
How to upgrade kernel from 2.4 to 2.6. Currently i am using rhel3 i want to upgrade it to 2.6
Please provide me the steps.
Prashant (1 Reply)
Discussion started by: prashant_ohol
1 Replies
8. UNIX for Dummies Questions & Answers
Hi everyone,
I am trying to have a second kernel in my Red hat 2.4.18.
I downloaded the 2.4.9 version and did all the extract and stuff. when I run the command make bzImage I get the following error:
devlist.h:6931: __devices_b1b3 causes a section type conflict
> devlist.h:6934:... (1 Reply)
Discussion started by: bashirpopal
1 Replies
LEARN ABOUT CENTOS
pki-server-upgrade
pki-server-upgrade(8) PKI Server Upgrade Tool pki-server-upgrade(8)
NAME
pki-server-upgrade - Tool for upgrading Certificate System server configuration.
SYNOPSIS
pki-server-upgrade [OPTIONS]
DESCRIPTION
There are two parts to upgrading Certificate System: upgrading the system configuration files used by both the client and the server pro-
cesses and upgrading the server configuration files.
When upgrading Certificate System, the existing server configuration files (e.g. server.xml, web.xml) may need to be upgraded because the
content may have changed from one version to another. The configuration upgrade is executed automatically during RPM upgrade. However, in
case there is a problem, the process can also be run manually using pki-server-upgrade.
The server upgrade process is done incrementally using upgrade scriptlets. A server consists of the server instance itself and the subsys-
tems running in that instance. The upgrade process executes one scriptlet at a time, running through each component (server instance and
subsystem) in parallel and completing before executing the next scriptlet. If one component encounters an error, that component is skipped
in the subsequent upgrade scriptlets. The upgrade process and scriptlet execution for each component is monitored in upgrade trackers. A
counter shows the latest index number for the most recently executed scriptlet; when all scriptlets have run, the component tracker shows
the updated version number.
The scriptlets are stored in the upgrade directory:
/usr/share/pki/server/upgrade/<version>/<index>-<name>
The version is the server version to be upgraded. The index is the script execution order. The name is the scriptlet name.
During upgrade, the scriptlets will back up all changes to the file system into the following folder:
/var/log/pki/server/upgrade/<version>/<index>
The version and index values indicate the scriptlet being executed. A copy of the files and folders that are being modified or removed will
be stored in oldfiles. The names of the newly-added files and folders will be stored in newfiles.
The instance upgrade process is tracked using this file:
/var/lib/pki/<instance>/conf/tomcat.conf
The subsystem upgrade process is tracked using this file:
/var/lib/pki/<instance>/<subsystem>/conf/CS.cfg
The file stores the current configuration version and the last successful scriptlet index.
OPTIONS
General options
--silent
Upgrade in silent mode.
--status
Show upgrade status only without performing the upgrade.
--revert
Revert the last version.
-i, --instance <instance>
Upgrade a specific instance only.
-s, --subsystem <subsystem>
Upgrade a specific subsystem in an instance only.
-t, --instance-type <type>
Upgrade a specific instance type, by the major version number of the Dogtag instance. For example, use 9 for Dogtag 9 instances and
10 for Dogtag 10.
-X Show advanced options.
-v, --verbose
Run in verbose mode.
-h, --help
Show this help message.
Advanced options
The advanced options circumvent the normal component tracking process by changing the scriptlet order or changing the tracker information.
WARNING: These options may render the system unusable.
--scriptlet-version <version>
Run scriptlets for a specific version only.
--scriptlet-index <index>
Run a specific scriptlet only.
--remove-tracker
Remove the tracker.
--reset-tracker
Reset the tracker to match the package version.
--set-tracker <version>
Set the tracker to a specific version.
OPERATIONS
Interactive mode
By default, pki-server-upgrade will run interactively to upgrade all server instances and subsystems on the machine. It will ask for a con-
firmation before executing each scriptlet.
% pki-server-upgrade
If there is an error, it will stop and show the error.
Silent mode
The upgrade process can also be done silently without user interaction:
% pki-server-upgrade --silent
If there is an error, the upgrade process will stop for that particular instance/subsystem. Other instances/subsystems will continue to be
upgraded.
Checking upgrade status
It is possible to check the status of a running upgrade process.
% pki-server-upgrade --status
Troubleshooting
Check the scriptlet to see which operations are being executed. Once the error is identified and corrected, the upgrade can be resumed by
re-running pki-server-upgrade.
If necessary, the upgrade can be run in verbose mode:
% pki-server-upgrade --verbose
It is possible to rerun a failed script by itself, specifying the instance and subsystem, version, and scriptlet index:
% pki-server-upgrade --instance pki-tomcat --subsystem ca --scriptlet-version 10.0.1 --scriptlet-index 1
Reverting an upgrade
If necessary, the upgrade can be reverted:
% pki-server-upgrade --revert
Files and folders that were created by the scriptlet will be removed. Files and folders that were modified or removed by the scriptlet will
be restored.
FILES
/usr/sbin/pki-server-upgrade
AUTHORS
Ade Lee <alee@redhat.com>, Ella Deon Lackey <dlackey@redhat.com>, and Endi Dewata <edewata@redhat.com>. pki-server-upgrade was written by
the Dogtag project.
COPYRIGHT
Copyright (c) 2013 Red Hat, Inc. This is licensed under the GNU General Public License, version 2 (GPLv2). A copy of this license is avail-
able at http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt.
version 1.0 Jul 22, 2013 pki-server-upgrade(8)
