Mike McCune wrote:
I'm thinking we need to drop support for Monitoring in 0.2. There are
just a few too many problems that will hopefully get fixed in 0.3:
* Startup scripts and some packages referring to things in
/opt/home/nocpulse but we still have most everything in /home/nocpulse
* Configuring the DB options on the
https://spacewalk.example.com/rhn/admin/config/MonitoringConfig.do
seems to mess up the database name vs password.
https://bugzilla.redhat.com/show_bug.cgi?id=461517
The only workaround to part of the above problem was to hard code
uname/password values into the Perl code. Even after that I still got
odd errors.
* Need to get the Monitoring rpms added to the spacewalk meta RPM but
don't want todo this until we get it actually working.
thoughts?
Mike
Sigh. It's way too late in the game to fix all of this in
0.2. We're already late :) I know Mirek has >100 commits in
a monitoring branch that seem to fix a lot of these. Let's
see if we can get monitoring working properly in Spacewalk 0.3.
--
jesus m. rodriguez | [EMAIL PROTECTED]
sr. software engineer | irc: zeus
rhn satellite & spacewalk | 919.754.4413 (w)
rhce # 805008586930012 | 919.623.0080 (c)
+-------------------------------------------+
| "Those who cannot learn from history |
| are doomed to repeat it." |
| -- George Santayana |
+-------------------------------------------+
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
