Jan Pazdziora wrote:
On the other hand, having the scout run on the same Spacewalk server
is just one possible setup. It can also run on Proxies and it will
probably be hard to shut down the scout on Proxies as well. Are we
OK with the scout on Spacewalk server behaving differently from the
Proxy one?
Scout (on proxy) check every minute url
/satconfig/cgi-mod-perl/fetch_commands.cgi
so I think we can crete new command "hey scout - die yourself". So if
monitoring backend is not running fetch_commands.cgi will always
generate this command and scout can switch off himself.
How about not allowing to disable the monitoring in the WebUI if there
is at least one enabled scout there? Or at least having big fat warning
You can always start scout on proxy manualy. So this warning/blocking
really does not make sense.
--
Miroslav Suchy
Red Hat Satellite Engineering
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
