Thanks Tony. 1) The MRTG thing is weird, I enabled cpu reporting and the mrtg stuff stopped running all the time. Then I disabled cpu reporting and since then there has been no time burned on mrtg. I'm guessing that the default config after a make install left things set up funny and 'refreshing' by turning on and off 'fixed' it. If I see it burning CPU again I'll investigate.
2) WRT the updates the 'standard' way on Fedora is to simply set 'enabled=0' in the /etc/yum.repos.d files then when you want to use them for a manual op do something like: yum --enablerepo=fedora --enablerepo=updates update This is a little safer than moving files around IMO. I submitted a feature request in Jira to be able to disable updates via the UI. -Eric On Jan 25, 2010, at 7:46 AM, Tony Graziano wrote: > If you don't want the package, remove mrtg via yum. > > yum remove sipxconfig-mrtg > > You can just rename the repo file with a different extension, that will > prevent upgrades unless you manually rename it back. > ============================ > Tony Graziano, Manager > Telephone: 434.984.8430 > Fax: 434.984.8431 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > > ----- Original Message ----- > From: [email protected] > <[email protected]> > To: Picher, Michael <[email protected]> > Cc: sipXecs users <[email protected]> > Sent: Mon Jan 25 08:37:29 2010 > Subject: Re: [sipx-users] Some admin type questions > > Thanks on #1, I'll file a request. > > For #2 its coming up as a child of some process started by sipxsupervisor, > not running via the normal system route. I'll investigate further. > > -Eric > > On Jan 25, 2010, at 4:34 AM, Picher, Michael wrote: > >> For number 1, I think the only way to do that is to move/remove the repo >> file from the yum.repos.d or in the repo file, add enabled=0 to the >> sipXecs section. I think filing a feature request for a check box on >> the updates screen would be the right thing to do. >> >> Not sure on #2. Could you set MRTG to not start on startup? >> >> Mike >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Eric >> Varsanyi >> Sent: Sunday, January 24, 2010 12:30 PM >> To: sipXecs users >> Subject: [sipx-users] Some admin type questions >> >> I've got the book and the UI but I can't figure out the 'correct' way >> to: >> >> 1) Disable automatic update checking w/o disabling the repos in >> yum.repos.d (I want to be able to manually update packages but I hate >> the overhead of the checks and the nagging in the UI -- I did shut off >> the alarm mail at least). >> >> 2) Disable mrtg; its burning a lot of CPU time every few minutes and I >> have no statistics enabled. >> >> This is a developer install from SVN 17748 on FC12. I am slowly starting >> to absorb the architecture of the various daemons and their configs but >> I have not yet penetrated the sipXconfig service and its schema. >> >> Thanks for any tips, >> -Eric Varsanyi >> _______________________________________________ >> sipx-users mailing list [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users >> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users >> sipXecs IP PBX -- http://www.sipfoundry.org/ > > _______________________________________________ > sipx-users mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
