Is there a way to kill an Individual Process without rebooting.

[Xolotl]

I was just wondering, is there a way to end a misbehaving NLM without having to Down, Restart Server, or even worst CTRL+ALT+ESC?

Something like 'CTRL+C' in DOS, or Linux.

Thanks.

 

[Lou0686]

Hi,

It can be done through debugger. Shift + Shift + Alt + Esc. I don't know the commands to do it (I don't think anyone does) but you can search Novell's site for debugger commands. I think that will get you what you want.

Lou

 

[terry712]

why do you just unload the nlm

ie unload shagger

 

[hunterfs]

Have you tried just unloading the NLM?? My experience has been that misbaving NLM's have usually overstepped their memory bounds. Even if you are able to end them with the debugger you usually wind up with memory issues when you try to reload it. It is almost always safer to re-boot the server. If this is a re-occuring process then try replacing the nlm file, possible the file has become corrupt. Also make sure you are using the most current support nlm's that the misbaving NLM were written for.

Anything after that you may need to contact the vendor.

Just my thoughts/experience.

 

[Xolotl]

Thanks, everybody, for your help.

Yes, I tried to unload the NLM by doing a CTRL+ALT+ESC, then option 3, and opening a second command line process, but it did not respond. Maybe if I wait a looong time, eventually it would do it.

In other OS's you have the option to kill a non responsive process immediately, without rebooting the system, and I just wanted to know if that was the case for NetWare 6.

 

[terry712]

is it abending the server?
is it locking the console?

to kill a non responsive you dont reboot the server
in fact the only time a netware server is normally rebooted is if you service pack it

what nlm is unresponsive

if you have flakey nlm's you should load it into a protective memory ring but should and do are two different things