[yast-devel] system services vs custom service
Hi, while testing the latest webYaST appliance (0.0.10), which runs nice and smoothly so far, I was puzzled by two modules: System Services and Custom Service. What is the difference between those two modules? And what is the reason, why they are separated? Because to me, as a Newbie, both modules basically set up some services. Cu, Martin --- Martin Schmidkunz User Experience Specialist mschmidkunz@novell.com +49 (0) 911 740 53-346 --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --- Novell® Making IT Work As One™
On 8.10.2009 10:28, Martin Schmidkunz wrote:
Hi,
while testing the latest webYaST appliance (0.0.10), which runs nice and smoothly so far, I was puzzled by two modules: System Services and Custom Service. What is the difference between those two modules? And what is the reason, why they are separated? Because to me, as a Newbie, both modules basically set up some services.
Actually Florian has already asked this question, here my reply: Custom service -------------- It is a special view in the service module (see later), it provides a possibility to define start/stop control for a custom service (a third party application, e.g. a database server). The vendor defines what should be called to start/stop the service. The customization is stored in /etc/YaST2/custom_services.yml file. Example: ----------------------------------------------------------------------- # This is an example of how could the configuration file for custom services # look like. # # It is a map of type # # service name: # description: Enhanced description of the service # start: path to application that should start the service # stop: path to application that should stop the service # status: path to application that should query the service status # # The file needs to be located under /etc/YaST2/. # ------------------------------------------------------------------------------ # # The list of services that could be operated by webYaST services module. # Add only name of service if there is /etc/init.d/<service-name> available. # Otherwise, provide also service description and paths to start, stop and # status scripts. collectd: description: Statistics Collection Daemon for filling RRD Files start: "/usr/sbin/rccollectd start" stop: "/usr/sbin/rccollectd stop" # status: "/usr/sbin/rccollectd status" ----------------------------------------------------------------------- System Services ---------------- No config possible, it just displays the basic system services like ntp, network, alsa, firewall, dbus... It displays the current status (running/not running) and allows to start/stop a service. Pretty simple... -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Thursday 08 of October 2009 10:44:13 Ladislav Slezak wrote:
Custom service --------------
It is a special view in the service module (see later), it provides a possibility to define start/stop control for a custom service (a third party application, e.g. a database server). The vendor defines what should be called to start/stop the service.
It is good to not look at Custom service just as some selected LSB service, but more as a specific vendor application, he would like to operate directly from the control panel. As Ladislav writes, "a third party application, e.g. a database server". Jiri -- Jiri Suchomel SUSE LINUX, s.r.o. e-mail: jsuchome@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Jiří Suchomel
On Thursday 08 of October 2009 10:44:13 Ladislav Slezak wrote:
Custom service --------------
It is a special view in the service module (see later), it provides a possibility to define start/stop control for a custom service (a third party application, e.g. a database server). The vendor defines what should be called to start/stop the service.
It is good to not look at Custom service just as some selected LSB service, but more as a specific vendor application, he would like to operate directly from the control panel. As Ladislav writes, "a third party application, e.g. a database server".
The initial WebYaST release for appliances will only show the custom services module. This should prevent any confusions. For openSUSE 11.2 (or SLE11 SP1), the custom service module won't make sense, so it shouldn't be installed on those systems. Going forward (read: WebYaST 2.0 for Appliances) we'll have to find a way to integrate both modules. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (4)
-
Jiří Suchomel -
Klaus Kaempf -
Ladislav Slezak -
Martin Schmidkunz