I'm attempting to build a RHEL 6.3 yum errata server inside our company firewall with no luck. Is this something Red Hat attempts to prevent people from doing?
I have done all the steps that I've been able to find to create a repository and configure it.
Dear Red Hat Linux user,
We are approaching the published end of life date for errata support
for our final Red Hat Linux distribution. We'd like to remind you of
this date and the options available to you for migrating your Red Hat
Linux implementations: Red Hat Enterprise Linux and the... (0 Replies)
Dear all,
My server has shutdown frequently.
It is AMD64, OS is RHEL 4 U5.
I've seen the system log, before the shutdown occured:
Jul 29 04:28:56 localhost kernel: EDAC k8 MC0: general bus error: participating processor(local node response), time-out(no timeout) memory transaction... (2 Replies)
hi ,
i installed RHEL 5 server in one machine . i am able to login through putty . But not through Exceed . i mean to say i want a graphical user interface through exceed . some other machine i am able to log in through exceed .
is there any configuration is there for that one . did i miss... (3 Replies)
I had the query of what would be the right approach to change the time on the RHEL server. I have the following ways to do that:
1)
# date -s "2 OCT 2006 18:00:00"
Or
# date --set="2 OCT 2006 18:00:00"
2)
# date +%Y%m%d -s "20081128"
The second option though would only change... (4 Replies)
I wanted to know how to find un-partitioned space in a Red Hat Linux server. I tried using fdisk but does not seem to be a user friendly output.
I hope, my question is clear.
Please revert with the reply to my query.
Regards (1 Reply)
I had a query that should the RHEL servers in production environment be re-started say every 2-3 months so that the cache is cleared?
I hope, my question is clear that should the Red Hat Linux servers be restarted periodically.
Please revert with the reply to my query.
Regards (17 Replies)
Hi Friends,
My Server is con't stated..it shows the below error..
Red hat exterprise Linux As Release 4(nahat)
kernel 2.6.9-5.ELsmp on an i686
INIT : id "x" respawing too fast :disabled for 5 minutes...
Please help help
Thanks,
Srinivas (1 Reply)
Dear All,
I have a RHEL 5 server of 64 bit . I have disabled the firewalls and added the name server also in resolv.conf.
I want to connect to internet inorder to link the machine with Linux Network.
# I could not connect to any website from this server for ex
ping google.com is not... (8 Replies)
Hi guys,
I'm moving some vPars from BL860c I2 and BL870c I2 using the DRD clone and relocation. In some case, as instance to upgrade to BL870c I2, the ERRATA document reports some additional driver to be added to the image made by the DRD and then recompile the kernel before the move to the... (0 Replies)
Dear All ,
One of our Oracle Database Server , which got hanged a couple of days before , so that we could not login to the Server , but it was pinging.
So we tried various options and at last we did a reboot of this server.
To find out the root cause of the Server Hang , when i checked the... (2 Replies)
Discussion started by: jegaraman
2 Replies
LEARN ABOUT CENTOS
ksc
KSC(1) User Commands KSC(1)NAME
ksc - Linux kernel module source checker
SYNOPSIS
ksc [ -d | --directory ] DIRECTORY
ksc [ -k | --ko ] FILE
OPTIONS
KSC accepts command-line arguments, and has both a long and short form usage. You can use either style or combine them to specify
options. When the tool is run with kernel module sources it checks for all four architectures, and when run with binary kernel modules, it
checks for the specific architecture for which the binary was built.
Valid RHEL whitelist releases are rhel6.0, rhel6.1, rhel6.2, rhel6.3, rhel6.4
-h, --help
show this help message and exit
-c CONFIG, --config=CONFIG
path to the local ksc.conf file. If not specified the tool tries to read from ~/ksc.conf and if that is also not found then from
/etc/ksc.conf
-d DIRECTORY, --directory=DIRECTORY
path to the directory
-i, --internal
to create text files to be used internally.
-k KO, --ko=KO
path to the ko file. You should either use -d or -k to run the KSC tool, but not both. If both -d and -k option is used at the
same time then only -d is used and the -k option is discarded.
-n RELEASENAME, --name=RELEASENAME
Red Hat release against which the bug is to be filed. Default value is 6.5
-p PREVIOUS, --previous=PREVIOUS
path to the previous resultset file and submit it as a bug to Red Hat Bugzilla.
-r RELEASE, --release=RELEASE
RHEL whitelist release used for comparison
-s, --submit
Submits the report to the Red Hat bugzilla (https://bugzilla.redhat.com). The credentials need to be in the /etc/ksc.conf file. The
tool will prompt for bugzilla password.
The configuration file looks like below:
[bugzilla]
user=user@redhat.com
partner=partner-name
partnergroup=partner-group
server=https://bugzilla.redhat.com/xmlrpc.cgi
-v, --version
Prints KSC version number
ksc - Version 0.9.11 Feb 2014 KSC(1)