Question after kernel param config

[steven Burgess_2]

This may sound like a silly question, but. I've just reconfigured the kernel on one of our systems. I've yet to reboot as i've only got a downtime window for midnight.

Are there any implications for not rebooting?

I know the kernel changes don't take place until after reboot, but if I try to look at glance I get the following error

GlancePlus fatal error.


== Fatal Nums Error == C.02.30.00 04/21/99 23:38:36 gailp ==
User: root Date: Mon Mar 18 22:30:13
File: nums.C Line: 4698 Product id: Glance
System: ******* B.10.20 9000/820

MI_GET_LANS failed: -1
== End of Error Msg =============================

Are the 2 connected?

Thanks in advance

Steve

[S.K. Chan · Accepted solution]

Matter of fact they are related. When your built a new kernel, put it in place without rebooting, Glance will be a bit confused because it gets it's data from the active kernel and detect that they are incompatible with the new /stand/vmunix. Only a reboot will make it happy.

[A. Clay Stephenson]

A few commands like ps, Glance, lsof, adb are going to give you very strange results and may crash. The problem is that /dev/kmem and /dev/mem don't map correctly as indicated by /stand/vmunix. It's normally best to delay your kernel rebuilds until shortly before reboot but you will probably be okay.

[steven Burgess_2]

Thanks chaps

I've read up entirely on the parameter changes, but never had to actually make any before. I'm covering for my 3rd level team all week and actually on call. I'm logged on from home waiting for the reboot just to make sure all goes well

Steve

[Tor-Arne Nostdal]

I found the at command very useful.

You could have scheduled a kernel switching and reboot by using the at command.

You can enter several commands you want to do, like making a backup copy of a kernel/moving new into place aso.

at midnight
command_1
command_2
command_3
^D
warning: commands will be executed using /usr/bin/sh
job 1000000001.a at Wed Mar 20 00:00:00 2002

remember that the at command checks and stores your current environment when you issue the command.
Make sure you have privilegies, is on / directory, dont need to give input to commands (Yes/No) etc.