Michael Mol wrote:
I still don't know the SysReq magic. I've just ssh'd in. If I can't do
that, it usually means something hardlocked.
This is from a post Neil made many ages ago. Notice the random sig too.
"Hold down Atl, hold down SysRq, press each of the keys in turn. The
usual full sequence is R-E-I-S-U-B Reboot Even If System Utterly Broken
By ${DEITY} - this tagline picker is spooky at times :-O
-- Neil Bothwick System halted - Press all keys at once to continue." Me
again, don't forget to include the options in the kernel config too.
Should look like this: root@fireball / # zcat /proc/config.gz | grep -i
sysrq CONFIG_MAGIC_SYSRQ=y root@fireball / # When it locks up to the
point that those keys don't work, grip the plug firmly and pull. I
usually get to about the E and sometimes the I before I find myself at a
console. Another thing, it is best if you use that to go all the way
down to single user mode, make sure no processes are running that
shouldn't with top or something then go back to regular default mode. I
say that because sometimes there is plenty of cruft left hanging around.
It stops services but the services still have run and lock files and it
leads to errors. You could also just reboot too.
There are quite a few of these commands that gets posted from time to time.
As a hint, I have a text file in my /root directory that contains the
commands and a description. I just cat and grep the file when I need to. I
wouldn't recommend a user directory tho. If for someone reason only root is
mounted, then you can get to /root but not /home if it is a separate
partition. You, and other Gentooers, may want to think about doing
something like this.
Hope this helps in some small way.
Funny thing is, I thought I'd taken care of it. It didn't crop up for
me until xscreensaver kicked in, which crashed X due to differeing ABI
versions between what was already running and what xscreensaver tried
to get linked in. Guess I should remember to restart X. :)
Yea, some updates are tricky. A good while back, I could upgrade all of
KDE and not logout until it is done. Now I have to logout at least a
couple times or things get buggy. I guess things are pretty tight
between programs nowadays.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how
you interpreted my words!
Miss the compile output? Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"
