>> I think the simple way is to place your script in >/etc/init.d/scriptname >> and then call "chkconfig --add scriptname" which will add >it, then use >> chkconfig for turning it on/off at various runlevels. > >Yes, if your initscript has the appropriate syntax at the top. > >I can think of a lot of reasons to bash Red Hat, but their system for >managing start/stop scripts, and really all of their "add a >file in this >directory" config setup is the best and most sysadmin-friendly (and in >many cases, packaging-friendly) configuration of any UNIX or >Linux vendor >I've seen. They've taken an area where AIX (of all things) >had the best >tools, and done it better and in a more open manner. > >So, here's a little applause for a job well done on their part! yes. note there's also a vendor-neutral extension of this concept in the LSB, which defines a more comprehensive set of initscript rules, still buried in the comments like the chkconfig support is. _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
