Still, I don't get it. We do have 'apachectl' for customers who are migrating from non Solaris world and 'svcadm' for regular Solaris 10 administrators. These two are distinct and different ways to start / stop the servers. Why should we create this wrapper , document it. and introduce another new way to manage the server ?
Yes, I can understand , if we patch apachectl script so that it internally uses svcadm to start/stop the server. This way, both apachectl and svcadm will give a consistent behavior and using one will automatically reflect in the other. thanks sriram Seema Alevoor wrote: >>> Agreed. >>> But, apachectl.smf script will essentially be a wrapper for the svcamd >>> commands. >>> >>> >>> >> Sorry, for being so ignorant , Why should we create a wrapper when >> svcadm commands are a standard interface in Solaris 10 and onwards ? >> > > So that user does not have to worry about FMRI and commands to start stop the > server. > For the user, it will be same as starting/stopping apache using apachectl. > > -- Seema. > _______________________________________________ > webstack-discuss mailing list > webstack-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/webstack-discuss >
