System files | Go to top

Location Description
/etc/init.d/ Holds service initialisation scripts. This is known as the SystemV style - the scripts are stored in subdirectories named after their runlevel, as opposed to the BSD style where each runlevel is defined by a script in /etc/rc.d/. These can be manually executed with /etc/init.d/[service] [start|stop|restart]. You can set which script starts at a runlevel with insserv [service].
/etc/rc.d/ Contains a subdirectory per runlevel, normally rc1.d, rc2.d, rc3.d, rc4.d, rc5.d, rc6.d, rcS.d. Each directory contains soft links to init scripts held in /etc/init.d/, populated using the insserv command (see Set services to start at boot). The naming of these links determine whether the service is to be started or stopped - those that start with K will be stopped (killed) and those that start with S will be started.

Disable SuSE Firewall | Go to top

SuSE 10.0 comes with it's own firewall, called SuSEfirewall2. This can cause problems if you don't know it exists ;-) For example, I was having problems connecting to ssh. I'd disabled SELinux (by adding selinux=0 to the boot options in /etc/grub.conf) and cleared all iptables rules, but still ssh wasn't working. It turned out I had to turn off the SuSE firewall too.

SuSEfirewall2 stop

Set services to start at boot | Go to top

SuSE Enterprise Server 9.0. To start a service at boot:

insserv service

To stop a service at boot:

insserv -r service

The service must be in /etc/init.d/ and the runlevel must be in /etc/rc.d/.

Last modified: 21/06/2006 (most likely earlier as a site migration in 2006 reset some dates) Tags: (none)

This website is a personal resource. Nothing here is guaranteed correct or complete, so use at your own risk and try not to delete the Internet. -Stephan

Site Info

Privacy policy

Go to top