Easiest way is to take a look at the manual entry for "chkconfig". This utility requires you to add a couple of special comment lines in the script you copy to /etc/init.d, and in return it will make all of the funky links in the rcN.d directories for you. It also gives you a nice way to activate and deactivate the service on a given machine (i.e., make a service available; you still turn it on and off by using the 'service' utility). I've done a couple of custom services this way; it's very quick, and a lot less error-prone. Good luck with it, Rob Thorne Martin Stricker wrote: >Jason wrote: > > >>Hmm, I just slid up to my coworkers RH8 system and think I figured it >>out. I just tried copying irda to irda2 in /etc/init.d and it did not >>show up in the list of services. But I then linked it in >>/etc/rc.d/rc3.d as S91irda2 and it showed up fine. Linking it as >>just irda2 didnt work. I imagine from what I've seen you have to >>link it as [S/K]XXyyyyyy in order for the services program to 'see' >>it. >> >> > >That's because such a filename is needed to start/stop that service at >bootup or runlevel change. S means start it if entering the runlevel, >K means stop (kill) it when leaving the runlevel. The two-digit number >determines the execution order, 00 is first, 99 is last. This is >important if a service depends on another (i. e. bring up the network >interface before starting the network servers). Any filename that does >not comply to this naming scheme will be ignored by init (man init for >more information), and thus service does the right thing by ignoring it >as well. > >Best regards, >Martin Stricker > > -- Rob Thorne Chief Technical Officer Torenware Networks -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
