Suse/NovellThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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.
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.