SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
We have a problem with SUSE 9.3, with scripts in /etc/rc3.d not running at system startup, however if scripts are started manually they will work fine, this config was used under 8.1 with no issue.
Can anyone point to anything we might have missed in the way of changes between the two distros?
Thanks for the advice in advance ;-)
Simon
PS this is an enquiry for a friend, I'm not that techy yet.
The fact they aren't starting automatically but do start manually may just mean you're NOT in run level 3. Have you done "who -r" after reboot to make sure you're in run level 3? If it shows you are not try typing "init 3" and see if that makes them start. The items in /etc/rc3.d would only auto start in run level 3 (items in rc2.d auto start in run level 2 etc...)
If you're not automatically going into run level 3 you can probably change this in your /etc/inittab.
Example from my Debian:
# The default runlevel.
id:2:initdefault:
This tells it to go to run level 2 meaning nothing in run level 3 would get started until I typed in init 3.
To make it boot automatically into run level 3 one would just change the line to:
id:3:initdefault:
Thanks for the input on this, we've managed to get round the problem.
The run level problem appears to be a kernel problem with the i686 version, it works as expected on a 9.3 i586 installation, they can be started manually but do not appear to start automatically.
This has been proven by building two machines, one i586 and i686 machine, apparently set up identically, but evidently not, the differences are marked.
We've also had other problems with loads of other programs too, all appear to be due to different kernels used on the different architectures.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.