I have a problem when i shutdown suse 10.1 intermittantly my system will just hang, the last service to stop is the syslog services which completes ok, no error logs or anything the system just freezes and then obviously on a reboot after physically killing power this forces a disk check. Does anybody have any ideas on how to narrow down the problem?

Shutting down syslog services does complete sucessfully by the way and according to my runlevel listing the only service enabled left to shutdown is xdm.

Not sure if the runlevel listing is in the same order as it is on shutdown??

Not sure why it hangs, but I can shed some light on the shutdown process.

The runlevel listing in Yast is alphabetical, and doesn't really indicate the order of starting or stopping. Look in your /etc/init.d/rc5.d directory. These are the scripts that are run when entering or leaving run level 5 (the full X-Windows system). The scripts starting with 'S' are the ones run when starting, and the ones starting with "K" are the ones run when ending. These are executed in the order you see them in. So, try to find what script is being run when it hangs, or what script comes next. That might help narrow it down. BTW: These scripts are just links that point to the actual scripts in /etc/init.d.

HTH.

Jean

Thanks for that information, its like gold dust. Should have guessed really it was in alphebetical order. durr.
;-)

Have now found that its hanging on network. I know i have had alot of problems getting my wireless connection up on everyboot with knetworkmanager. kept asking for my wep key everytime and got totally sick of entering a password everytime for kwallet so set it with no password, seemed to work but think its causing problems on the shutdown process now. Not sure if it will be kwallet or knetworkmanager causing the problem. Shame i cant get ifup to work with a 40bit wep key.

Thanks for your help, its much appreciated.

Maybe try reconfiguring your network card with Yast? I'm surprised you're having problems using the ifup method with a 40 bit key, that shouldn't matter.

Jean

Have tried with yast with suse 10.0 had no problems with ifup but 10.1 seems to only allow 128bit security, i think the answer to is is for me to change my wep key to something longer.

Same here - sometimes it stops while shutting kde/m manager.
I have just installed - Will check out log files and others.

FWIW: I'm using a 40 bit wep key with 10.1, and it works fine. The Authentication Mode is 'Open', and I entered the 10 hex digits for the key.

Of course, 40 bit keys are acknowledged to be much too weak, and we should both upgrade to 128 bit ... :-)

Jean