On Sat, Nov 12, 2011 at 09:09:18PM +0100, Jan Pazdziora wrote: > > Please find attached a proposed patch for this. > > I've added database.control boolean directly in rhn.conf file. > > I've modified the spacewalk-service script to manage this parameter. In all > > cases, oracle is controlled, for compatibility with RH Satellite product. > > I've left commented out a sleep before starting osa-dispatcher: this sleep > > allows to get rid of osa-dispatcher error connecting to jabberd. I couldn't > > find another find to check if jabberd was ready to accept connection. Feel > > free to either remove it or uncomment it. > > I'm against this change. The database (PostgreSQL, Oracle XE) is > completely independent from the Spacewalk software product and the > spacewalk-service script should have no business fiddling with them. > > If for some reason (what reason, exactly?) you need to restart > everything with one script, why not write a wrapper around it?
On Mon, Jan 23, 2012 at 10:25:53PM -0500, Marcelo Moreira de Mello wrote: > Hello team, > > Here follow 3 patches which includes a capability to Spacewalk > ignore to start some services when running the > /usr/sbin/spacewalk-service script. > > Below is an example after applied the patch excluding the > Taskomatic service to be started: > > # cat /etc/rhn/disabled-services > DISABLED_SERVICES="taskomatic" Since there were two opposite requests (add PostgreSQL to spacewalk-service, make it possible to remove taskomatic), I've ended up adding support for /etc/rhn/service-list where you can manipulate the $SERVICES list in any way. In Spacewalk master, spacewalk-admin-1.7.3-1. -- Jan Pazdziora Principal Software Engineer, Satellite Engineering, Red Hat _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
