Hi Andrea, Le vendredi 19 octobre 2007 04:09, Andrea Righi a écrit : > Honestly I don't know which is the best solution... IMHO starting rsyncd > and monitord without an explicit action from the user could lead to > security issues (exposing the availability of the images before any > customization of the rsyncd.conf for example). OTOH starting the basic > services at the boot could be a good point in terms of usability: why the > user has to start manually these services when he'll surely use them? At > least rsyncd is *always* needed for any kind of operation made by > systemimager. > > In these cases I vote for the simplest solution: do not start the services > on boot and leave the things as they are.
Works for me. > > The other problem, if I remember well, consists in the failure when you > stop a daemon and it has not been started before. Does this "corrupt" the > removal of the packages when the services are down? (not yet tested). Yes i think so but we should double-check i am far from being 100% sure. Regards, -- Geoffroy ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
