If you happen to administer SUSE LINUX Enterprise Server 9 (x86_64) and you need to add or remove already existing /etc/init.d script or custom created Apache / Tomcat .. etc. service and you're already familiar with Fedora's / RHEL chkconfig, then the good news chkconfig is also available on SuSE and you can use in same way chkconfig to start / stop / enable / disable boot time services.
To list all available boot time init.d services use:
suse-linux:/etc # chkconfig –list
SuSEfirewall2_final 0:off 1:off 2:off 3:off 4:off 5:off 6:off
SuSEfirewall2_init 0:off 1:off 2:off 3:off 4:off 5:off 6:off
SuSEfirewall2_setup 0:off 1:off 2:off 3:off 4:off 5:off 6:off
Tivoli_lcfd1.bkp 0:off 1:off 2:off 3:off 4:off 5:off 6:off
activate_web_all 0:off 1:off 2:off 3:on 4:off 5:on 6:off
alsasound 0:off 1:off 2:on 3:on 4:off 5:on 6:off
apache2 0:off 1:off 2:off 3:off 4:off 5:off 6:off
apache2-eis 0:off 1:off 2:off 3:on 4:off 5:off 6:off
atd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
audit 0:off 1:off 2:off 3:off 4:off 5:off 6:off
autofs 0:off 1:off 2:off 3:off 4:off 5:off 6:off
autoyast 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.clock 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.crypto 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.device-mapper 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.evms 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.idedma 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.ipconfig 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.isapnp 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.klog 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.ldconfig 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.loadmodules 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.localfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.localnet 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.lvm 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.md 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.multipath 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.proc 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.restore_permissions 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.rootfsck 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.sched 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.scpm 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.scsidev 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.shm 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.swap 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.sysctl 0:off 1:off 2:off 3:off 4:off 5:off 6:off
boot.udev 0:off 1:off 2:off 3:off 4:off 5:off 6:off
coldplug 0:off 1:on 2:on 3:on 4:off 5:on 6:off
To then stop the service:
suse-linux:/etc # chkconfig gtiweb off
If you prefer to do it the SuSE way and learn a bit more on SuSE boot time process check out:
suse-linux:/etc # man insserv
Removing already existing SuSE start-up script from init.d start up with insserv is done with:
suse-linux:/etc # cd /etc/init.d/
suse-linux:etc/init.d # insserv -r gtiweb
insserv: script ipmi.hp: service ipmidrv already provided!
insserv: script boot.multipath.2008-10-29: service boot.multipath already provided!
To install a new custom written and placed into /etc/inti.d/ on SuSE's server boot time with insserv:
suse-linux:/etc/init.d/ # insserv your_custom_script_name
More helpful Articles

Tags: apache2, boot time, command, custom, hp, init, process, script, server boot, udev