[Yum] [python API] logging

[Alon Bar-Lev]

----- Original Message -----
> From: "Panu Matilainen" <pmatilai at laiskiainen.org>
> To: yum at lists.baseurl.org
> Sent: Monday, September 17, 2012 7:37:34 AM
> Subject: Re: [Yum] [python API] logging

<snip>

> 
> >
> > Disabling the log completely is not something I like, logs are not
> > evil as long as I can control the output location and verbosity.
> >
> > Using this and propagate, I still have the following messages to
> > stdout:
> > ---
> [...]
> >
> > Freeing read locks for locker 0x5: 1228/139804988552960
> > Freeing read locks for locker 0x7: 1228/139804988552960
> > Freeing read locks for locker 0x8: 1228/139804988552960
> > Freeing read locks for locker 0xf: 1228/139804988552960
> > Freeing read locks for locker 0x11: 1228/139804988552960
> > Freeing read locks for locker 0x12: 1228/139804988552960
> > Freeing read locks for locker 0x13: 1228/139804988552960
> > Freeing read locks for locker 0x14: 1228/139804988552960
> > Freeing read locks for locker 0x15: 1228/139804988552960
> > Freeing read locks for locker 0x16: 1228/139804988552960
> > Freeing read locks for locker 0x17: 1228/139804988552960
> > Freeing read locks for locker 0x2f: 1228/139804988552960
> > Freeing read locks for locker 0x31: 1228/139804988552960
> > Freeing read locks for locker 0x32: 1228/139804988552960
> > ---
> 
> Note that these "freeing locks" messages are not something you should
> be
> normally seeing. They indicate that a process has been forcefully
> terminated (eg kill -9'ed or crashed) while having read-locks on the
> rpm
> database. If you're routinely seeing them, something is wrong (in
> your
> software or something else on the system)
> 
> 	- Panu -

Thank you Panu,

I am aware of that.

But my application should not print anything unexpected to stdout/stderr, no matter in which state yum is.

Regards,
Alon Bar-Lev.