[Yum-devel] Syslogging chrooted installs

[Jeremy Katz]

On Tue, 2006-06-20 at 16:30 -0400, seth vidal wrote:
> On Tue, 2006-06-20 at 16:08 -0400, Konstantin Ryabitsev wrote:
> > (this is a side-effect of mock builds)
> > 
> > I have noticed that yum will log all mock-related package installs in
> > /var/log/messages, even though technically those aren't applied to the
> > system -- only to a chrooted environment. Is that the expected
> > behaviour, or would it make more sense to syslog only actions that are
> > related to non-chroot installs?
> > 
> 
> so we need to check if --installroot is not / and if so not include the
> syslog logger path.

Does it make sense to do that or would it be better to include the
information on what the root is in the syslog'd message?  

For the mock case, sure, syslogging is probably overkill.  But if you're
managing chroots for some other reason, then it might not be so useless

Jeremy