Greco my friend, you are taking something that is very, very, VERY simple and making it extremely complicated.
Have you ever used any version of the "Red Hat Linux" operating system (maybe Fedora, RHEL or CentOS)? If you have, have you ever used a command called "chkconfig"? If you don't know what I'm talking about see this link below: http://www.linuxjournal.com/article/4445 Basically, if you don't want the iptables firewall to startat the next reboot you can just type in this command (while root): #chkconfig iptables off and if you want it to start on the next reboot you can just type in: #chkconfig iptables on and if you want to see what run levels it currently is set to start or not start in you can type in: #chkconfig iptables --list Ubuntu Linux has a similar command called "sysv-rc-conf" (I think you have to type in: aptitude install sysv-rc-conf to install it), and then if you want to see for what runlevels bluetooth is turned on you type in: # sysv-rc-conf --list bluetooth See, there is no real need to waste time in vi editing the init scripts to do something this simple because the chkconfig or sysv-rc-conf command does the work for you (you can turn different things on and off for different run levels, but I didn't want this post to be a 20 page tutorial on chkconfig). Anyway, versions of Solaris before Solaris 10 (i.e. Solaris 8 or Solaris 9) had init scripts similar to Red Hat's and Ubuntu's (Debian and Red Hat Linux scripts are copied from the old Solaris model from 20 years ago, ask Ian Murdoch if you don't believe me) and because of this the IRIX / Linux chkconfig command has been ported to Solaris 8 and Solaris 9 (I think you can download a package for it from blastwave but I doubt this is of any use to you since you're probably not running these old versions). Now in Solaris 10, instead of the chkconfig command, you can just use the svcadm command: If you type in this command: # svcadm disable ipfilter then ipfilter will no longer start up the next time you reboot the computer (kind of like "chkconfig iptables off"). Now if you type in this command: # svcadm enable ipfilter then ipfilter will start up the next time you reboot the computer. See, there is no need to edit any init files. If you want the service to not start up on the next reboot just type in: # svcadm disable nameofservice See this link from O'Reilly a better explanation of how it works: http://www.oreillynet.com/pub/a/sysadmin/2006/04/13/using-solaris-smf.html The only time you need to edit the SMF manifests is if you're some kind of super-advanced Solaris systems programmer and you want to make "self-healing services" with artificial intelligence that when the service crashes, SMF can automatically diagnose what is wrong with it, fix the problem and restart the service. I'm not advanced enough to do this yet, but the fact that you can do it is one of the main reasons that SMF is so much better than the old Solaris init scripts from 20 years ago that are still used in Linux. -- This message posted from opensolaris.org
