For every scheduled errata, YumAction.doTransaction() is called at some point,
which calls YumBases's runTransaction() at the very end.
The memory consumption grows significantly, when self.ts.run() is called
inside runTransaction().
The reason I'm asking you for advice is that I'm not sure whether we're
looking at some rpm-python bug or whether the way we're using yum libraries
is plain broken.
Greetings James, I'd very much appreciate your advice or hint on this
bug report.
Here's a link to yum-rhn-plugin code, that's used by rhn_check
when applying errata to a system:
http:// git.fedorahoste d.org/git/ ?p=spacewalk. git;a=blob_ plain;f= client/ rhel/yum- rhn-plugin/ actions/ packages. py;hb=HEAD
For every scheduled errata, YumAction. doTransaction( ) is called at some point,
which calls YumBases's runTransaction() at the very end.
The memory consumption grows significantly, when self.ts.run() is called
inside runTransaction().
The reason I'm asking you for advice is that I'm not sure whether we're
looking at some rpm-python bug or whether the way we're using yum libraries
is plain broken.
Thank you.