12-29-2013
Reboot does not work after update
Hi guys,
thanks for your help. I recently did a yum update on my rhel6.4 server. After this update, user logins take for ever and the reboot command does not work. When I do a reboot, the server hangs. Nothing happens.
Any help with this will be appreciated.
Thank you
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
I'd like to know if to reboot a work station I need the root permission.
If not what is the procedure ( commands or steps ) to reboot a work station.
Cheers
Mohsen (5 Replies)
Discussion started by: mohsen
5 Replies
2. Solaris
Hi Guru's
Can any want here could explain to me the different between soft reboot and hard reboot .
Best Regards
Seelan (3 Replies)
Discussion started by: seelan3
3 Replies
3. AIX
Hi,
The apar instructions is to reboot on the ibm site. Is there's a way to update apar w/o reboot? I think I heard something before that it's possible.
Thanks in any idea you will type... (1 Reply)
Discussion started by: itik
1 Replies
4. Solaris
Hi all,
I have a server SUN FUJITSU in solaris 10 ; result of uname -a is :
SunOS MOBD1 5.10 Generic_118833-03 sun4us sparc FJSV,GPUZC-M
I have configured the eeprom to auto-boot as usual and this automatic reboot does not work in case of power failure. I must type "boot" on the prompt "ok"... (5 Replies)
Discussion started by: aribault
5 Replies
5. UNIX for Advanced & Expert Users
Hi All!
I'm running "Solaris 10 10/08 s10s_u6wos_07b SPARC" on M5000.
I ran sys-unconfig and after the machine rebooted the system did not prompt me for configuration info (system name, ip address, etc). I have also modified /etc/.sysIDtool.state changing all "1" to "0" and touch... (1 Reply)
Discussion started by: bluescreen
1 Replies
6. IP Networking
hi all. and sorry for the random question, but this sparkled a raging flame-war at work and i want more points of view
situation
a router, with linux of some sort,
dhcp client requesting for ip in wan1 (as usual with wan ports)
dhcp server listening in lan1, and assigning ip (as usual... (9 Replies)
Discussion started by: broli
9 Replies
7. Red Hat
Hi
Is it a way ? When Linux kernel updated that don't want reboot it means without reboot the new kernel performances
Thanks (7 Replies)
Discussion started by: mnnn
7 Replies
8. UNIX for Beginners Questions & Answers
I have downloaded RHEV-H 4.2 Red Hat Virtualization - Red Hat Customer Portal (RHVirtualization 4.2 Host and Manager iso). I uploaded the image and installed on an HP G9 server baremetal.
I found I dont have a WAN/net connectivity later on HPG9 server. How can I still install virt-manager on... (1 Reply)
Discussion started by: Paras Pandey
1 Replies
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)